4 ms·
Yeah, and you can thank those abstractions that today, we have Microsoft bragging that they got the Teams chat client down to only 9 seconds loading time on a m
by xg15 4y ago
Yeah, and you can thank those abstractions that today, we have Microsoft bragging that they got the Teams chat client down to only 9 seconds loading time on a machine with several multi-GHz cores and gigabytes of RAM. But that's all fine I guess, because it's good enough.
Good enough for what? Good enough that people will grudgingly use it because instantly quitting their job over it would be overblown. Their life will only become a little bit worse through it.
I'm frankly scared how AI-created "good enough" software will look.
- nonethewiser 4y agoTeams is probably written in C# right? Are we really sure C# isn’t performant enough for desktop apps? Seems like a rather hot take. Otherwise what is the non performant abstraction? I think the reality is just that teams is poorly done.
- gwoolhurme 4y agoI don’t think so. I’m fairly certain it’s edge webview2. A lot of MS tools these days are web related. Which is why they run so poorly.
- KeplerBoy 4y agothat's the thing: it's not C#, it's chromium+react. They can't be bothered to write a truly native app for their own platform. Heck, they can't even be bothered to dogfood their in-house react alternatives. All of that for an app that's used by hundreds of millions of people every day. It's those things that make me think Casey Muratori really is onto something.
- nonethewiser 4y agoThank you for clarifying, and I recognize that React does lots of extra work because “it’s good enough” but is that really the limiting factor of teams? Slack is built on electron which we can chide for being resource inefficient as well.