3 ms·
A typical business org uses microsoft office for documents, and they employ programmers writing plugins to their microsoft office products using visual studio w
by Jensson 5y ago
A typical business org uses microsoft office for documents, and they employ programmers writing plugins to their microsoft office products using visual studio which also integrates into their internal .NET business services. I doubt migration would be easy, as everything ties into each other.
- Mikeb85 5y agoYes, I know. In my last corporate gig I was given a laptop with a bunch of MS crap on it. It was far, far worse than my normal setup (Ubuntu + OSS stuff + Google Docs). MS Teams specifically would consume so much memory that eventually other programs wouldn't open without a reboot (the laptop was kinda shit too). I know what you describe is a thing. That doesn't make it a good thing. Edit - should add, Office 365 file synching is also absolute shit. Drove me insane.
- trulyme 5y agoHeh, MS Teams... I wonder if the UX team is the same as for SharePoint. They both suck in a similar way - fortunatelly I can mostly avoid them both.
- prmoustache 5y agoI've been working in companies that use office 365 for the last 4 or 5 years and I had no problem working with office documents either using the office 365 web apps or libreoffice on linux.