[ivegotnoaccount]

While I understand the reasons why the author think it will go that way, I'm not fully convinced:

- [in average rich countries in 2030] Fast gigabit internet is cheap and everywhere (5G or mesh wifi) => Glad to hear that it will be that way, unlike the 4G for which we got the same promises yet for which I often have issues with my phone in the suburbs of a middle-sized city of a rich country. Also glad to hear ISP issues will be a thing of the past. Sorry for the slight sarcasm here, but this point is a prerequisite for the whole post.

- Outside of work for which expenses are not mine to pay, I'm really not a fan of paying extra for cloud services when I can do without.

- On the "editing code" part => That seem to introduce quite a lot of friction. What if the tool I like to use are not supported as part of this workflow? Which of those support private clouds if I'm working on things that must be kept private?

Last but not least, though this one is more a nitpick of mine than a real complain, but the article uses "localhost" quite ambiguously as sometime it refers to "running things locally" and other as a concept of the whole development machine (editing things locally, having the code on your drive...) and talk about things like OS development: While this may work fine for webdevs, I'm not so sure about other kinds of developers. GUI dev would get added friction, same for work needing low latency (the article talks about edge computing, but that requires paying even more if your structure is small). Maybe that works for Tesla OS devs, but not all companies have what is needed to create a full-fledged cloud environment for embedded developers.