Not sure the author's main point - that computers become slower and less reliable over time - holds. HN is snappy and rarely fails to function. I can't remembe

Not sure the author's main point - that computers become slower and less reliable over time - holds. HN is snappy and rarely fails to function. I can't remember ever using a better group communication tool. The author's website is also snappy and worked perfectly to let them express their view and for me to read it. A lot of software I use today is software I wrote myself and that works in the browser. It is reliable and snappy too. And I write more and more of it with the help of LLMs. Just yesterday, I wrote an image editing tool with a very special feature set and was amazed how much faster I was able to implement features in perfectly elegant code via this approach: 1: Give the existing code to an LLM and instruct it to add a feature. 2: Test the feature to make sure it works. 3: Go through the changes via git diff in one window and clean them up in another window in VIM. 4: Test again. 5: Commit. 6: Goto 1 This way, the development of this new tool was multiple times faster than if I had written it manually. To me, the main questionmark about the future of computers is how browsers will develop. The one thing I am missing is that currently no mobile browser supports the File System Access API. On desktop, Chrome does. And that allows users to securely safe their data on their own device. So web software does not have to be like "All your data needs to be in the cloud". Chrome already works on bringing that to mobile. Then the current state of affairs on Desktop and Android will be perfect from my perspective. And all I hope for is that Safari follows. So that iOS users can comfortably use my software too.