huntrss

I can agree with Arch but recommend Sway ;)

Thanks, the multiplexer idea is actually really good.

Having Said that, In my particular case it was actually my fault.

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.

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.

Ich habe meinen Teil getan ;)

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

So I guess you have to wake up now …

Thanks for the explanation.

That’s a good and relatable Arch Linux meme.

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.

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

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

Thanks for the clarification. This is especially true for libraries that can benefit from async.

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.

I thought as well: should be sway ;)