Ah, that example is demonstrating an internal mechanism used to ensure the high-level asynchronous API calls take at least one tick of the event loop to complete.
There is no `result` variable - I was just attempting to convey that "some async stuff happens, then it waits if we can't verify that it's not the same tick as when the call started". The "async stuff", in the actual implementation, is sending or receiving.
Linux graphics you mean? The compute ones are fine.
It's not as much of an issue about supporting old versions, it's just that new versions of Linux breaks the drivers since they don't know what's in it.
But such servers have no need to, for example, suspend and resume correctly. Or handle hot-plugging of displays correctly. Or install updates in a completely reliable manner. Or include the 32 bit support needed for Steam to work.
Not sure I agree about Svelte's bundle size being a problem, but v4 already improved tooling quite a bit by switching to JSDoc and judicious type export limits. Intellisense for library functions, the ability to drill down seamlessly from your code to library code, and helping IDEs choose the correct import have all greatly improved.
