To not much official fanfare on Thursday, the Windows operating system turned 40 years old, marking four decades since Windows 1.0 debuted in the United States on November 20, 1985. Its midlife milestone comes with a crisis, though. Diehard Windows users are switching to Linux for a variety of reasons.

For one, gaming is finally better on Linux machines, which makes the moat Windows dug for itself a little more passable. Add to that the end of support for Windows 10 in October, the growing frustration among power users about Microsoft Recall, and the growing number of polarizing features, and power users are finding plenty of reasons to make the switch to Linux.

It’s unclear if the wave of Windows power users loudly moving to Linux has crested yet, or if this is just the beginning. That said, the past year has seen a flood of articles like this one, scores of posts on Reddit, and YouTube videos documenting and occasionally evangelizing the conversion to Linux.

  • Wooki@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    16 hours ago

    Your claim with the api is outright wrong. The difference is between client side and service only api the rest is hyperbole. That gap is MASSIVE functionally. Client api is responsive, fast, access to local OS and local hardware. Service side has its place, but its service limited only. Severely limits access to other services which is very important when moving data.

    You have conflated User Experience with User Interface. I didnt say UI for that obvious reason. The experience matters a lot. Having to open and process the same flow of task from one app to another app breaking concentration is bad fucking UX. Losing context is bad UX the list goes on. it reduces accuracy, & performance and ultimately productivity. Something as simple as classing becomes simple when the context of the conversation is very easy to get and more accurate when you dont duplicate an entire chain.

    • Alaknár@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 hours ago

      Client api is responsive, fast

      If it’s done right. So, just like an app.

      access to local OS and local hardware

      I’m already speaking for switching from Outlook with API to apps, you don’t need to sell it to me!

      Severely limits access to other services which is very important when moving data.

      Read this again.

      You’re advocating for moving data via Outlook. Mate, I hate to break it to you, but this is peak insanity!

      You have conflated User Experience with User Interface. I didnt say UI for that obvious reason

      UI is integral to US. That’s why I mentioned it.

      Also: “familiar UX” makes little sense. People don’t get “familiar” with UX, the UX is either good or bad. That’s why I mentioned both.

      Having to open and process the same flow of task from one app to another app breaking concentration is bad fucking UX

      Here’s the thing: it shouldn’t be “teh same flow of task from one app to another”. Modern apps tend to encompass the entirety of a process.

      Something as simple as classing becomes simple when the context of the conversation is very easy to get and more accurate when you dont duplicate an entire chain.

      That’s what ticketing systems are for.

      In general: using email for business processes must die just as much as using Excel for a “database”.