It's so human how - instead of admitting its error - it's pulling this bs right out of its ass 🤣

Her life is normal. The depiction on the television is fiction. No reason to be envious

I think the article is ok, and yes I read it ;)

I think the title is unnecessary click-baity, because there are some relevant truths to it.

Most relevant truth us, that a lot of applications won't need async since they are not large enough, not IO bound etc..

I think one of the misconceptions in this article is, that the author arguments that you need to be an Amazon or google to benefit from async. This is not completely wrong but, as a software developer in the embedded system industry that I am, I must say it is also very relevant for embedded systems.

If someone read the article and is unsure about async, I can recommend these two articles that provide insights "from the other side" these means devs that actually find async relevant and beneficial:

https://notgull.net/why-you-want-async/

https://without.boats/blog/why-async-rust/ The article from boats is absolutely worth it. Even if you are an async sceptic.

Finally regarding the introduction of async APIs and abstractions into any code base:

Creating an async application or sync application is an architectural decision. And since architecture is the sum of all decisions that are hard to change (I think this is from Martin Fowler) thus decision - async or sync - is hard to change and one must live with it.

Yes, there are languages like Go or Erlang that resolve this async vs. sync problem, they come at a cost (having a runtime, at least Go has one afaik, I no nothing about Erlang). And choosing a particular language is also an architectural decision and hence hard to change.

The first-class dev and debugging experience, is this with Visual Studio or Rider as IDEs?

Because I currently do C# with Linux + neovim + Omnisharp as Language Server and it is really slow and bad. Do you have any tips?

Ich habe meinen Teil getan ;)

Ich Frage much nur: verstehen die wirklich nicht wie das Internet und Internet Communities funktionieren?

Same here. 10 years on my laptop and it broke only once: I accidentally closed the terminal where the initramfs was installed. So my mistake. I could fix it by using an arch install on an USB and my knowledge of how to install the system, since I did it myself, by hand.

Rust and Zig are currently my favorite languages.

Automotive, Aerospace. Everywhere where you need safety qualifiable software (safety as in ISO 26262 or equivalent)

Didn't read all, however, thanks for sharing. Made me laugh and I certainly needed a good laugh today

I ask the most important question:

Which Linux Distribution are you gonna use?

And before you answer: There are wrong answers 🤪

I live in one of many streets in Germany named after Anne Frank. Banning an illustrated version of Anne Frank's Dairy is horryfying to me.

They used to cause anxiety in the past as well. But there was a window where - at least I - didn't fear them. Main reason why I still think they are necessary are security patches. But I do fear updates due to their tendency in breaking things.

It's obviously not giving 110% as it should

Poor Snoopy ...

Why did you need to disable secure boot? To boot from USB?

I am looking forward buying a framework laptop. Still using an ASUS from 2011 but it is getting slow and I am starting to have issues, e.g., my touchpad seems to have broken down.

I can relate ...

Maybe yes maybe no.

I still don't envy a situation in television that is so unreal like a prince (or something similar) dancing with his dream woman (I assume). It's so surreal tgat I can't take it serious and can't envy it.

I agree this is not a meme. There is another community for exact this kind of discussion. I left thus other community exactly because of this kind of discussion. I hope I don't have to leave thus one as well.

I can agree with Arch but recommend Sway ;)

Not so much relevant for production use cases but from an educational point of view: whorl is pretty great. One file that explains async runtime basics from top to bottom. The cleverness of doing this in one source code file is remarkable.