3 ms·
I really do hate is MSFT's naming conventions AND their propensity for calling two different products by the same name for marketing reasons. I mean Microsoft
by ubermonkey 4y ago
I really do hate is MSFT's naming conventions AND their propensity for calling two different products by the same name for marketing reasons.
I mean Microsoft Word, the word processing tool that runs as a native app on one's computer. The degree to which the online or Teams versions do not play nice with the "real" one is a HUGE own-goal by MSFT and reason enough to avoid them if you can. If you're going to have an online tool called Word, it damn well needs to work EXACTLY LIKE THE REAL VERSION.
- zo1 4y agoI've used both extensively and interchangeably. The fact that Microsoft got "Word" running in the web, and embedded inside another application, and made it all work mostly seamlessly is downright amazing. I've yet to encounter any issues with formatting between the three, and am constantly surprised at their ability to be consistent. Now where it all goes pear-shaped, is not the technical side of it all, it's the UX and marketing teams that got involved. One big example is the "save" dialog that's been butchered beyond describing (even in the standalone desktop version of Word) in order to promote OneDrive and other microsoft offerings.
- lostlogin 4y agoMy issues: Pictures, headers and footers, the amount one can fit in a page (varies between versions). What will happen to the Teams version if I download it, edit in the native app and save? Downloading a lot of files off Teams usually fails and gives a load of html files. The ‘integration’ nag for one drive which can’t be dismissed or enabled but seems to work. It’s an absolute mess and I’m very surprised to encounter someone who finds it works well.
- Dalewyn 4y agoYou might be (not) pleased to know that Windows 10 and Windows 11 both identify internally as NT 10.0.
- ubermonkey 4y agoI'm definitely not surprised.