I also personally changed to the EUPL where I would normally use a GPL. As I understand it the EUPL aligns more closely with actual (European) law. Recent events have persuaded me to alugn more with that than theoretical US law.

That depends on the license. Music is also available on Youtube without authentication requirements but I don’t think you can just download those and do whatever you want with them.

Everything Herb Sutter says about the popularity of C++ should be taken with a huge grain of salt.

Right, so you can’t “enforce” a return from the function.

shouldn’t Rust enforce returning from function

How do you enforce returning from exit or a function with a loop that never terminates?

You’re kidding yourself if you think most people in this thread are actually programmers. Most people here wouldn’t know the difference between C and Rust code if they saw it, let alone be able to write anything in either language.

We have already accomplished a great deal. Compile-time C++ is already fully free of UB, which means a huge chunk of real-world C++ is already UB-free today.

This statement is so categorically ridiculous that I have no choice but to assume that Herb Sutter is deliberately trying to mislead people. I would be very surprised if even 5% of “real-world C++” occurred at compile time. In fact, I would be very surprised if even 5% of “real-world C++” was valid constexpr that just ran at runtime.

Just self host an open source runner like woodpecker and you’ll never have to move again

How painful is the setup and general maintenance/security?

I’m considering the idea but I just don’t want to deal with people abusing exploits in the actions that give them access to my LAN.

I defiantly had a far easier time learning c and apply my existing programming knowledge. Getting my head around the borrow checker was one hell of a pain in the ass.

What specifically was difficult to understand about the borrow checker? Much of what the borrow checker requires you to do are things that you still need to do in C just without compiler support.

I have used cargo ramdisk before with success.

According to this this slideshow:

At a fundamental level, this is the state of terminal emulators today as I saw it. You have fast terminals, feature rich terminals, and native terminals. You can pick at most two properties to have.

Ghostty aims for – and in my opinion already achieves – all properties.

Also, calling out the warning signs, my bar for a native platform experience is that the app feels and acts like a purpose-built native app. I don’t think this bar is unreasonable. For example, I don’t think it’s unreasonable to say that Alacritty is kind of not native because new windows create new processes. Or that Kitty is kind of not native because tabs use a non-native widget. And so on (there are many more examples for each).