• 0 Posts
  • 5 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle


  • withabeard@lemmy.worldtoScience Memes@mander.xyzCFCs
    link
    fedilink
    English
    arrow-up
    1
    ·
    7 months ago

    Depends on the “they”…

    But generally, back in the day data storage, memory and processing power were expensive. Multiple factors more expensive than they are now. Storing a year with two digits instead of four was a saving worth making. Over time, some people just kept doing what they had been doing. Some people just learned from mentors to do it that way, and kept doing it.

    It was somewhat expected that systems would improve and over time that saving wouldn’t be needed. Which was true. By the year 2000 “modern” systems didn’t need to make that saving. But there was a lot of old code and systems that were still running just fine, that hadn’t been updated to modern code/hardware. it became a bit of a rush job at the end to make the same upgrade.

    There is a similar issue coming up in the year 2038. A lot of computing platforms store dates as the number of seconds since the beginning of 1970-01-01 UTC. As I type this comment there have been 1,710,757,161 seconds since that date. It’s a simple way to store time/date in a way that can be converted back to a human readable format quite easily. I’ve written a lot of code which does exactly this. I’ve also written lot of code and data storage systems that store this number as a 32bit integer. Without drilling down into what that means, the limit of that data storage type will be a count of 4,294,967,296. That means at 2038-01-19 03:14:07 UTC, some of my old code will break, because it wont be able to properly store the dates.

    I no longer work for that employer, I no longer maintain that code. Back when I wrote that code, a 32bit integer made sense. If I wrote new code now, I would use a different data type that would last longer. If my old code is still in use then someone is going to have to update it. Because of the way business, software and humans work. I don’t expect anyone will patch that code until sometime around the year 2037.



  • Microsoft did this with browsers.

    HTML was a thing, that was implemented by other browsers at the time. Netscape Navigator (the precursor to Firefox) was a thing that already did HTML well. It could access the world wide web, and was the defacto standard.

    Microsoft introduced internet explorer, bundled with Windows. At first, internet explorer was not as good/complete/compatible as Netscape Navigator. Over time, it got better almost to parity. But it also added new features, features not in the HTML specification. They were not added to the specification, and how IE would use those features was not made public. So Netscape could not implement them.

    Users started to expect those features.

    Over time, more webpages would break on Netscape than on IE. Web designers wanted the fancy new features of ie. So users moved away from Netscape.

    If only a number of technical users care about something, that the “mainstream” (for want of a better word) doesn’t care about. Then things work less and less for the techies.

    Meta could do the same with the Fediverse. As they already have market domination in other markets, they can introduce a lot of users to our “safe space”. But be real if posts stop working and you as a techie knows it’s because Meta have done something funky, Grandbob Jim isn’t likely to care. Grandbob Jim will continue to use what “works”. And some of the less techie of us will be forced to move to the MetaFediVerse to talk to our Grandbobs.