Earlier quoted context omitted.
so keep using it? ending development doesn't mean the executable stops working. the good news for you is this is essentially a promise that wordpad will never change.
I took > will be removed in a future release of Windows to mean it's not just unmaintained (indeed that's fine) but actively removed from your computer
Microsoft is killing WordPad in Windows
321–330 of 367 posts
Re: Microsoft is killing WordPad in Windows
#322Earlier quoted context omitted.
There are many arguments for FOSS. This isn’t one of them. Plenty of open source apps are abandoned. The maintainers get tired, too busy, or whatever. Few users, if any, are depending on this app that hasn’t been getting attention for years. There’s plenty of replacement apps as good or better, including FOSS ones. If it was open source, the odds are no one would care to take over maintenance (though they could) sinc…
> Plenty of open source apps are abandoned. The maintainers get tired, too busy, or whatever. Other people can pick up the baton. For example my window manager of choice is Window Maker which was abandoned for literally years (fortunately since the underlying tech doesn't change every other month, it still kept working) before someone else it picked it up and nowadays there are a few developers working on it. > If it…
(The full OLE capability needs a bit tweaking to get it working right, if one needs it)
Re: Microsoft is killing WordPad in Windows
#323Earlier quoted context omitted.
Wait, it opens files made with Microsoft Office? I thought it refused that and only did rtf and text files like html, txt, etc. Is this perhaps new or do I just misremember?
AFAIK Wordpad can only open Word 6 files.
Not sure if it is some update or what.
Re: Microsoft is killing WordPad in Windows
#324Earlier quoted context omitted.
What’s the load time on LibreOffice these days? Years ago on Linux it took awhile. I use Notepad and Wordpad because they load fast.
The latest version of LibO, 7.6, loads considerably faster than it used to. I now use it almost exclusively but I've MS Office 2007 still installed as there are times when I still need it. LibO's Write still has many bugs and can become incredibly slow when loading large tables (60 to 100 pages or more). To get myself out of trouble I've exported the .ODF file to .DOC and used MS Word to continue. Nothing irks me mor…
We're mostly volunteers, so people implement whatever they feel like doing :-) The essence of open-source.
Come help out if you can, or sponsor some fixes with one of the LibreOffice consulting companies.
Re: Microsoft is killing WordPad in Windows
#325Earlier quoted context omitted.
Microsoft Write (which supported RTF) was included in Windows 1.0 - https://en.wikipedia.org/wiki/Microsoft_Write For Win95, the new included-in-the-box email client required a text editor which supported multiple fonts, colours, font styles, et al. But Microsoft Write code was not written to be modular and cross-platform (much of the Win95 email client code would also run on the Macintosh, for Mac OS System 7.x). So…
Windows 1.0 was released in 1985 November. Microsoft Word for Windows was released in 1989 November, four years after Windows 1.0 included Microsoft Write. see https://en.wikipedia.org/wiki/History_of_Microsoft_Word
And the later WordPerfect for Windows was competition that MS was keen to kill.
Re: Microsoft is killing WordPad in Windows
#326Re: Microsoft is killing WordPad in Windows
#327Earlier quoted context omitted.
For me, Notes tries too hard. The auto-heading of the first line of text, all the editing and markup options, the sharing, etc. are all more than I want, and they end up being distracting and getting in the way. My mind will easily wander to “what if I make all subjects this font and this color and bold etc.”, and then I lose the context of whatever I wanted to write down. TextEdit, new .txt file, name it “{subject}…
If you like plain text, you'd probably love it even more with a better text editor.
Re: Microsoft is killing WordPad in Windows
#328Earlier quoted context omitted.
> I know you're being sarcastic but it also introduced the virtual desktop switcher Which is a PITA to use, so useless. > , (full) DX12, made significant improvements to the console Cmd.exe is still the same > , added real ARM support for the desktop OS, Not relevant > replaced IE, Not fully. They still have it as a menu item in Edge > implemented proper DPI support (all the way to per-monitor true fractional), YMMV.…
cmd is pretty much deprecated in favor of powershell. And both have the best terminal application available on any OS.
Re: Microsoft is killing WordPad in Windows
#329One interesting thing about WordPad (at least from the Windows XP / 7 era) was that it supported the complete OLE2 / ActiveX stack. This let you do all kinds of things like embed other types of controls (like canvases or images from Paint, or Excel tables) inside your document, and WordPad's UI would jump through all the hoops to update and transform into the embedded application's UI when that control gained focus.…
WordPad was an official sample application for the MFC and OLE: https://web.archive.org/web/20070429125746/http://msdn2.micr...
"The WordPad sample demonstrates how to implement an application that imitates the functionality of WordPad, including the user interface elements and some of the capabilities."
I should have known it wasn't the real Win95 WordPad source code since this version is written using MFC and C++.
C++ was not an approved programming language for Win95 components in its quest to run on Brad Silverberg's (Win95 manager) mom's 4MB RAM PC.
Re: Microsoft is killing WordPad in Windows
#330Earlier quoted context omitted.
I know you're being sarcastic but it also introduced the virtual desktop switcher, (full) DX12, made significant improvements to the console, added real ARM support for the desktop OS, replaced IE, implemented proper DPI support (all the way to per-monitor true fractional), added openssh, actual HDR support, and many more things that can be surprisingly hard to go without if you revert to a previous release. There is…
> I know you're being sarcastic but it also introduced the virtual desktop switcher Which is a PITA to use, so useless. > , (full) DX12, made significant improvements to the console Cmd.exe is still the same > , added real ARM support for the desktop OS, Not relevant > replaced IE, Not fully. They still have it as a menu item in Edge > implemented proper DPI support (all the way to per-monitor true fractional), YMMV.…
cmd.exe is a shell so it shouldn't be any different just because the console updated. This article simultaneously explains the difference between a shell and a console as well as explicitly list the feature changes added to the console in Windows 10 https://blogs.windows.com/windowsdeveloper/2014/10/07/consol...
> Not fully. They still have it as a menu item in Edge
Well sure, completely removing IE just because they added Edge would have made the replacement more painful for no real gain. They already committed to ongoing support of IE based applications for many years to come years ago.
> YMMV. This one is hit or miss.
YMMV on what apps support the new DPI features but the APIs and support itself is 100% there all the time in every copy of Windows 10. In previous versions of Windows apps were unable to reach that level of DPI support regardless if they wanted to update and do so.
> You cannot revert to a previous release in Windows.
Where'd you get that idea? I've done it myself, it's quite possible. You're also quite welcome to just install fresh if you're update data has been cleared but you can revert otherwise.
> When SW changes just for the sake of change (see calc.exe), something is wrong.
Calling adding resizability, OS theme following, (fractional) DPI awareness, additions to the unit and time conversions, and graphing "changes just for the sack of changes" is spot on the nose of what I was talking about - the only way they could have made you happy was to not change, it has nothing to do with how much better or worse the new calculator actually is. Maybe you personally aren't a fan of a single one of the changes, that's still not reasoning for why it's changes for the sake of changes.
The rest is more individual so I won't say anything one way or another. E.g. ARM support can be critical to one person and irrelevant to the next, hard to make 1 list containing only what every person on Earth agrees is relevant so I included things many will even if some won't. That doesn't mean I'm saying you specifically must find ARM support one of the meaningful changes.