We have competent design tools running in the browser now… we’re doing fine.
We have competent design tools running in the browser now… we’re doing fine.
[1] https://support.microsoft.com/en-us/office/turn-off-office-a...
[2] https://docs.microsoft.com/en-us/troubleshoot/windows-server...
https://www.extremetech.com/computing/261148-modern-computer....
Going through dozens upon dozens of layers (ever increasing) just to draw a rectangular box with some text inside is creeping complexity.
So, yes, I am fine on my beast machine, still the direction is wrong for me.
20 years ago software was running locally. Now, it must communicate with mothership for every action you make. Tools running in the browser are slow, because they use the browser to get user input or to display information.
In particular, this image offers a nice comparison of some newer and older pieces of software: https://pavelfatin.com/images/typing/editor-latency-windows-...
That said, typing isn't everything, but there are stark differences even in something so basic.
People noticed that the windows built-in terminal app has noticeable latency, and when the WSL1 team implemented their own terminal app, they ended up with much better latency [1]. I wonder if this input lag test was done using the built-in terminal or this WSL1 terminal.
It barely chugs through on my 2018 iPad Pro. Every click takes actual seconds to load.
In what world was anything faster 20 years ago? Do these readers not remember waiting minutes for their computer to start up?
It took like 3-5 seconds at least, growing up