• 0 Posts
  • 39 Comments
Joined 1 year ago
cake
Cake day: August 7th, 2023

help-circle

  • The Fediverse is a bit more like the old USENET days in some regards, but ultimately if it ever becomes more popular the same assholes that ruin other online experiences will also wind up here.

    What made the Internet more exciting 30 years ago was that it was mostly comprised of the well educated and dedicated hobbyists, who had it in their best interest to generally keep things decent. We didn’t have the uber-lock-in of a handful of massive companies running everything.

    It’s all Eternal September. There’s no going back at this point — any new medium that becomes popular will attract the same forces making the current Internet worse.







  • I’m not sure what’s keeping Microsoft and ibm from Open Sourcing all the rest of the DOS versions as well — the 3.x series was very influential, 5 added disk compression, and 6 was the most modern of them all. I can’t remember if Stac’s lawsuit against Microsoft would require them to take out the disk compression parts (although AFAIK the relevant patents are probably long expired now), but even if that’s the case having these available as OSS would also be useful — even if only for a historical context.


  • To put things into context, IBM didn’t get ripped off in any way (at least not from DOS - the whole IBM/Microsoft OS/2 debacle is a different story). The earliest PCs (IBM PC, IBM PC XT, IBM PC Jr., and associated clones) didn’t really have the hardware capabilities needed to permit a more advanced operating system. There was no flat memory model, no protection rings, and no Translation Look-aside Buffer (TLB). The low maximum unpaged memory addressing limit (1MB) made it difficult to run more than one process at a time, and really limits how much OS you can have active on the machine (modern Windows by way of example reserves 1GB of virtual RAM per process just for kernel memory mapping).

    These things did exist on mainframe and mini computers of the day — so the ideas and techniques weren’t unknown — but the cheaper IBM PCs had so many limitations that those techniques were mostly detrimental (there were some pre-emptive OSs for 8086/8088 based PCs, but they had a lot of limitations, particularly around memory management and protection), if not outright impossible. Hence the popularity of DOS in its day — it was simple, cheap, didn’t require a lot of resources, and mostly stayed out of the way of application development. It worked reasonably well given the limitations of the platforms it ran on, and the expectations of users.

    So IBM did just fine from that deal — it was when they went in with Microsoft to replace DOS with a new OS that did feature pre-emptive multitasking, memory protection, and other modern techniques that they got royally screwed over by Microsoft (vis: the history of OS/2 development).


  • As someone who has done some OS dev, it’s not likely to be of much help. DOS didn’t have much of any of the defining features of most modern OS’s — it barely had a kernel, there was no multitasking, no memory management, no memory protection, no networking, and everything ran at the same privilege level. What little bit of an API was there was purely through a handful of software interrupts — otherwise, it was up to your code to communicate with nearly all the hardware directly (or to communicate with whatever bespoke device driver your hardware required).

    This is great for anyone that wants to provide old-school DOS compatibility, and could be useful in the far future to aid in “digital archaeology” (i.e.: being able to run old 80’s and early 90’s software for research and archival purposes on “real DOS”) — but that’s about it. DOS wasn’t even all that modern for its time — we have much better tools to use and learn from for designing OS’s today.

    As a sort of historical perspective this is useful, but not likely for anything else.


  • AWS already had to effectively do this. AWS only exists in two regions in China because they licensed much of the AWS software to be run by a pair of Chinese-government affiliated ISPs inside China (that is, Amazon doesn’t run AWS in either of its China zones — it’s run by a pair of Chinese companies who license AWS’s software).

    This is why the China AWS regions are often quite far behind in terms of functionality from every other region (they either haven’t licensed all the functionality, they don’t keep up-to-date at the same cadence as Amazon, or Amazon is holding certain functions back), and why you can’t really access them from the standard AWS console.

    So in effect, Amazon did have to give their software to Chinese-government affiliated companies in order to continue operating in China.



  • An honest review isn’t what’s going to kill their business. Even a bad product in and of itself isn’t necessarily what could cause the death of their business — it’s their not adequately tempering consumer expectations. From the sounds of it, they’ve oversold what the product can actually do, and are charging a price based on this fantasy.

    If you’re honest in your marketing as to what your product can actually do, and charge a corresponding price then consumers and reviewers may be more forgiving. Where companies like this one which are doing fairly experimental stuff fail is when they over-promise and under-deliver. And reviewers will always take them to task when they do that.



  • Got a T-Mobile eSIM while travelling in the US last year to get around this. The eSIM was a great deal (can’t remember the specifics, but pretty cheap with a decent amount of data). I was making two trips to California and Georgia in the same 30 day window, so it was useful to have.

    The only downside was that I couldn’t activate the eSIM before getting to the US, and LAX didn’t appear to have any WiFi while we were there (not sure if that was generally true for the time, or if it was just offline). So I wound up having to roam to get the eSIM, and to get a text message from the shuttle that was picking us up from the airport (as I had to give them that in advance, and didn’t know what my US number would be until I got there).

    Still saved us some money, but it was a bit of a PITA to activate with no WiFi available at the airport.


  • Yaztromo@lemmy.worldtoProgrammer Humor@lemmy.mlHow do we tell him ?
    link
    fedilink
    arrow-up
    13
    arrow-down
    4
    ·
    9 months ago

    Honestly, I hate these memes. As an old school hacker/programmer who has been doing this for many decades, I can usually just start thinking in code and start dumping out everything I need from my brain through my fingers to the keyboard. I never copy-and-paste code from online for something I’m coding (I don’t count something like copying a script to do a quick shell task of some-sort; for something like Amazon’s directions for installing Corretto I’m not going to type all that out manually; and I don’t really consider that “programming”).

    But as a tech manager (and former University comp.sci instructor), I know this happens more often than I’d prefer. But some of the worst code I’ve had to review has been copy-and-paste jobs where the developer didn’t understand the task correctly and jammed in something they found online as a quick solution. I get that I started in a generation where you had to understand the problem and code the solution from scratch (because the Internet crutch wasn’t what it is today) — but the fact that so many younger developers revel in the fact they copy-and-paste code on the regular makes me sad.