TIL: When you download Microsoft Visual Studio 2022 Professional, what you're downloading is an installer. Not an installer for VS2022, but an installer FOR THE INSTALLER of VS2022.
TIL: the VS2022 installer gives you a button to click to get an installation log file. It opens this in Notepad. But they've announced with great fanfare (but for no actual good reason) that Notepad is going away!
Lots of other things on Windows use Notepad. Killing it without a good replacement seems extremely dumb.
I mean, sure, Notepad++ is far better, but most users don't have it installed.
@railmeat@brouhaha there is. AIUI what they're deprecating is the old notepad.exe you'd find in system32 and they're replacing it with the newer Notepad app that's based on WinUI and installed as an app package. same thing with calc.exe
@oclsc@railmeat@ed1conf My favorite is still TECO 124 on TOPS-10. IIRC, it was also known as Stevens or UT TECO, after the institutions that made the enhancements over DEC TECO.
Then on micros, I used Wordstar, mostly in non-document mode.
Then emacs, from 1984 to present.
I find it quite annoying that over the past 40 years, emacs went from being a bloated pig of a program, to lean and mean, not because of any changes to emacs.
@brouhaha@railmeat@ed1conf In my TOPS-10 (pre-Unix) days, I used TECO regularly, and was part of a group of undergrads who, for reasons I cannot recall, reconstructed source code for Stevens TECO by disassembling the binary. I guess we just didn't think of contacting the authors. (Network e-mail was not a thing for us--Caltech was not on ARPANET so far as I know.)
@brouhaha@railmeat@ed1conf I was dismissive of line-based editors because of LINED. Then I gained access to Unix, learned ed because it was all there was, and found that the elegant design around lines--especially stuff like
g/pat1/s/pat2/rep/
was what I really wanted, far less clumsy than TECO's model. Then I encountered Toronto qed (left on that system by a previous sysadmin), with multiple buffers and slightly more flexibility, and that was that.
@brouhaha@railmeat@ed1conf I did spend a week getting vi to compile (this was 1980 on a bootleg USG TS/1.0), another week trying to use it, then I said fuck this clumsy crap and went back to qed.
Never found a screen editor I could stand until I joined BTL and could use jim, then sam. But still used qed most of the time.
40 years on, my two daily-use editors are still qed and sam, and ed is fine if that's all there is.
@brouhaha@railmeat@ed1conf Discovering how well (q)ed matched my brain was just like how C felt just right (coming from DEC-10 MACRO!). And pipelines. And the terminal windows in mux (I now use 9term and 9wm, cursor addressing can go suck a VT52). In all cases it felt like coming home. Was a real wrench when I decided NJ was just the opposite, and left BTL so I could move to Toronto, though overall that shift proved wiser than I'd expected (cf Lucent, Nokia).
@railmeat@brouhaha@ed1conf ed(1) is kind of at the core of what Unix really is, but it's OK (really, no sarcasm) to use stuff built atop Unix without actually using Unix. Makes us who found Unix such a big deal a little sad, but in the end it's not for everyone.
@oclsc@brouhaha@ed1conf I should probably try out ed, just to understand how it works. However I don't think we have much Unix around these days. I think Linux is most of Unix now and it does not follow the Unix philosophy, as I understand it.
Add comment