• 0 Posts
  • 49 Comments
Joined 10 months ago
cake
Cake day: June 9th, 2024

help-circle
rss

  • See, IBM (with OS/2) and Microsoft (with Windows 2.x and 3.x) were cooperating initially.

    Right-ish, but I’d say there was actually a simpler problem than the one you laid out.

    The immediate and obvious thing that killed OS/2 wasn’t the compatibility layer, it was driven by IBM not having any drivers for any hardware that was not sold by IBM, and Windows having (relatively) broad support for everything anyone was likely to actually have.

    Worse, IBM pushed for support for features that IBM hardware support didn’t support to be killed, so you ended up with a Windows that supported your hardware, the features you wanted, and ran on cheaper hardware fighting it out with an OS/2 that did none of that.

    IBM essentially decided to, well, be IBM and committed suicide in the market, and didn’t really address a lot of the stupid crap until Warp 3, at which point it didn’t matter and was years too late, and Windows 95 came swooping in shortly thereafter and that was the end of any real competition on the desktop OS scene for quite a while.











  • I’m a fan of the Bambu printers because they just simply work.

    You want to print something, they print something, done.

    If you want to fiddle, then they’re the wrong printers, but if you want to model shit and make things then they’re really hard to beat right now.

    And, yes, I have reservations about the closed sourced nature, but honestly ask yourself: are you going to contribute to the code? Are you going to build your own firmware to run on your printer? If the answer is no, then that’s probably not really a concern that should be driving your decisions.





  • The best way I’ve heard that described is that for the Bambu stuff, you spend your time fiddling with the thing you want to print, not your printer.

    I love my p1p (and it’s several thousand hours and 100kg of filament into ownership and all I’ve had to do is clean the bedplate and replace a nozzle), and really wish there was anyone who was making an open-source printer that’s as reliable and fiddle-free as this thing has been.




  • Honestly, I’d contact their support and ask what their processes are and what timelines they give customers for a response/remediation before they take action.

    Especially ask how they notify you, and how long they allow for a response before escalation to make sure that’s something you can actually get, read, and do something about within.

    It might not be a great policy, but if you at least know what might happen, it gives you the ability to make sure you can do whatever you need to do to keep it from becoming a larger issue.


  • This new uh, tactic? of going after a registrar instead of a hosting provider with reports is a little concerning.

    There’s an awful lot of little registrars that don’t have any real abuse department and nobody is going to do shit other than exactly this: take it down and worry about it next week when they have time.

    It really feels like your choice of registrar is becoming as much or more important than your choice of hosting provider, and the little indie guys are probably the wrong choice if you’re running a legitimate business as you’re gonna need one that has enough funding and a proper team to vet reports before clobbering your site.

    On the OTHER hand, Network Solutions is just took down DigitalOcean for no reason, so maybe they all suck?