3 ms·
> You're not "starting Teams.exe", you are deploying a server and booting an operating system. Sounds about right and, actually, is quite a feat. I just wonde
by moepstar 4y ago
> You're not "starting Teams.exe", you are deploying a server and booting an operating system.
Sounds about right and, actually, is quite a feat.
I just wonder how they went from "build a chat app with some filesharing built in" to "include everything and the kitchen sink and oh, in your own universe" kinda thing...
- DrewADesign 4y agoBecause then they could be absolutely sure that the people they hired to build their application didn't need to know how to build the things needed to build their application, or build the things needed to build those things, etc. Looking at electron et al apps purely based on performance is like comparing the cost of a restaurant meal to the cost of cheap groceries without acknowledging the benefits. If you're a software developer, the benefit probably doesn't seem worth it. If you're a project manager hiring developers to be responsive to new feature requests from the product managers, interface changes from the UX team, branding changes from the identity team, adapt to infrastructure changes from the devs designing the services, etc etc etc then having a battle-tested-on-most-platforms batteries-included platform makes a lot of sense... even if it comes with 60 kinds of batteries when you only need 5. Especially when for the most part, only a tiny percentage of people actually give a shit about whether something takes 50ms to load vs 3s. The large operations that take 30s to load occur rarely enough (startup, for example) that most users just don't care.