• 0 Posts
  • 70 Comments
Joined 3 years ago
cake
Cake day: July 9th, 2023

help-circle





  • I can top that.

    I queued for steam. the software. over night.

    Back in 2003 when steam launched, hosting was still a bit tricky, and serving software to a ton of people at once, was not as easy as it is today.

    When steam launched, you could download just the steam client like today, and install stuff via steam. But it was very slow and buggy as hell

    So a couple days after launch, they started to release steam bundled with CS 1.6, so you didn’t need to install it via steam.

    But that was of course a much bigger download. And a TON of people wanted it.

    So they published it via a download service that integrated a queue, so they could still provide some reasonable bandwith to the people downloading.

    I remember that I joined the queue in the evening before bed, let the family computer run over night, started the download before school, and the download was roughly finished when I came back home.

    fun times


  • as a webdev: this is (mostly) not really chrome’s fault.

    It’s the fault of devs not testing or not getting enough time to get something run on more than just chrome.

    For too long the web standards were “eh, it’s stable enough. works on one browser, works on all”. But that only holds true for the basic feature set. When you start using features that are not super common, the browser implementations start to diverge slightly. And that needs to be tested for. But often isn’t