0xDEADBEEFCAFE

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.

I also don't think people should learn to code but that's because I want to limit the available workforce and inflate my wages.

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.

You can tell he's a simple minded idiot because Jabbascript and Go aren't immediate disqualifiers in all scenarios.

I was more thinking along the lines of having FOSS repos that are primarily used by me but which can accept external pull requests by anybody with a Github account.

I like the idea of running my own machine for CI but I don't like the idea of having to become knowledgeable about avoiding exploits.

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 can't define jerking but I know it when I see it.

It's worth considering the original sub rules:

• Original sources only, no manufactured jerk
• No socialjerking (IMO this one is super critical to not just devolve politics spam)
• No crazy people
• No enthusiastic youngsters
• No long unjerk threads
• No implicitly untagged jerk (this will probably be hard to enforce since some replies seem to be serious)

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.