Comment by TeMPOraL

1 day ago

Markdown support isn't a bad idea, actually, as long as they don't break the most important (IMO) property of Notepad: binary WYSIWYG. I.e. if I type in some plain text and then open the file with anything else (including after moving to another machine/platform, or even viewing raw data stream in transit or on drive), I can trust to see that text, as is, and nothing else. In particular, if I restrict myself to lower 127 bytes, I expect byte-to-byte correspondence.

(Modulo CR/LF, of course.)

FWIW, Notepad has had support for BoM detection and wide-characters (UTF-16/UCS-16) for some while. That said, IMO, most simple editors at this point should default to UTF-8 encoding and only LF for line endings.

Notepad being a plain text editor, it always supported markdown. Versions of notepad from the 80s would be able to open and edit markdown, as it’s just plain text.

Apps like classic notepad are useful to have around, when apps that try to parse things like markdown get it wrong and the underlying file needs to be fixed.

  • Makes me wonder - with Notepad rapidly evolving into WordPad v2, and no default "just render bytes as text" solution in modern Windows to replace it, maybe there's still a way to hack one together on the go, just from pieces laying around in every default installation? I mean, rundll32.exe is a thing.

    All I really need is a basic text box with a scroll bar, and a way to feed it with bytes from a file.

    To make it a well-defined challenge: the task is to find a way to create a basic notepad - a multi-line textbox that supports scrolling, and can be fed bytes from a file to render as text directly. Additionally, this must be achievable through simple means - simple enough to memorize - and must work on standard Windows 11 installation, with no extra dependencies to procure. Solution can be e.g. something I can type from memory into "Run" (Win+R) box, but could also be a short list of GUI steps (e.g. open some program, click on "Help", drag file to help box).

Remember this?

https://en.wikipedia.org/wiki/Bush_hid_the_facts

  • I think the Real Bug™ here comes from product-management: Nobody should be taking this kind of stochastic guess process and then just... 100% trusting the outcome with no feedback to the user and no way for the user to correct bad guesses.

    For example, a prompt when opening the file like: "It's unclear what kind of data this is, here are a few options with a preview, pick which one you'd like me to use."

    Annoying, but them's the breaks when you're making software and aren't willing to put in hard requirements about what it is expected to (not) operate on.