nchi3

In Norway it was 3 deaths in 130000 vaccinated if I recall correctly. But yeah, Norway definitely seems like an outlier.

How is this relevant in the least? They haven't "come for" anyone because of an opinion or race, but for actions.

It's more like "First they came for the murderers".

> Additional complexity in your apps is not.

My point was that it really isn't that much additional complexity. 99.9% of the time, the main difference is that you'll have to write "await". You don't really need to know that there's a state machine hiding beneath.

I haven't used async in Python, but I'd bet you don't really _need_ to understand every single one of those concepts, unless you're developing something very niche and low level (or an interpreter). If you do need to know it, I'd argue that it's not a great abstraction; you definitely don't need to know that implementation details and concepts in either C# or Rust to use async/await.

Or, you just take the initial leap and write async from the start. For languages with decent abstractions such as async/await, it really isn't hard when you've done it for a while, and I'd make the same argument as one of the parent posters in that it's great "documentation".

K8s is brings way more complexity and headache, so it's kind of funny that you suggest that before using async/await.

That's probably because Slack isn't the "main" communication where you are. Where I work it's the opposite, people answer slack but don't notice emails, because Slack is how we're "supposed" to communicate within the company.

Medical condition is a very different thing from a mental illness though. I'm quite sure there aren't mental _illnesses_ which last 1-2 days like Stockholm syndrome does.

>Suggesting everyone using C++ isn't capable of properly evaluating it (which the comment author can clearly tell from the outside, for every use case) is "not derogatory"?

I see it more as "I wonder if they have given other languages a chance?". There's definitely a lot of C++ devs who aren't giving for example Rust a try, and don't see the negatives of C++ because they haven't experienced anything else lately.

If anything, it was derogatory towards C++, not the devs.

Yeah, hence high level non-GCed language. Using heap allocated linked lists is rarely the way to go if you're not developing for embedded.

However, if you're developing for embedded you'll probably want to be familiar with unsafe either way if you're going to use Rust.

Regarding self-referencing: Rust encourages you to design differently, which I've found leads to nicer and more thought out designs most of the time. Not all algorithms are possible (or efficient) without it though, and for those you'll have to use unsafe if you _really_ have to implement them yourself.

Self-referential data structures are a code smell in non-GCd languages, and I think I have neither used or written a doubly linked list since university.

You can do both in unsafe rust though. But you probably shouldn't no matter what high level non-GCd language you use.

/Another ex-cpp-master-race guy who has been impressed with Rust

Look up sealed classes if you're using Java 15. There's no proper exhaustive pattern matching for them yet though, but that's coming in a future version.

Stockholm syndrome isn't a mental illness, nor is it derigatory.

Spotify employees started working from home in March though, just like most tech companies. Yes, some people still go to their offices, but they are small minority unless they have a job where they can't work from home.