zetaposter

I should add that the concurrent algorithm I described for processing data from a socket, i.e asynchronously read data fragment (i + 1) then do work on data fragment i, would only be optimal if the throughout of the work you do on the data is higher than reading throughout.

Even if the above condition doesn't hold, you would have to be very careful to do better with threads.

Is it just an arbitrary design decision that NodeJS is single-threaded?

async/await is about superimposing useful CPU computations with slow I/O operations.

For example, you would read data fragment D0 from a network socket, and right before doing any work on it, you ask the OS to fetch data fragment D1, etc. This would is faster than reading and working in distinct time intervals. And despite whatever you seem to believe, it would also be faster than reading and working using thread parallelism. Because even if you eliminate the synchronization overhead or you devise a good lock-free algorithm, thread context switches still have a massive overhead, not to mention issues related to memory bandwidth and cache coherence.

Still, how does one gather the nerve to call a feature present in most modern languages, from C# to Zig, a hype?

No author name? No post index?

What's the point of an anonymous block of text published on the internet?

Are you high?

- Sir, you have to install this application, it's available on both iOS and the Google Play Store.

- Do you have a Debian package?

- I beg your pardon?

- My Pinephone runs a modified version of Debian, the Universal Operating System.

- ... What is that?

- Oh fine. I'll settle for a Flatpack then.

- I'm not sure I follow.

-Does Qatar's Law require me to have an Android phone xor an iPhone?

- No ... ?

- Well your Law specification is incomplete and buggy.

you get arrested for obstruction of justice

Um. What the hell?

The linker/compiler discrepancy sounds incredibly weird. This Linux levels of "things don't work together as expected" but how can a uniform system developed by a sole company include nonsense like this?

Yeah ... Just reboot the machine and make me loose all my work, bro.

A text editor without a well rounded GUI story isn't worth it for me. There are all these desperate projects each with their own focus, ranging from "simple graphics acceleration" to "tons of bells and whistles, animations and ad-hoc UI extensions".

UI should be thought out at PRs and issues, but the same people who develop the main core. But they don't have to, because they're making a terminal application, which has its use cases.

But I so no reason why I should type my text in a terminal, when I can use a proper GUI application.

And I'm not even suggesting VSCode, even Emacs is better in this regard, which is what I use.

1. GCC has more backends than LLVM. 2. Competition is good in general. 3. I expect this will trigger inconsistencies between GCC and rustc; because Rust doesn't really have a specification. Which will force both parties to discuss and solve them.