It was handy to have as a simple .doc/.docx/.rtf viewer. In my previous job, some of our teams would create documentation written in .docx (eg as part of a application package), or automatic reports generated as .rtf files, and WordPad enabled us to view these docs from secure, locked down servers, without needing to install any addition software (which would increase the attack surface and add unnecessary maintenence overhead).
With MS now getting rid of WordPad, I’d imagine it’ll be a bit of a hassle - they would now have to switch to a different native file format (which would be a PITA to convert several hundreds existing files), or install a file viewer or some other app, which would add maintenance overhead.
WordPad wasn’t bloat, it was a tiny, executable which didn’t depend on any special dlls or frameworks.
You know what’s actually bloat? Candy Crush, Bing, Ads in File Explorer and all that MS Store / UWP / “Modern UI” crap that MS keeps pushing out.
It was handy to have as a simple .doc/.docx/.rtf viewer. In my previous job, some of our teams would create documentation written in .docx (eg as part of a application package), or automatic reports generated as .rtf files, and WordPad enabled us to view these docs from secure, locked down servers, without needing to install any addition software (which would increase the attack surface and add unnecessary maintenence overhead).
With MS now getting rid of WordPad, I’d imagine it’ll be a bit of a hassle - they would now have to switch to a different native file format (which would be a PITA to convert several hundreds existing files), or install a file viewer or some other app, which would add maintenance overhead.
WordPad wasn’t bloat, it was a tiny, executable which didn’t depend on any special dlls or frameworks.
You know what’s actually bloat? Candy Crush, Bing, Ads in File Explorer and all that MS Store / UWP / “Modern UI” crap that MS keeps pushing out.