Very cool but I hope they give it proper GUI integration, not just a webview or VNC, which is how the alternatives work.

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

From what I could tell it's just because he cared about things a lot, and maybe is a little on the spectrum. He definitely wasn't wrong, and maybe other people would have just given up and gone on with their lives but I don't think that's necessarily a trait to encourage.

To put it another way, sometimes when people kick up a fuss it's because they are obstinate naysayers, and sometimes it's because they're doggedly holding decision makers to account. This seemed more like the latter from what I read.

Yeah I would also recommend avoiding async Rust as much as possible. There's really only a small number of situations where you need it - WASM, embedded (Embassy), and unfortunately most of the web ecosystem forces you to use it even if it isn't necessary for 99% of people.

Sync Rust - even multithreaded - is absolutely fantastic at protecting you from mistakes & giving an "if it compiles it works" experience. Async Rust on the other hand is full of surprising and difficult to debug footguns.

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.

Git LFS does actually support file locking. But in general I find LFS to be hackily pasted onto Git and not very good (as with submodules).

Depends on your specialisation. Also immigration laws. But yeah I think in general the job market for programmers is very easy (as long as you are decent).

Even if "isn't that bad" were true, it's hardly a stunning endorsement. I wish Linux aimed higher than "not that bad", but it always seems to hit "only some bits are broken".

Wow, I would love to understand what leads to such insane views. Like, did Rust kill your father or something?

I'm actually serious, why do you have such love for a bad (by modern standards) language like C and such hatred for a great language like Rust?