1093
"Microslop" trends in backlash to Microsoft's AI obsession (www.windowscentral.com)
submitted 10 months ago by to c/technology@lemmy.world
92 comments fedilink hide all child comments
 

Microsoft CEO Satya Nadella penned an AI-heavy blog post to close out 2025, leading to widespread mockery and a brand new moniker for the big M.

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 10 months ago (4 children)

Or you can just not introduce extra instability layers and use native Windows. I can't even fathom the cost of implementation and maintenance of something like that in a company like HCL (200 000 employees, last I checked).

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 4 points 10 months ago* (3 children)

    Haha, are you aware of how many layers of Windows are just backward compatibility hacks? Architecturally Windows has changed a lot since Win98.

    The fact that your 30year old business software is still running is just the fact that Windows has built in patches for some common programming patterns used at the time and someone having insight enough can enable/disable them (mostly).

    Btw, the same for games. Windows detects specific games and re-enables former direct x bugs.

    There are numerous layers of abstraction between your Win32 application and the Kernel, there's no reason they won't work on another kernel.

    Oh. And of course it's badly debuggable and frequently goes wrong.

    I stopped maintaining Windows systems and focused on developing software - it's so effing annoying that things always break out of the blue with a new windows patch versions because MS has bad quality control on their overcomplicated house of cards that is named Windows.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 10 months ago (2 children)

    The fact that your 30year old business software is still running is just the fact that Windows has built in patches for some common programming patterns used at the time and someone having insight enough can enable/disable them (mostly).

    ... which is exactly my point. What's yours?

    Oh. And of course it’s badly debuggable and frequently goes wrong.

    Not so frequently to cause major disruptions.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 10 months ago* (last edited 10 months ago) (1 child)

    Much too frequently, if you need to manage systems for a company.

    THAT is my point.

    I have spent too many nights unrolling and blocking Windows updates just to keep the fucking MS Exchange server happy. Or the damned 8 year old CRM software which writes to places that Windows now blocks access to.

    Yeah it was paid time, but I'm much more happy if the systems I care about just run without hiccups.

    So ultimately I just jailed all the Windows stuff in VMs which I can snapshot and reliably backup, which I can roll back (mostly, as long as it does not involve Active Directory) etc. Windows is inherently unstable, that's my point.

    The ultimate solution was to get out of that job. Yeah, I stilm do use Windows as a daily driver, but single use only, no centralized management and thats kind of OK.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 10 months ago

    Yeah it was paid time, but I’m much more happy if the systems I care about just run without hiccups.

    No such thing exists, especially with legacy corpo software.

    Windows is inherently unstable, that’s my point.

    As a Windows admin for the past ~20 years - nonsense.

  • permalink
  • fedilink
  • source
  • parent