3 ms·
In the embedded space I'm still seeing plenty of 2038-problematic code being produced today. 32 bit microcontroller + unix timestamps = future problems. I thin
by leoedin 5y ago
In the embedded space I'm still seeing plenty of 2038-problematic code being produced today. 32 bit microcontroller + unix timestamps = future problems.
I think this will bite us hard - way harder than Y2K (which happened when software was far less prevalent). There must be millions or even billions of embedded devices out there which are susceptible to this problem - the only real question is how badly they'll fail.
- jamjamjamjamjam 5y agoOh definitely. How long did python3 take? We’re still on ipv4. But lets chill. In 2038 I should be retired but I’ll return from my retirement and make bank
- avnigo 5y agoI can picture it now, coming out of retirement for one last job[0]. Not kidding, that's a movie I'd watch. [0]: https://tvtropes.org/pmwiki/pmwiki.php/Main/OneLastJob https://tvtropes.org/pmwiki/pmwiki.php/Main/OneLastJob
- slowhand09 5y agoSimilar mistakes being made today on different scales. For instance, 3G cellular service is being removed in many places to free bandwith for 5G services. My 2015 automobile has a 3G cellular modem embedded for several services including on-the-air updates. So backwards steps my include plugging in a USB card if updates are needed.