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.

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 could actually see myself contributing to Rust kernel code. C code has always been impossible for me to understand, but the Rust part seems to have a more understandable structure

I feel like all C++ does these days is badly and very slowly copy other languages. It wouldn’t be a huge loss.

deleted by creator

Wayland is basically the direct successor to X11. It basically fixes tearing, makes HDR possible, makes scaling way better, and is all-round just better prepared for the future. I’ve been using it for years without much trouble. The only issues I keep having are scripts which expect x11-specific tools to be there, but that seems to be quickly solving itself while people realize that x11 is quickly loosing support. If you want to try it, I recommend setting up a fresh installation of a distro with KDE, Gnome, Sway, or Hyprland, just to make sure all the right dependencies are installed.

Weird that it doesn’t work. The usual way to run scripts on startup is through systemd units though. That has the added benefits of automatically logging all output and letting you control it through commands like systemctl enable <unit name>. It’s a really neat system, and I highly recommend learning it if you see yourself doing this kind of automation more often.

VS Code could really use some work in that regard and I really do feel bad for that person, but this is also just funny as heck

Oh lawd, another thing to check out

Both GIMP 3 RC1 and FreeCAD 1.0 in the same month, damn

People on Hacker News are speculating that they implicitly define forking as “taking the project in a different direction in an independent repo”. The Github TOS say that everyone has the right to create a fork of any public repo in the Github sense of the word. It’s all a huge mess…

They have the audacity to use the term copyleft for that bullshit license… It doesn’t mean anything unless you have the right to fork it.

The USB spec requires one master and one slave device, which is usually decided by which type of connector each side has. USB OTG can bypass that restriction, but I’ve only ever seen it done with micro USB or type C.

The thing it can do best is bewilder developers with it’s strange choices

Integer underflow

It’s a decent language I guess. My main criticism is that the constructor paradigm just isn’t well suited for RAII. I always find myself retrofitting Rust’s style of object creation into my C++ code.