Ask HN: Is average code getting worse?
I think we are seeing code stick around longer than ever before in the personal computer&#x2F;mainstream era of computing, which has led to more ways to hit buggy, unmaintained code than ever before. Hear me out:<p>If you wrote code for desktop computers in the 1980s, the platform you wrote code for probably didn&#x27;t exist for longer than 5-10 years and the code had to target the CPU&#x2F;arch directly because anything else was too slow. Your C64 library wasn&#x27;t going to be reused on an Amiga or IBM. So any code older than ~5 years old just sort of died off. No support needed.<p>If you wrote code in the late 80s&#x2F;early 90s, the hardware platform was starting to stabilize around the IBM PC, but the GUI layer was in rapid flux and languages were relatively immature - Windows 3 or OS&#x2F;2? Protected mode? Windows 95? 16bit vs 32bit? Would C++ win? Even basic stuff like playing sounds (Adlib? Soundblaster?) or what graphics card to target (EGA? VGA? etc.) was in constant flux. Software lived a short life.<p>By the mid&#x2F;late 1990s, the OS was stabilizing (mostly around Windows 16-bit) and basic hardware for video and sound had shaken out, but now we have the internet on the scene and a whole new round of immature and one-off tools. Remember WinSock? Netscape Navigator 4? Java applets?<p>By the early 2000s, 32bit Windows and OSX were on the scene and desktop software was mature in a way we rarely see anymore, but we were in the last days of single-user desktop software. Momentum was moving towards the web and software designed with the internet in mind. The mature desktop software of the early 2000s would mostly be abandoned as people moved to the internet and expected different things from computers.<p>By the late 2000s, we have the full-on mobile device wars with iOS, Blackberry, Android, Windows Phone, Palm, etc, all fighting over new ways of presenting software to users and all using different software approaches to make that happen. Iteration was incredibly rapid. APIs and languages changed quickly. The UI bar was raised significantly.<p>But around 2011-ish (10 years ago), things really started to shake out. The internet was relatively mature. iOS and Android became a duopoly. Linux became the standard for deploying web backends. Desktop software is largely dead at this point except in niche&#x2F;creative industries. Rapid development moved toward new areas (AI&#x2F;ML, etc) but the foundation was pretty stable.<p>The difference between now and 10 years ago is OSX Lion vs. Big Sur and Windows 7 vs. Windows 10. Hardly a fundamental change. People used Chrome to browse the web then and they still do, now. People mostly used iOS and Android then and they still do.<p>In 2011, web devs were mainly targeting Linux to run Python, Ruby, PHP, and Javascript. HTML 5 was finally a real thing. MySQL and Postgres were hot. Memcached and redis were cool. Some people used Mongo. The Windows crowd was using C# on .Net 3.5. All of those things have evolved over the last 10 years, but aside from Javascript, they are just iterations and are basically what we still use today. (Javascript of course has gone crazy, but that&#x27;s a different story.). Maybe now you target a container instead of a bare machine, but the ideas are basically the same.<p>So my premise is that mass-market computers have broken compatibility less over the past 10 years than ever before. Along the way, more open source code has been released than ever before by a huge factor.<p>We have a situation now where new generations of developers are coming up and writing their new code for the <i>same basic platforms</i> as the previous generation. The old code still more or less works fine, but may have lapsed into unsupported territory. The new code more or less does the same thing, maybe in a slightly different way. There&#x27;s more code than ever to maintain and not enough time to maintain it.<p>So now the number of libraries you can choose between to solve any problem has multiplied to the point where the surface area needing bug fixes and maintenance has become untenable. The hottest Django library that everyone used for file attachment uploads in 2011 has been replaced by 10 newer libraries that half-work and then those were replaced by 400 javascript versions of the same idea. And all that half-supported code is still sitting on Github, just waiting for you to include it in your project and cause yourself headaches. There&#x27;s often no good way to know which library is mostly likely to work reliably and sometimes none of them do.<p>Another symptom of this phenomenon is that when you google about a bug or error, you often get 10 year old Stack Overflow answers that sort of apply but are also totally out of date and lead you down the wrong path. Attempts to update the question get deleted as &quot;already answered&quot;. So now we not only have bugs to fight, but we have the endless perpetuation of wrong answers to long-since fixed bugs getting copy&#x2F;pasted into new code forever.<p>In the past, the constant platform churn let us avoid this problem because the old software would just break and be obviously useless. But now that the basic platform is more stable and software is sticking around longer, we need to figure out better ways to deal with gradual change.