step 1: remove wordpad

step 2: omg there's demand for features

step 3: turn notepad, whose point was to be a dumb simple thing, into a wordpad

step 4: get a raise because you "solved" the problem

Glad (/s) to see the MBA-ification of tech companies continues uninterrupted as we enter the second half of the decade.

I don’t know what sort of insane nerd echo chamber you have to be in to think that MBA-ification means “adding rich text editing features to a text editor”.

You’ve heard legitimate complaints about “MBAs” but very clearly lack the knowledge to identify those problems on your own.

> "adding rich text editing features to a text editor”

Yeah, we already had that. In the form of Wordpad. Which was EOL'd. And now we have Notepad with AI features.

Notepad was, and always should have been, a simple & lightweight text box for storing and editing text only files. If you wanted to edit something more complicated, you could use the other tool that was built into Windows specifically for that.

I like having something all in one.

I liked having a simple plain text editor

I assume there's like a single manager who's job it was was to maintain notepad and force use of AI, so obviously, vibe code needless features because if it's not broke, how can you fix it with AI.

I've never liked Windows but did appreciate the dumb simplicity of parts of it. Especially MS Paint. Like Mac Preview has always had all these nice advanced features, but lacked one simple thing most people need, a frikin pencil tool. Then they added a pencil but made it try to turn your scribbles into neat shapes every time... with fill.

Yeah IDK. Wordpad is built around rich text, with all the weirdness and complexity that comes with it. I know for a fact that .rtf is absurdly complicated to work with, and I assume that .docx is similar.

I’m willing to bet that adding markdown to Notepad was a lot simpler than trying to make it work in Wordpad, especially since you’d probably still have to support rich text.

Both Wordpad and Win11-Notepad use the RichEdit control (which first appeared in Win95, brought to you by the Mail client group aka Capone - cuz no one else wanted to do a RichEdit text control). see https://devblogs.microsoft.com/math-in-office/windows-11-not... and https://learn.microsoft.com/en-us/cpp/mfc/rich-edit-control-...

The RichEdit control handles parsing RTF (I believe there was a CVE-level bug about RTF-handling in RichEdit - ahh - here we go https://www.kb.cert.org/vuls/id/368132/), the programmer/app is insulated from grokking RTF.

Here's sample code for opening an RTF file - https://learn.microsoft.com/en-us/windows/win32/controls/use...

Adding realtime conversion of text-only Markdown to the processed-richtext Markdown is slightly more difficult than an instant message-type edit control converting a text :) to a unicode emoji character representing :)

You'd have some bookkeeping to remember which lines are markdown and which are plain text. But it's not rocket science.

Imagine Win11-Notepad as WordPad with all the UI for rich text formatting disabled.

Hence why I use .txt and not .rtf (After having multiple RTF files become corrupted)

[deleted]

Syntax highlighting is definitely less complex than updating and rendering RTF and HTML.

There is configurable syntax highlighting in vscode.

Should an app like Notepad ever embed a WebView? (with e.g. tauri-apps/wry instead of CEF now FWIU)? Not even for a Markdown Preview feature IMHO.