Threads have nothing to do with that and don't increase memory usage due to dependencies.
233 karma · joined November 6, 2019
Threads have nothing to do with that and don't increase memory usage due to dependencies.
That's a difference of more than 6 orders of magnitude :')
And yes, a monorepo is usually the best approach in most cases for a project or even an entire company.
They start thinking they are beyond the normal people and that everything is a joke.
Some subset of features inspired in them are used in some languages, but that has nothing to do with functional programming taking over.
I think for webpages it is the opposite: non-orthogonal in most cases.
If you disable your JS/Ad/...-blocker, and go to pages like Reddit, it is definitely slower and the CPU spikes. Even with a blocker, the page still does a thousand things in the first-party scripts (like tracking mouse movements and such) that slow everything down a lot.
Which, in many cases, is way worse than the alternative pricing model.
Saying it is not going to change is what makes things harder.
Confusion in units is never a good thing.
There is no playing: the error is logged and quite clear, by the application or by the kernel.
Being consistent, predictable and as deterministic as possible is a key feature of reliable software, and paging into swap kills all that.
VSync, if done properly, only adds less than a single frame of latency.
That is 17ms tops for 60Hz, which nobody notices unless you are a pro-gamer on an FPS game. Certainly it does not matter for a pixel editor.
It may be harder than editing a Cargo file, but it is something you do once. They are some of the most mature and tested libraries in the world.
> wgpu will eventually also work on the web, so it's a great option for broad platform compatibility
OpenGL works everywhere today, including the web!
> In terms of efficiency (memory, battery, cpu etc.), the modern graphic APIs have more headroom than the GL-based ones
It doesn't matter for a pixel editor. Even if it did, you would have to do a very good job to beat the driver's GL implementation.
Otherwise, you may end up with something slower or buggier!
> Today, 4K screens are pretty common, and in the future, 144hz monitors will be more and more popular. If I want to render 2d graphics with no latency in those setups, access to the GPU makes things feasible
Perhaps, but again, GL allows you to do that.
I have been running swapless for two decades without any issue.
The fact that you can't achieve the ideal does not mean we should claim defeat.
Not only that, the cost of implementing a Metal frontend is trivial for NVIDIA.
The only thing that works is Metal, on purpose.
However, has Vlang delivered on its promises? There were several heated discussions around that topic in HN.