5 ms·
Imagine you are designing the web server for some hardware like this. You might write it in Go, dockerized and hosted it in Kubernetes in Google Cloud. You mi
by londons_explore 7y ago
Imagine you are designing the web server for some hardware like this.
You might write it in Go, dockerized and hosted it in Kubernetes in Google Cloud. You might use a hosted mongo db and 3rd party auth service.
Now in 30 years time, Google Cloud will probably no longer exist, your database API will have changed beyond recognition, and your auth service has closed down. IPv4 no longer exists and your hardware depends on it so you have to build all kinds of compat layers. You won't be able to get hold of all the packages for your server side code. The Go compiler probably won't even run on an OS 30 years from now. Your staff have retired, and nobody new wants to learn a programming language from 30 years ago.
Maintaining a server side API, even a really simple one, pretty much costs 1 fulltime person forever.
This hasn't always been the case. If you had written your code as a self-contained DOS executable back in 1990, you could still run it bare metal on some of today's hardware, or on any hardware without too much hassle in a VM. Hardware from 30 years ago running in a cupboard probably has a 50/50 chance of still being alive today, and if you had set up 2 backup machines at the time, you'd probably have something working now even with nobody touching it for 30 years, sans the occasional office move.
- geerlingguy 7y agoWrite it in Node.js and it will be obsolete within 6 months!
- whoisjuan 7y agoNahh. Just "npm update --save/--save-dev" and you will be good. /s
- 8fingerlouie 7y ago> IPv4 no longer exists I hope you're right, but i'm not entirely convinced. IPv4 has proven to very resilient. A survey in Denmark of pretty much all ISPs reveals that most, if not all, of the large ISPs have absolutely no plans for migrating to IPv6. Not as "not right now", but as "no plans at all". Some of them have plans for migrating business customers, but no plans for residential. We'll end up with companies running IPv6 and the rest of us stuck on an IPv4 network with a 4to6 gateway. https://ipv6-adresse.dk/ https://ipv6-adresse.dk/
- soneil 7y agoI asked my ISP, and got a template reply telling me they were shooting for late 2017. I asked again in 2018, and received a template reply telling me they were shooting for late 2017. I asked in 2019, and got the same reply ... They've since changed ownership, so I'm curious if the 2020 reply will still be late 2017.
- FeepingCreature 7y agoAt least here in Germany, my ISP doesn't even give me a publically routed ipv4 by default anymore. Ipv6 no problem though.
- p1mrx 7y agoWhat actually is a 4to6 gateway? For example, how would an IPv4 client connect to a 128-bit address like 2606:4700:20::6819:6c0d?
- quintushoratius 7y agoYou contract with a tunnel broker (most, if not all, are free) to give you an address. If you have a lan then you can set up radvd (or similar) to distribute addresses. You may need to replace your router though. Your ipv6 packets head out over a 4to6 tunnel to your broker, and then out to the wider world.
- drdaeman 7y agoNah, that's not the problem/solution, not in the ISP context. It's trivial for most ISPs (unless they have ton of ancient hardware and neglected to upgrade, or if they have very poor and limited peering options) to obtain an IPv6 block and set it up on their backbone network. All the complexity is about providing this to the end users. Depending on your tech stack, you may have no issues, or you may need to replace just about everything (NASes, accounting/billing system, etc - whatever pieces were built with IPv4-only in mind) Source: I worked for an ISP a while ago. We got our servers IPv6 connectivity, in, like, a day. We haven't solved IPv6 end-user connectivity (but it really wasn't a priority then), although was we had a few experimental connections - with lots of duct tape and random end-user issues whenever something was misconfigured (e.g. at the time not every site's AAAA record was actually responding, despite the existence).
- bsanr2 7y agoThis might be one of those "it's a feature, not a bug" dealies. Software is now subject to similar rules of decay and planned obsolescence as hardware and material objects. Guess you just have to go buy a new one under whatever pay structure is the current paradigm.
- londons_explore 7y agoExcept the vast majority of material objects don't decay, or at least don't decay quickly. The hoe I use for de-weeding my garden was my great grandfathers, and is probably 100 years old. It functions pretty much the same as it did when it was new. My father had to put one new screw in it I remember, so it has served its purpose continuously for 100 years with ~20 minutes of maintenance. A similar small bit of software would need recompiling monthly, and rewriting every 10 years, at huge labor costs, just to keep the same functionality.
- grawprog 7y ago>for 100 years with ~20 minutes of maintenance. While I get your point, are you honestly saying a hoe has lasted 100 years and still completely usable to its original standards with absolutely no sharpening, oiling, cleaning or care of any kind other than changing a screw? Stainless steel wasn't exactly common back then, so I'm assuming this hoe was probably iron with a wooden handle? The iron would definitely need to be at least cleaned and dried after use to prevent corrosion and the handle, while probably at least treated at one point, would likely need some kind of maintenance, even if just cleaning, to prevent rot and decay? After 100 years not even a single nick in the blade that needed to be honed out? Never hit a single rock with it? Tree roots never dulled it? Sorry, I know I'm being kind of facetious, but manual tools definitely need care and maintenance if they're used regularly. Even simple ones.
- userbinator 7y agoTo give a better and perhaps more relevant example: The wiring and many electrical devices in my house are over half a century old, yet all the switches and outlets still function perfectly fine.
- legulere 7y agoWorking on software from the late 80s to 90s also come with its challenges. You’ll have a discontinued third party database engine that is no longer maintained and writing files on smb shares wich more or less regularly breaks. It’s probably written by real plumbers and not software plumbers because they back at the time were more available. If you haven’t constantly adapted the code it for sure doesn’t compile with a modern compiler.
- roel_v 7y agoI have (c++) code from the early 1990's that compiles and works fine. People like to crap on c++ and Windows, but for just getting things done and maximum compatibility, I have yet to see better systems.
- l33tman 7y agoSame thing with old 90's linux and most code from that time. I guess the key thing is not the OS or languages but the reliance on external things, a dockerized microservice on a modern cloud is basically on the other end of that spectrum.
- kalium_xyz 7y agoStill better than the frontend which will be declared out of fashion within six months after release.
- emmelaich 7y agoI'm going to guess all those things will be available in 30 years. Want to make a http://longbets.org/ http://longbets.org/ bet of it? PS. longbets, please get https.