Live data from Hacker News

Microsoft is killing WordPad in Windows

bleepingcomputer.com

211–220 of 367 posts

Re: Microsoft is killing WordPad in Windows

#211

Honestly, I'm just waiting for the Linux community to figure itself out with Wayland/X and get a bit more stable and I'll probably be switching. The only question in the air for me is how I'm going to manage my cloud files (I've gotten used to having filesystem sync between multiple devices) as the existing offerings seem more or less meh.

Wayland's a solved problem if you use an up to date or rolling release distribution.

No, it's not. A lot of things are a works-in-progress, and it's less stable than X. Calling it solved is understating by a large margin the plethora of issues that still need to be addressed.

Is it better than where we were a couple years ago? Yes, definitely. Is it stable enough to be a daily driver? Somewhat, yes.

Re: Microsoft is killing WordPad in Windows

#212

Honestly, I'm just waiting for the Linux community to figure itself out with Wayland/X and get a bit more stable and I'll probably be switching. The only question in the air for me is how I'm going to manage my cloud files (I've gotten used to having filesystem sync between multiple devices) as the existing offerings seem more or less meh.

I haven't looked yet but on steam deck I've noted that Windows/wine stuff has improved a ton lately - could you just run your sync tool from win32 on *nix?

Important critical files, to run on something like this? No thanks.

Re: Microsoft is killing WordPad in Windows

#213

This is deeply unfortunate. WordPad is by far the best implementation of RTF anywhere.

But who uses RTF? I can't recall ever receiving an RTF file. Scanning my drives, I've only found a single Readme RTF file in some old Windows utilities.

I haven't created an installer for a Windows desktop app in over 5 years, but it was a common format for the embedded EULA. It's not as important these days, but there was a huge file size difference between an RTF created in Wordpad vs Word.

Re: Microsoft is killing WordPad in Windows

#214
post #149
post #127

Earlier quoted context omitted.

pbrush also opens Microsoft Paint. (It used to be called Paintbrush.)

can i do something in regedit so that "paint" loads up "paint.net" and not og paint?

Add entry to. Works atleast in Win 11

   Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\App Paths

Re: Microsoft is killing WordPad in Windows

#215

Earlier quoted context omitted.

ffmpeg had a schism just over a decade ago and the splinter group forked off into libav. One of the splinter group members happened to be the now-former ffmpeg maintainer in the Debian and Ubuntu repositories and switched them from ffmpeg to libav. Yes, this was done purely for ideological reasons.[1] So this bullshit happens in the open source world just like in the closed source world. In a way, I would argue it's…

I don't see this as "bullshit", but the opposite: Instead of going from one useful software to zero, we've gone from one to two.

Absolutely true. This is why we have hundreds of Linux distros, which is fine for us who can sort our way through but average users throw their hands up in desperation. I've the same problem in supermarkets when confronted with dozens of brands of an item in that they all seem the same.

Re: Microsoft is killing WordPad in Windows

#216

Earlier quoted context omitted.

I always figured this was by design. Microsoft needed a GUI word processor that was free to stifle competition in the new "windows software" market, but not good enough to upset their Word business. Good job WordPad - one of the flag bearers of Microsofts anti-competitive business practices.

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…

Notepad.exe have lots of improvement in past 10 years. A major revamp in 2022 It is no longer a "thin wrapper".

Re: Microsoft is killing WordPad in Windows

#217
post #150

Earlier quoted context omitted.

I always figured this was by design. Microsoft needed a GUI word processor that was free to stifle competition in the new "windows software" market, but not good enough to upset their Word business. Good job WordPad - one of the flag bearers of Microsofts anti-competitive business practices.

Seems like there were three options: 1. Ship Word with Windows and not get paid for it, even though they had hundreds of engineers working on it. 2. Ship no word processor with Windows, and make the end user find one on their own. 3. Ship a basic one and let the user upgrade to Word if they needed something more. At the time with option 2, it's not like you're going to hit google and download some FOSS solution - you…

Microsoft had a cheaper office suite that they sold as a middle ground. I remember the "poor" kids in highschool couldn't edit their papers in certain ways at home and had to do some things on school computers instead.

https://en.m.wikipedia.org/wiki/Microsoft_Works

Re: Microsoft is killing WordPad in Windows

#219

Earlier quoted context omitted.

I don't see this as "bullshit", but the opposite: Instead of going from one useful software to zero, we've gone from one to two.

Absolutely true. This is why we have hundreds of Linux distros, which is fine for us who can sort our way through but average users throw their hands up in desperation. I've the same problem in supermarkets when confronted with dozens of brands of an item in that they all seem the same.

> This is why we have hundreds of Linux distros, which is fine for us who can sort our way through but average users throw their hands up in desperation.

This is probably a good thing for those who want something very particular.

For example, something like Ubuntu for the desktop, but without snaps everywhere - that'd be Linux Mint. Or maybe something like RHEL, but without necessarily having to (or being able to) pay - that'd be Rocky Linux or Alma Linux.

On the other hand, this also means that the community's efforts are spread thin, there's lots of fragmentation and the whole experience is just way more messy.

Instead of writing install instructions for The One True Linux Distro, you now need to write those for many, deal with multiple packaging formats and repositories, or just live with the reality that something available in one distro won't be available in another. I even had that issue with WireGuard, where it worked in Ubuntu but not Debian for a particular use case, shortly after it came out.

For as niche the types of BSD OSes are, they feel more coherent. I wonder what things would be like if we'd have similarly focused efforts for Linux, even stuff like one audio solution that's made to always work everywhere, one display server/compositor, one desktop that scales back to run as fast as XFCE or be as pretty as KDE.

But that's not how humans work and instead we'll just get new packages replacing older ones, sometimes for the better, but not always.

The very same thing applies to many FOSS software packages out there, but in a sense it's still better than some closed source package being abandoned and nobody ever being able to do anything about it.

Re: Microsoft is killing WordPad in Windows

#220
post #150

Earlier quoted context omitted.

I always figured this was by design. Microsoft needed a GUI word processor that was free to stifle competition in the new "windows software" market, but not good enough to upset their Word business. Good job WordPad - one of the flag bearers of Microsofts anti-competitive business practices.

Seems like there were three options: 1. Ship Word with Windows and not get paid for it, even though they had hundreds of engineers working on it. 2. Ship no word processor with Windows, and make the end user find one on their own. 3. Ship a basic one and let the user upgrade to Word if they needed something more. At the time with option 2, it's not like you're going to hit google and download some FOSS solution - you…

MS Works was supposed to fill that role...[0]

https://en.m.wikipedia.org/wiki/Microsoft_Works [0]

Post reply on HN