because someone believed an ANSWER on a different question answered my question

Yeah that is actually their official position. Your question is duplicate if an answer elsewhere might answer it, which is clearly absurd. Essentially they think "what's 1+3?" is a duplicate of "what's 2+2?".

I think fundamentally they gamified moderation too well, and for many people they turned the site into a mod-maxing game, which obviously makes it an abysmal place to be for normal users.

Stop linking this, please! Any benchmark where Typescript and JavaScript are different is trash.

That's nitpicking. It is statically typed. Is Dart not statically typed because it has dynamic.

You could call it "gradually typed" if you want to be pedantic.

can be circumvented pretty easily

That means it isn't sound.

Uhm... You went to all that effort and then didn't actually answer the question! Can you put the data in a readable format so we can see whether using exceptions made a difference?

I would say:

1. Avoid async if you can. It's way more difficult and error prone than non-async Rust. Unfortunately a lot of web stuff insists on async.
2. Don't be afraid to .clone() stuff to fix lifetime errors. It's not optimal but consider that in C++ everything is pretty much cloned by default, and nobody ever said C++ was slow.
3. Use anyhow::Result for error handling. It's the easiest option.

Wow look at that CUPS code and tell me with a straight face there aren't 5 more similar vulnerabilities waiting to be found...

I agree, too little regard for backwards compatibility. They also removed distutils which meant I had to fix a load of code that used it. It was bad code that shouldn't have used it even when written, but still... seems like they didn't learn their lesson from Python 2.

It's not like it would be difficult to avoid these issues either. Everyone else just makes you declare your "target version" and then the runtime keeps things compatible with that version - Android via SDK target version, Rust with its editions, hell even CMake got this right. CMake!!

It's not a browser issue. There's some weird "responsive" thing that entirely hides the graphs. You probably just have a bigger screen.

The general difficulty of setup, poor & buggy hardware support and the inevitability of dropping to the command line are bigger issues.

Git is all about tracking changes over time which is meaningless with binary files.

Utter codswallop. You can see the changes to a PNG over time. Lots of different UIs will even show you diffs for images.

Git can track changes to binary files perfectly well. It might not be great at dealing with conflicts in them but that's another matter.

The only issue is that binary files tend to be large, and often don't compress very well with Git's delta compression. It's large files that are the issue, not binary files. If you have a 20 kB binary file it's going to be absolutely fine in Git. Likewise a 10 GB CSV file is not going to be such a good idea.

You're right of course. I think the issue is that Linux doesn't care about the UI. As far as it is concerned GUI is just another program. That's the same reason you don't have things like ctrl-alt-del on Linux.

I scrolled a lot before I gave up looking for an example. No thanks.