In many ways this is a "classic Microsoft" move — take something that works perfectly fine and replace it with something new but completely inferior and often less featureful. They have been doing this in the consumer space for years and inevitably users get upset but move on.
What I doubt they have considered is the number of businesses dragging-and-dropping mails as EML files and working with offline PST folders and relying on various other invisible features daily that will be completely broken by the transition, not to mention that many businesses likely won't be as tolerant of that breakage as the average consumer will.
This is extremely prevalent in my org. With decades of emails saved on the file system and used as evidence of procedural workflow. It’s now getting annoying as different parts of the org are on different clients so these files don’t always open.
There’s no easy equivalent on the web client or Mac client. Print as pdf sort of does the same thing with a durable record of the email, but takes many more clicks and seconds.
Comically, the people I know who just print out emails and physically file them will be the only ones with real records in years time.
I know there are ways to handle them, but it's still a hassle compared to using a standard format, for which most popular languages have a parser in the stdlib.
> In many ways this is a "classic Microsoft" move — take something that works perfectly fine and replace it with something new but completely inferior and often less featureful.
They’re taking Outlook, which is a Windows-only locally installed piece of software, which can only be extended using Windows-specific APIs.
They’re replacing it with a cross platform codebase which runs on Windows, Mac, Mobile and online in a web-browser (so you can use it on Linux too).
This new version can be extended using web-technology, implemented however you like using whatever language you like, which will not just work on Windows, but on all platform targets (Windows, Mac, mobile, web) seamlessly in a single code base.
Yes. Some features and extension points are going away.
But let’s not pretend we’re getting nothing in return. This is a massive improvement for developers.
Disclaimer: responsible for Outlook addons in company I work for. When applicable, I greatly prefer the new model.
For me it means I’m able to have the same flows and capabilities available regardless of platform or “terminal” I’m using and not have to depend on a particular machine, OS or Outlook “installation”.
There are use-cases which are less supported, like dealing with EML-files, which I too consider a notable loss. Hopefully they manage to bring that back.
> But let’s not pretend we’re getting nothing in return. This is a massive improvement for developers.
If you mean developer end users: those are either by company policy tied to use Windows because corporate antimalware like SEP, Zscaler or WDATP can be deployed and managed remote - or they could just use the web mail and pin that to their desktop as a native app. The “new Outlook” is just a web app, really.
As one simple example among many ways in which the new outlook is inferior, you can't (as for as I can tell and I really have tried) add "message type" as a column. So you can never do the thing which I used to do all the time in classic outlook when processing a full inbox where you click on the message type column, get all the calendar invites in one spot, process them all quickly as a chunk, then go back to processing mail. No. Some pm in microsoft knows better than you. Having that feature would only confuse, so it's been removed.
Last time I tried the new Outlook, I casually pressed “Alt+H, MV, A” to perform an “Always move to the folder…” action, guess what, the new Outlook at the time didn’t even supported the keyboard shortcuts. What is the point of rolling out a new version of your software if it doesn’t even support basic features from the previous version ?
I would prefer MS to be blunt and honest and just say “From now on, it’s Office on the web and suck on it loosers !” Instead of releasing half baked apps that are neither comfortable to use on the web nor on desktop version.
This said, let’s wait and see, MS was able to make a pretty decent Electron App (VS Code) and maybe they can do the same kind of magic with Office apps. I don’t know.
They forget their own history. Wasn't one of the key features of the first versions of Word that switching from WordPerfect was easy because Word used the same keyboard shortcuts?
Yeah I know. And I don’t understand 2 things about it:
1) How is it possible to have a company releasing VSCode wich is a quite viable and ok to use Electron app and on the other hand, releasing some Electron garbage such as Skype or Teams.
2) Why MS discontinued the version of Teams on Linux ?! Isn’t the purpose of Electron App to encapsulate web apps to make them look more native *and* be able to release these *cross-platform* I mean if your Electron app is working for PC and Mac, then, why not releasing it on Linux ?
Replacing Outlook with whatever it is the "New Outlook" is supposed to be is so bad that Microsoft shareholders should get involved. It is a total destruction of value.
It's just bizarre. Probably 80% of corporations are paying Microsoft billions of dollars really just so they can have Microsoft Outlook and Microsoft Excel. What makes it valuable is precisely that it is a "legacy" app people have used and built on for decades.
What does MS possibly stand to gain by replacing it? It's a mature application you can pretty much just leave in maintenance mode, with just a couple new features per release (I guess the new hotness would be adding AI or something.) How does it make sense to spend developer-time building an inferior (from a customer perspective) copy and then eliminate one of the reasons your customers choose you?
Those corporations often pay that money through IT departments that are somewhat distant from how the software is used. They are focused on security, manageability, maintenance, legal requirements, help desk workload etc. If it makes those things easier then it is a superior product for those people.
Also, this kind of move gets Microsoft closer to a world in which a workers laptops is like a Chromebook. Everything running in a walled garden of cloud, electron app, and browser tabs. And Microsoft providing the tooling as part of Azure. In the name of security they get to charge rent on everything. Need a fast GPU or more disk space? Rent it from Azure. Need a developer/ai environment? Rent it from Azure. It is a way of creating artificial scarcity and then charging people to escape that.
It depends. Old Outlook keeps failing me, in ways the new, dumb web app has not (yet):
- Not sending e-mail unless I am restarting it (I added Outbox to Favorites to catch this before hours have gone by)
- Crashing when I try to add an attachment, and loosing my drafted email
- Claiming it's out of memory and hence can't add my signature.
Now, granted, all this maybe due to incompentence at my workplace, or me having "too much email or calendars", but boy does Outlook get in the way of me getting work done. I've run into all of this over the last week, BTW.
I'm not saying you aren't experiencing that, but I've never heard of those complaints before and if they were remotely common there is no way Outlook would be used so much that we are at a point of people complaining it will go away.
I like the versions of outlook from 97/2000, how clean, compact, and uncluttered they are. The core functionality hasn't changed much but there are so many random toolbars and crap plastered all over the place anymore.
It's hard to find a clean spot to click on to just drag a window now.
I'm wondering how many human hours will be wasted in the transition. Every worker that uses a computer depends on email software daily and ends up creating a certain workflow within years of use.
I am glad I am using Thunderbird. All my colleagues are using Outlook, I will see how they will transition, but I will be surprised if it is smooth.
Take one basic feature lacking from the web client - bulk printing all of the emails in a folder. That should be enough to show the web client is not fit for purpose. Not to mention all the organisations relying on extensions.
New Outlook was so messy to use with GMail (what my employer uses) that I’ve switched to Thunderbird. I can’t say Thunderbird is really all that great, but it’s better (and behaves more predictably) than new Outlook.
Generally, desktop email clients (and email in general) feel due for disruption.
I do understand for people relying on it but lets also remember just how much effort it takes to support the very very weird HTML (basically MS Word) that Outlook requires.
To me it seems ridiculous to throw away an entire program which has so much more going on than this one "weird HTML renderer". Rewrite entire program for just this one thing?? Just replace the HTML renderer in Outlook then.
From MS's POV they have just replaced the HTML renderer in Outlook. They just took the opportunity to drop some hard to maintain legacy code (COM compatibility) and "improve" the UX in ways people predictably hate.
New Outlook has actually been decent for me. It started out pretty bad and slowly got better. The big decider will be if they continue that path or stop early in the next two years, not whether or not the app is exactly the old one. E.g. COM add-ins are out but cross platform (what will be browser/phone/web and Windows desktop) compatible extensions will be pushed instead. Some will miss the COM addins after the end of the decade but most will be really glad it's not just a legacy windows desktop that has the addin they need at that point.
Bonus points that New Outlook(tm) can't launch offline. At all. Throws an obscure error that doesn't even say it's from Outlook and fails.
Meanwhile, New Teams(tm)? It'll happily open up offline, let me browse all my chats, everything, while telling me that I'm offline.
Learned this one the interesting way by watching my laptop take an extra long time grabbing a network connection during boot as everything was launching.
I had never heard of that COM integration feature people would miss, but regarding email, calendar and contacts, I've been using Outlook web at work for two years, and it works perfectly fine for my simple use case. Some colleagues insist on using the desktop version or even Thunderbird, and I honestly can't see why they bother. Perhaps Microsoft considers simple use cases like mine to be the norm. That could explain the plan to discontinue support for the desktop client in 2029(!!).
1. Microsoft apps are incredibly featureful: they seemingly never say no to adding a feature. Their bloat and lack of simplicity is one of the main reasons I dislike MS products: I'll take a simple product I can actually over one that makes me think just to get the basics done almost every time.
2. Seemingly the only way MS can step off this treadmill is to completely abandon an existing product and start anew. But even there, users are raising cain about their favorite feature(s) that aren't included in the replacement.
All of that said: people complaining about a five-year window seems insane to me. In five years we're going to be telling our AI assistant to communicate with the other side's AI assistant, come to a mutually beneficial agreement that doesn't compromise on points X and Y but allows leeway on point Z, and let us all know the result when done. And it will be done two minutes after the other side gives their AI assistant instructions.
What I doubt they have considered is the number of businesses dragging-and-dropping mails as EML files and working with offline PST folders and relying on various other invisible features daily that will be completely broken by the transition, not to mention that many businesses likely won't be as tolerant of that breakage as the average consumer will.