Best thing is, they introduced some settings to turn that auto-conversion off and they don’t work 🤣 can’t make that stuff up.

Hetzner ❤️

JPEG does not support lossless compression. There was an extension to the standard in 1993 but most de/encoders don’t implement that and it never took off. With JPEG XL you get more bang for your buck and the same visual quality will get you a smaller file. There would be no more need for thumbnails because of improved progressive decoding.

https://youtu.be/UphN1_7nP8U

JPEG does not support lossless compression. There was an extension to the standard in 1993 but most de/encoders don’t implement that and it never took off. With JPEG XL you get more bang for your buck and the same visual quality will get you a smaller file. There would be no more need for thumbnails because of improved progressive decoding.

https://youtu.be/UphN1_7nP8U

It’s not just like jpeg with extra channels. It’s technically far superior, supports loss less compression, and the way the decompression works would make thumbnails obsolete. It can even recompress already existing JPEGs even smaller without additional generation loss. It’s hard to describe what a major step this format would be without getting very technical. A lot of operating systems and software already support it, but the Google chrome team is practically preventing widespread adoption because of company politics.

https://issues.chromium.org/issues/40168998

Could be because of people (or bots, whatever) rating but not commenting?

He is comparing himself to Caesar? Maybe someone should stab him to help him out.

I’m pretty sure it’s not FALLS() but WENN(), at least the last time I used Excel.

I’d suggest “vorzeichnenbehaftete Ganzzahl” (maybe vbGanz) and “vorzeichenlose Ganzzahl” (vlGanz) 🤣 please don’t make that a thing

Does that get translated if someone else with a different language opens that file?

Could be because Ganz is short for Ganzzahl and a noun.

Don’t use floats when you need to get accurate stuff

Floats are accurate. Could you name a situation (except money) where you think floats are not accurate enough to handle it?

Sure, just asign them a random Greek letter and call it a day 🤣

Why?

Not only for audio, but everything that doesn’t have to be an exact base 10 representation (like money). Anything that represents something “analog” or “measured” is perfectly fine to store in a float. Temperature, humidity, windspeed, car velocity, rocket acceleration, etc. Calculations with floats are perfectly accurate and given the same bit length are as accurate as decimal types. The only thing they can’t do is exactly(!) represent base 10 decimals but for a very large amount of applications that doesn’t matter.

That’s not really true and it depends on what you mean. If your decimal datatype has the same number of bits it’s not more accurate than base 2 floats. This is often hidden because many decimal implementations aren’t 64 bit but 128 bit or more. But what it can do is exactly represent base 10 numbers which is not a requirement for a lot of applications.

You can use floats everywhere where you don’t need numbers to be base 10. With base 2 floats the operations couldn’t be more accurate given the limit of 64 bits. But if you write f64 x = 0.1; and one assumes that the computer somehow stored 0.1 inside x they already made a wrong assumption. 0.1 can’t be converted into a float because it’s a periodic in base 2. A very very pedantic compiler wouldn’t even let you compile that and force you to pick a value that actually can be represented.

Down the rabbit hole: https://zeta.one/floats-are-not-inaccurate/

But that’s not because floats are inaccurate. A very very pedantic compiler wouldn’t even let you write f64 x = 0.1; because 0.1 (and also 0.2 and 0.3) can’t be converted to a float exactly (note that 0.5, 0.25, 0.125, etc. can be stored exactly!)

The moment you write f64 x = 0.1; and expect the computer to store that inside a float you already made a wrong assumption. What the computer actually stores is the float value that is as close as possible to 0.1. But not because floats are inaccurate, but because floats are base 2. Note that floating point types in general don’t have to be base 2 - they can be any base (for example decimal types are base 10) but IEEE754 floats are base 2, because it allows for simpler hardware implementations.

An even more pedantic compiler would only let you write floating point in binary like 10.10110001b and let you do the conversation, because it would make it blatantly obvious that most base 10 decimals can’t even be converted without information loss. So the “inaccuracy” is not(!) because float calculations are inaccurate but because many people wrongly assume that the base 10 literal they wrote can be stored inside a float.

Floats are actually really accurate (ignoring some Intel FPU hardware bugs). I skipped a lot of details which you can find here: https://zeta.one/floats-are-not-inaccurate/

Equipped with that knowledge your calculation 0.1+0.2 != 0.3 can simply be translated into: “The closest float to 0.1” + “The closest float to 0.2” is not equal to “The closest float to 0.3”. Keep in mind that the addition itself is perfectly accurate and without any error/rounding(!) on every EEE754 conforming implementation.

Selling your data would be stupid, because they make money with the fact that they have data about you nobody else has. Selling it would completely break their business model.

I don’t think that’s how it works. If it exactly looks like something protected by laws like copyright or whatever your country uses, I highly doubt that any court would say that it’s fine just because it was created by AI.

Ok I also try it one last time 🤣

Go to Google images and search for “Desktop”. What you see is Desktop machines amd setups and how I and the vast majority of the world use the word “Desktop”.

Now search for “handheld game console”. It’s very likely that one of the first few results is literally a SteamDeck.

Now back to the stats. As I already said. SteamDeck will be tracked as a Desktop because stat tracking sites just use Browser User Agents and try to detect what the device actually is, but that’s very hard if not right out impossible because clients (including the SteamDeck) intentionally (for privacy and compatibility reasons) lie about what they are all the time!

If you take your mobile browser and enable “Desktop site” or “Desktop mode” it will lie(!) and make the server think it’s a Desktop - even though it is really not. A smartphone doesn’t magically become a Desktop PC. If I browse the web with my typical mobile browser - every site will track my activity as smartphone. If I switch to Desktop mode most sites will track me as a Linux Desktop Machine. But my device has not changed.

So you are right that the SteamDeck is tracked as a Desktop PC. But that’s because the Server has has either no better category for the device or can’t determine what the device really is because it lies about what it is.

https://webaim.org/blog/user-agent-string-history/

Stat tracking always had (and will have) two big issues (which can’t really be fixed).

Devices which lie about what they are (see link above) and the problem that they have to come up with some categories and there will always be some devices which fall between the categories (Think fridge, microwaves, sex toys, etc.).

If your SteamDeck is currently actually connected to a monitor a mouse and a keyboard than you are actually using it as a Desktop PC. But if you use it like most people - even though the SteamDeck lies about it - it’s not a Desktop, because the word “Desktop” really is about the form factor - it’s not just my definition. Give any of your friends a piece of paper and a pencil and ask them to draw a Desktop PC - I would actually be amazed if anybody in the world (even you! outside the context of this discussion) would draw anything even remotely resembling a Steam Deck.

👋