> Outlook is based on WebView2, and like all web apps, it’s slow
Fastmail also has a web based email client, which is as fast as (if not faster than) Outlook Classic.
The new Outlook is just bad. Load order is wrong, it renders everything on every window, loads unnecessary data, etc. Plain annoying.
IME running the new outlook in an actual web browser (through outlook.office.com) is waaay faster than the heavy (heh) client.
Bonus points for it running fine on Linux, too. I understand there are some missing features compared to the old one (can't recall which), but for basic corpo emailing it works perfectly for me.
I now have 0 reasons to use Windows at work, so, for once, I'll nonironically cheer MS for a job well done!
> I understand there are some missing features compared to the old one
There are some people that use Outlook for...well I'm not sure what but things that go way beyond email and calendar. I've been using the web app for several years now, it's fine. When I was new in IT, I always struggled to see what the big deal was with Outlook desktop. The web mail has folders, rules, shared mailbox support, integrated calendar, etc.
What more do you need out of email?
Well, turns out a lot. People treat email has a permanent data store. I've encountered folks with multiple PST files archiving 10+ years of email. I ran into people that needed to queue up a bunch of offline emails in their outbox to send when they're on network again (ok, I kind of get this use case), and I came across all manner of horrors of COM Add-ins.
Anyway, the root of the problem is people using email for everything it was never intended to do or be. If "new" Outlook can break some of those habits, we'll all be better off for it.
> People treat email has a permanent data store.
Is this strange?
I'll be trying to solve some problem, half-remember an email conversation from several years ago on something relevant, and want to look it up.
This feels like the most natural thing in the world to me, and it's not like the ability to save emails is new. Why, exactly, would a forced change of habits be for my own good?
>Why, exactly, would a forced change of habits be for my own good?
At the personal level, it wouldn't be. It makes a lot of sense, and I do the same with Fastmail.
At the corp level where it's often in M365 cloud, you've got hard limits from Microsoft on one hand (100GB primary mailbox - period), and corporate data retention limits on the other. Legal often has strong opinions on how long you are allowed to retain emails which you may or may not be able to personally override. Could be just a few years, which forces a different strategy.
I'm not sure on the details of Google, but one imagines corp workspaces have equivalent interests.
No, not conversations, actual data. Think reports, invoices, large PDFs, etc. Emailing files to yourself, that sort of thing. Then they end up with multiple PSTs.
I very much prefer Outlook's indexing compared to Sharepoint's shitty UI and search capabilities.
Copilot search is great for searching SharePoint
I mean, yeah if your choice is between Email or SharePoint, email wins every time.
But I've seen enough corrupted PST files in my days to never trust Outlook/Exchange as permanent file storage.
Now with "New" Outlook you don't even get that, you get an ODT cache file, everything else is permanently server side in Microsoft land.
Enterprise "productivity" software is fundamentally broken.
Not even counting Sharepoint syncs...
>and I came across all manner of horrors of COM Add-ins.
It works both ways, I ran into a situation where a random Add-in was enabled on the web client and affecting the desktop client behavior despite not being in the list of Add-ins, and could only be disabled from the web client.
Pretty much any app that's been around a while will have all kinds of advanced features that the average user will never use, and eventually becomes detrimental. Hence there's always a group of users and product managers asking to rewrite the app to focus on "the basics".
There's all flavors of "lite" apps and Firefox started as a stripped down version of Netscape.
A lot of older email apps have a prominent "offline" mode that if you accidentally activate it, basically stops the app from sending or receiving any email. I guess a lot of executives demanded the feature because they were handling all their email while on a plane without connectivity.
Outlook COM addons + AutoHotKey was one of the ways that I learned programming back in the day. Email arrives > check the sender > if sender is $company > check for keywords and then run excel macros based on that > generate PDF report and automatically generate an outlook email, attach and send the file.
Good times, it feels like we're getting less and less flexible with the hackability of our corporate workflows as time goes on.
so true - I use some outlook vba to send mass emails programmatically
Yeah this is pretty much the only thing protecting us from Records Retention Policy(tm). Because the legal office thinks discovery is toooooooo risky, we have to delete all of the information we used to develop long lived business processes.
When I wrote this god and I understood it, now god only knows.
The last [US] BigCorp I worked for deployed (in Outlook) automatic deletion of all emails older than their Records Retention threshold. It was incredibly frustrating to have essentially all design/rationale history (from the key players involved) go into the auto-shredder with nobody but me caring. The only workarounds that could avoid the auto-shredder were enormously labor intensive, and of course, debatably violated Record Retention policy.
More like email became stripped down and no longer what it was. Mailboxes were always a permanent data store, there were mail files on disk.
Funny enough, COM is still the fastest way to read calendar data.
A self sorting shield against to much information if you are at the hub of some organization..
> People treat email has a permanent data store.
Email the protocol has this built in.
> If "new" Outlook can break some of those habits, we'll all be better off for it.
It won't, since email is in fact the best data store available to most people in enterprises (especially compared to things like Sharepoint). It might finally accelerate the move away from Exchange though. Here's hoping.
Anyway, the root of the problem is people using email for everything it was never intended to do or be. If "new" Outlook can break some of those habits, we'll all be better off for it.
If ever there was a recipe for doing a terrible job at building software, that's as good a way to put it as I think we will ever see.
Public Folders is what makes us stick with the old Outlook client. For 25 years Public Folder has been a simple drag and drop, hierarchical archive system for communications with clients and vendors at team level.
Same experience when I worked somewhere using outlook.
I exclusively used the web UI because it always ran faster for me, except for a small number of things it couldn't do.
Same experience here. Web version works just fine.
Even their Office Suite runs okay in the Web. For heavy lifting, like getting an md file into our Corporate Design, I still use libreoffice combned with our template.
The Fastmail client is good when it's up and running, but not as good as well-implemented native apps. The initial startup is much slower, and the iOS / iPadOS app (which is the same webapp iirc) is pretty bug-ridden, with the webview freezing or app not progressing past the loading animation without a close swipe / reopen.
You can definitely make a webview app that starts as quickly as most native thing (sub-1s start). We used Tauri and you wouldn't be able to tell the difference.
That's a pretty simple view of native app vs web. Web will always have a lot of baggage that native apps simply won't have, layers and layers of abstractions that still needs to load.
It's true that a blank canvas loaded as a web view will start fast, though. But in practice, when web applications grow - performance tends to take a hit, and the developers also tend to be careless with resources.
The downside of the native app is the open abuse of surveillance. Why does Teams _need_ local network access to function on my ipad? Why does outlook want access to bluetooth from my phone?
Users don’t want to have to configure every app to fuck off, and native web apps (the world we _all_ live in) work way better than some hodgepodge of shit baked together by copilot that’s using unsafe calls and/or libraries.
The Teams conferencing solution probably needs it.
It’s pretty spiffy when it works - it detects whether you’re in the same room as the conferencing device and suggests pre-muting your audio.
The teams conferencing solution probably needs it. It’s pretty spiffy when it works - it detects whether you’re in the same room as the conferencing device and potentially suggests muting
Web developers are not magically worse at this than native devs. See: much of the windows OS lately. The performance of a web view app is more to do with the quality of the devs than the platform it's built on.
Generally though, web developers are of lower quality than native app devs. Often little or no consideration to the layers below, and their focus is more on security rather than speed.
Funnily, I'd say the reason web apps tend to be worse than native apps is because the web is so much more powerful and flexible.
For a native app, I'm often limited to just a small set of components and maybe images I can put on those components. Animations are out of the picture. Configuring colors is sometimes not available but always painful (every component needs it tweaked, there's no universal way to change it). I can't really change things like border margins, rounding, or adding crazy stuff like wobbles or splash effects on click. And really, the more I try to add those things, the worse experience it ultimately ends up being as the OS style and theming moves on. My best bet is keeping everything as close to native styling as possible because that has the best shot of still being usable in windows 20.
Because web apps allow configuration of everything, everything is configured. There are libraries and frameworks that do mass configuration. You can always add 1, 2, or 20 new layers and webdev has abstracted that away into a simple <MyButton /> component. And because of all these capabilities, you need a pretty beefy runtime to be assured you can do them all. Coupled with the fact that this is all also powered by a javascript engine.
Although technically speaking, native is much more flexible as you can literally do anything. But yes, most devs will just use standard UI components and that's it. So your point holds.
Well, to do literally anything outside of standard components, you effectively end up in a realm of programmatically drawing your own "anythings". Certainly possible because obviously browsers are examples of this. But a lot harder.
> That's a pretty simple view of native app vs web. Web will always have a lot of baggage that native apps simply won't have, layers and layers of abstractions that still needs to load.
Well, as I say, you can definitely have webview apps that start fast and aren't taking ten seconds to do things. Not just blank canvasses.
Yes, I’ve made multiple Jumpstart iOS & Android apps that work with Jumpstart Rails and the speed is awesome.
My main gripe with the Fastmail client is that it doesn't work offline. This is of course absolutely possible to do with a webapp, and IMO ought to be a priority for an email client.
Offline support was added in August last year: https://www.fastmail.com/blog/fastmail-works-offline/
I literally switched on "Enable offline support", caching "All mail" offline on my iPhone a few months ago. Tons of free space, only using 4GB for offline.
But when my phone is actually offline (on a plane or elevator) it beachballs when trying to find something.
(I work for Fastmail). That sounds odd – have you contacted our support team so we can look into it? https://www.fastmail.com/support/
The mobile client now supports viewing emails offline.
Got an example of a well-implemented natice app for email? I'm bugged by some bugs with the Fastmail app, but have generally had a better experience with it than any other client I've tried. Search in particular is far better on the Fastmail app.
iOS Mail app still undefeated 19 years later
I really like Mimestream, which is a native client for Gmail.
Very fast and supports all the usual native macOS keyboard navigation, e.g. shift or command to amend selection in a list.
I've heard good things about it, for sure, but I'd argue that it isn't really an Email client. It is a Gmail client as it doesn't work with anything else. Fastmail is in the same bucket, but it is part of my contention about there not being good Email apps generally.
It’s really tempting - uses their API for that speed.
I’m worried Google won’t like it someday. It’s such a hassle if they shut you off that I want to seem like the most normal user to them. Pay Mimestream, skip ads, avoid Gmail app telemetry… any incentive for Google to permit it longterm? (Like maybe you’d switch to Fastmail if they killed Mimestream… or maybe not!)
> Got an example of a well-implemented natice app for email?
Mail.app isn't total shit. It's not great. But it doesn't fumble the basics, like Outlook for Mac, which thinks it's fine to take like 10s to show me my inbox.
Why does it seem to take so long to get & read one new email?
I can use get new mail or synchronize in Mail.app, but always spoiled by the instantaneous Gmail app notification. Often don’t have patience to wait for Mail.app for 2FA codes (just OCR or manually type from the Gmail notification mirrored on Mac).
Also should back up a bulk of ancient emails clogging the app, might be partially my fault.
Mail.app's search is completely and utterly broken in my experience on Macs and on iPhones.
It looks like Apple is addressing this with the next release of macOS/iOS
it really feels like that not progressing past the loading animation all of a sudden has gotten worse. like yea, used to happen like once a week for me, but now it's probably once a day
Yeah, somehow we've lost lessons learned. Used to be, you knew it would take forever to display all of something, so you displayed what you could as you had time to render it. For instance a long report. As you render each page you would make that available to display instead of waiting for the entire 200 page report to render first. "Feeling" fast was often as good as "being" fast.
No we still do that in web dev. This one was just a classic example of design by committee. Classic microslop
The decision to use web technology and the decision to not give a shit about performance (or usability for that matter, unstyled text as buttons anyone?) are often made together, even though they are theoretically independent.
Gmail used to offer a low bandwidth / performance webmail interface, that was essentially their original UI. Ran like greased lightning, used barely any memory. Emails loaded almost instantly.
It was nice while it lasted.
Isn't it still the case then? I used the basic HTML version when I was working at Google to try to understand whether or not it was slow because of the (unoptimal) frontend or not (it was the backend that sometimes took >=600ms to load messages unfortunately, not the frontend).
Google killed basic HTML in Gmail a few years ago
Just last week I vibed an .eml viewer that uses WebView2 and can confirm that it's very quick when not encrusted with garbage.
https://github.com/efsavage/WinEML
Also a daily Fastmail user and it's as fast as any local mail client I've ever used.
WebView2 can be a fantastic experience when the application is designed around it with intent. It can't be a technological afterthought. Taking an application that was designed for web and throwing it in a desktop shell is how you wind up with bad experiences. A hybrid of WebView2 and native elements seems to be the best approach. You can completely hide the browser startup delay with these techniques. The Discord engineers decided to just throw a splash screen in front and call it a day. You could do that too. It seems to fly.
Until you look at memory consumption in Task Manager or Process Explorer. WebView2 spawns ~400Mb worth of various browser processes. Your main app process by itself might look nice and slim, but all that (somewhat hidden) cost is atrocious.
I have 16 GB of RAM on my laptop, and I'm told that's relatively little nowadays. Even after the OS's 2 GB cut, I can run 35 applications that use 400 MB each. I don't even have 35 applications that I care about. (and I'm certainly not going to want to run more than, say, three email clients)
RAM usage at that scale might not be desirable, but any engineer knows that it's the result of a tradeoff where the other options take longer to develop. I would rather have an application that uses 400 MB now than a slimmer one in several years, or one that uses less memory but is extremely slow in some corporate environments (like older Outlook).
(please don't respond to quibble about the napkin math)
No quibble, but you'll have to pry classic Outlook from my cold, dead hands... :)
Microsoft Schedule+ was Microsoft's workgroup calendaring app before the Office division merged email and calendar into one app.
Outlook was late so Schedule+ was included in Office 95 for the Win95 release and so Schedule+ got a wider retail consumer release than if it had been just included with the Microsoft Exchange Server 4.0 release.
from https://www.reddit.com/r/software/comments/v73bk7/microsoft_...
7MB RAM is a lot when Win95 was designed for a 80386 with 4MB RAM. But a modern day x86 (okay, x64) with 8GB, that's about 0.1% of total RAM.It's crystal clear Microsoft simply can't make good software at all anymore. Vendor lock and inertia are their biggest selling points.
When was the last time they did? Buying existing companies does not count
Windows NT/2k?
Active Directory and MS SQL Server are both solid products, as is .NET. The windows NT kernel is very well thought out, too. The last iteration of windows phone was quite good, if too little too late.
Don't get me wrong, MS will enshitify anything it can to make a quick buck. They're much like Disney in that regard.
SQL Server is a fork of Sybase. Not a MS invention.
Active Directory is probably based on someone's LDAP server, though I don't know for sure.
.NET is a copy of Java
NT kernel is good, thank Digital/Dave Cutler for that.
> SQL Server is a fork of Sybase. Not a MS invention.
It's long-since been rewritten. Pre-SQL Server 2000 it was garbage, but it's been improved significantly since then. I'd still use alternatives given the choice, but it's a solid DB.
>Active Directory is probably based on someone's LDAP server, though I don't know for sure.
So you don't know. It was written in house, using a bunch of standardized protocols (LDAP, X.500, kerberos), though with proprietary extensions (GPOs, etc).
> .NET is a copy of Java
That's a gross oversimplification. It's arguably a rip-off after MS tried to sabotage java, but it's their own implementation.
> NT kernel is good, thank Digital/Dave Cutler for that.
Yes, MS hired an experienced OS person for it. Probably one of the best things they ever did.
---
I'm not saying MS deserves kudos or the benefit of the doubt, but they can put out good software, and these are all mission-critical examples of what they have to (having AD go down would bring a whole corporation to a halt). The problem is that with almost everything else, MS has the incentive and capability to ruin. And ruin they do...
For early history about Active Directory, you can't get much better than straight from the horse's mouth ( manager of the Exchange / Active Directory group ).
see https://hardcoresoftware.learningbyshipping.com/p/021-expand...
and
https://hardcoresoftware.learningbyshipping.com/p/bonus-the-...
I will say that in the era when they came out with AD they really took "enterprise configuration management" seriously and made Windows by far the best mainstream ecosystem to manage hundreds or thousands of corporate desktops.
NT, SQL, AD is good. It's the schizophrenic management in the last 20 years that has messed it up.
Microsoft shows how long you can coast on some good decisions.
Exactly that. Haven’t heard it said like that before. Same with my company.
Sure seems like all this fancy Copilot coding help they have would've helped develop a better email client.
I think it really could. You can vibe-code efficient software, if you care.
Microsoft's problems are organizational. A developer can't actually do shit correctly when constantly being pushed to deliver more.
It is. Classic outlook didn't intermingle ads into your inbox. That feature alone makes new outlook much better.
Written on my windows phone 7 series 7
- Satya Nadella
Depending on if you have Microsoft365, you don't get ads either. It's not ads, it's fact that browsers are still not native performance to Win32 application. However, companies hate maintaining multiple applications (Win32/MacOS) and Sysadmin at companies hate maintaining Win32 Applications as well so everyone starts building WebView2.
I do get ads. I constantly get notified about copilot features and whether I've used them 'enough'.
This is done by my employer but the "adoption" team at Microsoft provide the tools to do this monitoring and advertising, and they even provide the emails they send me verbatim. I have some stuff to do with the organisation around that. God I hate those guys, they are trained to be literal shills, corporate puppies. Completely brainwashed.
The "new" Outlook is older than Copilot, so we can't blame the AI here. Don't take this as defense of the new Outlook - I hate it with the same passion.
I think that the usage of WebView2 is a moot point. It effectively is an Edge browser just the same as Edge itself. There may be other underlying issues, but I'd be shocked if WebView2 was to blame.
Wondering to what extent the new code has been AI-assisted.
It would be hilarious if it, like Teams, was backed by Sharepoint. It would also explain a lot about how terrible it is.
Not to mention they puts ads in your email client regardless of whether you use office or not