Meetings! Meetings as far as the eyes can see!

There’s no escape, there’s no rest. Life is only meetings now.

Well, round numbers will indeed make the math easier.

Yes, people some times live up to 120 years. You should start at 60.

Yeah, by default kill sends sigterm, and not kill the process at all.

It’s the correct behavior, sending sigkill by default would be harmful. Now take a look at how killall worked in Solaris (before it adopted GNU).

The NT kernel was all built to emulate object orientation (read Smalltalk, not C++) style message passing. That’s because it was the 90s, and it’s the new technology kernel.

So yeah, expect everything to have more flexibility sending data around, and no standardization at all so you can’t have any generic functionality.

Even worse. You’d get from Windows 7 to Windows 11.

Why, indeed?

Yeah, it’s because it’s not the school that is bullshit.

It’s some of the stuff people do there. At the same time, some aren’t. And we are incredibly bad at telling the difference, and worse than useless on doing that at scale.

Just let C++ die already, and stop pretending it’s a reasonable thing to compare other languages with.

If you can’t do it in C, you are better in Java, Python, Haskell, whatever.

The length of variable and function names should be proportional to the size of the code that can potentially call them. And preferably segmented in namespaces, explicit modules, or something like that.

I belong to all of them. Same question.

Or at least say what’s broke…

The worse people are the ones that generate most of the interactions, so every side is biased.

It’s supposed to be stocks trading, not an AWS bill.

Oh, heavyweight Wasm is one of those things better written in Rust.

Intrinsically, one would expect there to be better options. But Wasm is difficult enough that people have been unable to port most tools. That will probably change at some point, but I would not stop anything to wait for that.

All the other options are worse.

But, hummm… Some people do use Rust for software where other languages are a better fit. But usually not in public. You see a lot of libraries helping people to use Rust in GUIs or web applications, but all the Rust rewrites people talk about are for stuff better done in Rust.

Think of it like Haskell’s cast from the Typeable class.

Yes, if somebody sends random stuff, you’ll have to handle a failure, or do the equivalent of returning undefined, what is way easier than properly handling it in TS. What you do from there is up to you.

Not really. The things where C++ used to shine are usually best done in higher level languages.

Rust is a great C replacement.

Well, the author is to blame for the choice of language.

That is, unless somebody forced their hand. What happens a lot in professional settings. Then it’s that other person to blame.

There are only 10 types of people:

the ones that expected a binary joke, and

the ones that expected a ternary joke, and

the ones that expected a quartenary joke, and

…

Nor care to have those reasons in the first place.

And if you press them, you get complete bullshit reasons. But SO will also ban you, while ChatGPT only cares about you paying.

have to check and destructure the result of every function call

Learn how to use enum error types, how error bubbling works, and how to convert between Options and Results.

It’s Rust you are talking about, not Go.