6 ms·
It's odd to see an article emphasising backwards compatibility, but not a single mention of Microsoft (I even ctrl+F'd the page source to check!) They've regres
by userbinator 6y ago
It's odd to see an article emphasising backwards compatibility, but not a single mention of Microsoft (I even ctrl+F'd the page source to check!) They've regressed a bit in the recent years but I'd still consider MS the gold standard for back-compat. I have Win32 binaries I last modified over 15 years ago, small (or perhaps tiny - size measured in KBs) utilities that I use daily. They worked perfectly on Win95, and still do on Win10.
I wonder when/if the software industry will ever stabilise. It's possibly the only industry where frequent and disruptive change continues to happen, and is even welcomed by many in it (not me).
- deleted 6y ago[deleted]
- jonchang 6y agoThe article talks about Windows, which is produced by Microsoft.
- junkrat002 6y agoThere was a short shout out to Windows.
- toast0 6y agoYou missed this: > I’ll also give a shout-out to our friends in the Operating Systems business: Windows, Linux, NOT APPLE FUCK YOU APPLE, FreeBSD, and so on, for doing such a great job of backwards compatibility on their successful platforms. I share your desire for stability. I don't necessarily mind frequent updates for security reasons, but I'm getting to the point where if things are changing in big ways often, I'm just not going to use it --- I no longer find enjoyment in running on the upgrade treadmill, it's just work. That said, I don't see a lot of hope for our outlook. Most people don't seem to have a concept of completable software. It would be nice if it were bug free, but getting to the point where the cost to fix bugs compares to the cost of leaving bugs as known issues is doable.
- TwoBit 6y agoOK but he talks about how Android OS has had backward compat for over ten years, but Windows has been doing it far longer and with a much bigger OS and more complex hardware base.
- john-shaffer 6y agoThat's because he has much more detailed knowledge of Android's backward compat story than he does of Windows's.
- bdavis__ 6y ago"completable software". that's the ticket. the maturity to say no more features will be accepted; it is done. for the past 20 years we have been teaching the agile way, that points to the constant churn of requirements, the pivots, and the idea there is always another sprint
- efreak 6y agoLinux code might be backwards compatible, but nothing like windows. I can run pbrush.exe taken from Windows 95 on windows 10, and it works fine. Want to run a 10yo binary on Linux? It's easier to set up a VM with a 10yo Linux release on it. You've hot the source code and you can compile it? Well, tough, the build tools have changed, and some autoconf script has been removed, even from autoconf-archive.
- Craighead 6y agoThis is a bad take, there are immeasurable numbers of binaries from even Windows 98 or Windows 7 that dont run on Windows 10.
- dekhn 6y agoActually, I've kept an ancient statically compiled Mathematica (linux) binary from 2000 and it actually still runs. I had to make some symlinks since X11 font paths have changed. That's a full GUI app with a sophisticated internal kernel. This should be generally true of any well-compiled static binary on linux from 20 years ago.
- physicles 6y agoI went googling for some Raymond Chen examples of the great and terrible things Windows does in the name of back compat, and came up with this old thread: https://news.ycombinator.com/item?id=13450160 https://news.ycombinator.com/item?id=13450160
- asgard1024 6y ago> I'd still consider MS the gold standard for back-compat No way! IBM mainframe (zSeries) is the gold standard for backward compatibility in IT.
- bobbydreamer 6y agoWhen IBM starts to say they are going to deprecate something in mainframe, they will deprecate it in probably 10-12 years time. There will be 3 versions in between and each version will have a much better migration path. If a corporate don't want to take risk, they will be mostly the last ones to migrate, after confirming &consulting all the IBM tech champions, they would start the migration process which would last a year, before they install the new version.
- 1vuio0pswjnm7 6y agoI think NetBSD, or any other BSD generally, is also pretty good with backwards compatibility. I run programs well over 15 yrs old using the latest kernels. If I need to, I can build any of the older kernels, too, because all the code is still readily available (=gold standard). Earliest one predates Win95. Your Win32 binaries sound better than whatever software is being distributed by the companies today.
- jimmaswell 6y agoThe absolute worst in my small experience with it is anything touching the node ecosystem. Try to follow any guide or use any library not updated in the last week and there will be breaking API changes and deprecation warnings everywhere.
- LoSboccacc 6y agotry using four libraries and chances are they require two different version of a build tool installed globally
- kungato 6y agoThe sad part about the js ecosystem is that even the biggest corps like Google can't keep their own js ecosystem stable on the last version. I have a small Angular app with Firebase backend and every time I come back to it to update, the libs are out of sync
- nicoburns 6y agoGoogle aren't very good at this, but Facebook are. Maybe give React a try.
- joepie91_ 6y agoGoogle is notoriously bad at maintaining (or even designing) their open-source stuff. I wouldn't say "even the biggest corps like Google" -- Google does considerably worse at this than many hobbyist maintainers! I just don't use Google libraries anymore, if I can at all avoid it. See also my other comment[1] - Angular is an example of such a magical does-everything framework. [1] https://news.ycombinator.com/item?id=24168279 https://news.ycombinator.com/item?id=24168279
- nl 6y agoTensorflow is another example of this.
- RonanTheGrey 6y agoWe've abandoned an app because of the inability to keep Firebase working on it (JS libraries). Between out of sync Typescript definitions, broken APIs, broken interfaces, "this version of some other dependency works with this version of Firebase thanks to some random transient dependency", it just became too much. We won't use the JS libraries at all anymore. Angular is the only one that has remained even remotely usable, but certainly not stable. It's never as simple as running the upgrade utilities, changing the version, and being done. It ALWAYS takes at least a day to find all the "little" things they didn't feel fit to mention in the upgrade docs. It's aggravating. I genuinely don't like using Google software, at all. I've felt for a long time that Google is coasting on the momentum of the early web and the awe people felt for what they built early on. That hasn't been Google for a long, long time.
- megablast 6y agoMicrosoft bend over backwards for app compatibility, but keep breaking UI compatibility every few releases for no good reason.
- 1vuio0pswjnm7 6y agoThe popularity of Go suprises me when even relatively simple programs measure 10-20 MB or more. It is like Java. Is it even possible to write Go programs measured in KB?