223
Linux comes for Windows at 40 — and gaming can't save it (www.makeuseof.com)
submitted 11 months ago by to c/linux@programming.dev
64 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] 0 points 11 months ago (12 children)

It's not "bollocks", it's a fact. Lots of businesses that go cloud replace API calls with external apps. People used to do human resources management via Excel and Outlook with macros and plugins, now they use BambooHR or Workday, for instance.

Of course there will also be lots of businesses that don't, but I haven't seen that in the last 13 years of working in the field. And in that time I went through companies as small as 200 users to as large as 180 000 users.

That is being cut off in an anticompetitive move by Microsoft

Agreed. Kinda. Email should be email, nothing else. It's not secure enough for anything else. If you want fancy features, get a fancy app that can do them, maybe have it send notifications to your mailbox, that's it.

It allows for information management and automation to be verified by people with simplicity and a familiar UX

With this I don't agree. Again, email is email - third party (or custom) software can do these things infinitely better. As for "familiar UX" - come on, it's 2025. If someone can't handle a new UI/UX, they shouldn't be doing office work.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 12 child comments
    •
  • [–] 1 point 11 months ago* (11 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 11 child comments
    •
  • [–] 0 points 11 months ago* (last edited 11 months ago) (10 children)

    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 UX. 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".

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 10 child comments
    •
  • [–] 1 point 11 months ago* (last edited 11 months ago) (9 children)

    So you're advocating for slowing process, bad user experience, and duplicating shitty email functionality in every app to receive and send email limiting communications. Got it.

    people dont get familiar with UX

    Yes they do. Duplicating email into other systems that doesnt have anywhere near the same functionality and flow as their dedicated email app which is designed for email is frustrating, and restricts communication.

    ticketing system

    Wtf does classing have to do with ticketing systems. It applies to records management, project management, legal case management, the list goes on. It applies to most business

    using email for business process must die

    Oh my sweet summer child. I've got news for you: email is HOW business is conducted. That is not going away any time soon.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 9 child comments
    •
  • [–] 0 points 11 months ago (8 children)

    So you’re advocating for slowing process, bad user experience, and duplicating shitty email functionality in every app to receive and send email limiting communications. Got it.

    Yeah, if you ignore everything I said and invent your own stuff, then this is exactly right.

    Yes they do. Duplicating email into other systems that doesnt have anywhere near the same functionality and flow as their dedicated email app which is designed for email is frustrating, and restricts communication

    I'm still trying to wrap my head around the fact that you think that email is somehow the peak of UX.

    Could you give me an example of a process that's much better handled via API to Outlook than literally anything else?

    Wtf does classing have to do with ticketing systems. It applies to records management, project management, legal case management, the list goes on. It applies to most business

    Wow, these all sound like important things that should definitely not be handled via Outlook. But, again, I might be super wrong - please give me an example, because maybe we're talking about two different things.

    Oh my sweet summer child. I’ve got news for you: email is HOW business is conducted. That is not going away any time soon.

    Are you from the US?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 1 point 11 months ago* (7 children)

    peak of UX

    Good UX.

    give an example

    Already have provided 1 of many examples: classing. Applying a type to the communication relevant to the business. To the process it could be scope, direction, decision ect. This can route, tag, extract, modify and move/copy messages automatically to target services.

    Just to be clear I am not advocating for building Microsoft Lotus notes (Teams), not at all. Quite the opposite.

    However jumping between apps is how mistakes are made, and evidence lost from laziness or "too busy". IMO Email communications should only be handled by Outlook or a dedicated email client that has the depth of functionality for good communication. Addins provide the middleware between different products and services to integrate them. It can even be completely transparent to the user.

    Bringing this back to the topic. The shift to the web only Outlook means no more BYO libraries, no more .net , no more OS api, no more COM api. These provide an enormous amount of capability for addins to leverage and provide integration. Now with website Outlook, the api is incredibly limitted and entirely controlled by Microsoft, there is no BYO libraries and connectivity and those existing web api's can and are removed at whim removing the ability to conduct business on 365.

    So if someone can build an app like Outlook that has rich email, calendaring and pure depth of functionality that it has. This would be a massive barrier removal if not in my oppinion the last barrier for mass business FOSS adoption.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 0 points 11 months ago (6 children)

    Already have provided 1 of many examples: classing. Applying a type to the communication relevant to the business

    This is not an example. What type of communication? Are you classing emails? Are you classing internal documents? Are you classing marketing material? Are you classing internal comms?

    To the process it could be scope, direction, decision ect. This can route, tag, extract, modify and move/copy messages automatically to target services

    This description screams "use a proper ticketing system" to me but, again, I feel like I don't have enough information about the process you're talking about.

    However jumping between apps is

    A badly designed process or the wrong app.

    So if someone can build an app like Outlook that has rich email, calendaring and pure depth of functionality that it has. This would be a massive barrier removal if not in my oppinion the last barrier for mass business FOSS adoption

    Again, this all sounds like you guys are using the wrong tools for the job, but would need to hear more details.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 1 point 11 months ago* (5 children)

    use a proper ticketing system

    Im done. You have utterly no idea what you a talking about. Fundamental information management concepts are foreign to you.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 0 points 11 months ago (4 children)

    And you seem to think that "ticketing system" can only be used for IT incident management. It's like you're not aware of integrations with (or flat out specialised tools for) knowledge management systems, HR systems, CRM systems, asset management systems, and a billion others.

    You still didn't give me any example of a process you had in mind so, yeah, I agree, the discussion is pointless.

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

    Great story never said that.

    Go do a course in basic information management.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 0 points 11 months ago (2 children)

    No need, we have a tool for that. One that's decidedly not email....

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

    No doubt its a ticket system

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 0 points 11 months ago

    Yes. It's a system where we can create an entry for every case, monitor it, log all activity, manage who's responsible, who needs to approve, and who owns which parts of the process, automate everything that needs automating, and - in case of an audit - present the entire lifespan of the case, from start to finish to the auditor.

  • permalink
  • fedilink
  • source
  • parent