RoyaltyInTraining

I miss the days of barely functioning SLI

My swiss army knife's mechanism has been completely seized up for years now. I hate that there is no obvious way to take it apart for cleaning.

Please don't lump me in with the iPad kids.

Fair point.

No self-respecting UI designer would ever want to work on that dinosaur of a codebase. The GIMP team is simply unable to do what Blender did, even if they made the UI their number one priority.

Isn't C just wonderful?

The worst thing you can do in non-unsafe Rust is perform an out-of-bounds indexing operation, or anything else that panics. The error you get tells you the panic's exact location in the source code, down to the line and column. Meanwhile, C and C++ either don't produce an error at all when accessing uninitialized memory (which is arguably the worst behavior), or it segfaults with zero extra info.

The only way to make Rust segfault is by performing unsafe operations, and those must always be clearly marked.

Best of all, with Tesa you get 50 m instead of just 3M

Except that many other languages have proven that C++ is simply terrible at providing meaningful errors.

I always try to avoid these, unless the application I'm installing has it's own package management functionality, like Rustup or Nix. Everything else should be handled by the system package manager.

I hope they can establish themselves somewhere, I wanna have a good laugh at their opinions every now and then.