Anonymous, 29 June 2014:

26 years ago I had a problem – text processing was a bit slow. It seemed to add a little megahertz, a few hundred kilobytes of memory, and it will be fine, and finally it will be possible to work normally.

But no, text editors became graphic, megahertz did not help. The damn scratch looked at me in the ward and stopped. Everything eats memory. It would seem, add a little gigahertz and megabyte of memory, and it will be fine, and finally you can work normally.

But no, now the documentation is only on the network. Open the google.docs browser and click there. Everything is written in JS, everything is in the browser, and so it brakes. But this is because the tab shares the core with other tasks (and memory is small). It would seem, you need to add a little 3 gigahertz cores, a few more gigs of memory, and it will be fine, and finally you will be able to work normally.

But no, now the OS will be written on the iascript as well. And the driver. Dedicated to Torvalds, they write drivers on JS, this world went crazy. Although it is understandable - in 20 years Intel will have to somehow sell new processors on 1024 cores (because on 512 cores the text will normally not be redacted - they will come up with something for this), we need to start solving the problem in advance.

And I had to take the first step (26 years ago) to master vim and send everyone to hell.