the VS in VS Code stands for Vibed and Shitty
-
@davidgerard @401matthall TECO is such a good language that most of the common control structures are single unprintable characters, like $ (the escape key, yes you insert escape to terminate commands, if you use dollar sign instead it breaks) and ^R (control-R). oh you can’t figure out how to insert these characters into text files? well guess what editor lets you do that
TECO: it lets you do anything! you’ll fucking hate it!
@zzt This description of TECO makes me really glad I never learned vi beyond the most basic, common-to-all implementation features.
I know how to quit, save, move the cursor, and switch between edit and command, and... that's about it.
HP-UX 8? Redhat Enterprise 9? NetBSD 1.4.3 through 11? Alpine 3.22? Solaris 8 or 10? AIX 5L? Debian Buster? Irix 6.4? I type "vi $file", and it's all the same.
I have achieved immunity to change by pure obsolescence alone.
@davidgerard @401matthall -
@davidgerard @401matthall TECO is such a good language that most of the common control structures are single unprintable characters, like $ (the escape key, yes you insert escape to terminate commands, if you use dollar sign instead it breaks) and ^R (control-R). oh you can’t figure out how to insert these characters into text files? well guess what editor lets you do that
TECO: it lets you do anything! you’ll fucking hate it!
@davidgerard @401matthall TECO! how does it look? I swear to fuck it looks like
EBhello.c$$P$$SHello$0TT$$-5DIGoodbye$0TT$$EX$$
(example stolen from Wikipedia because I’m taking far too much of a dump to log into my TOPS-20 account where the horrors live)
and again $ is where you mash the escape key if editing live or insert escape into your script otherwise. this shit opens a file named hello.c and replaces Hello with Goodbye??? supposedly????
you’re gonna fucking hate TECO, as requested
-
@davidgerard @401matthall TECO! how does it look? I swear to fuck it looks like
EBhello.c$$P$$SHello$0TT$$-5DIGoodbye$0TT$$EX$$
(example stolen from Wikipedia because I’m taking far too much of a dump to log into my TOPS-20 account where the horrors live)
and again $ is where you mash the escape key if editing live or insert escape into your script otherwise. this shit opens a file named hello.c and replaces Hello with Goodbye??? supposedly????
you’re gonna fucking hate TECO, as requested
@davidgerard @401matthall P$$S Hello$, I scream at my computer, taking myself extremely seriously as a programmer
piss hello indeed, it replies back
-
@zzt This description of TECO makes me really glad I never learned vi beyond the most basic, common-to-all implementation features.
I know how to quit, save, move the cursor, and switch between edit and command, and... that's about it.
HP-UX 8? Redhat Enterprise 9? NetBSD 1.4.3 through 11? Alpine 3.22? Solaris 8 or 10? AIX 5L? Debian Buster? Irix 6.4? I type "vi $file", and it's all the same.
I have achieved immunity to change by pure obsolescence alone.
@davidgerard @401matthall@aaron @davidgerard @401matthall the most telling thing about TECO is that when the emacs community needed a set of modal editing commands they went to great expense to write an ecosystem of vim emulators and supporting code in lisp rather than ever touch TECO again
the only TECO in elisp implementation I know of is a joke implementation from like 6 years ago
-
@davidgerard @401matthall P$$S Hello$, I scream at my computer, taking myself extremely seriously as a programmer
piss hello indeed, it replies back
@davidgerard @401matthall I love TECO, it’s so bad, I say, pulling on my TECO glove
feel free to use the rest of this thread to post about editors that meet _his_ needs (TECO is Turing complete, of course it’s Turing complete, it’s much more painful if it’s Turing complete) but are absolutely not your favorite. just the most dreadful, so bad it’s good shit that’s ever edited text (or punched paper tape, TECO doesn’t care)
-
the VS in VS Code stands for Vibed and Shitty
of course it's fucking vibe coded, how could anyone have ever thought otherwise
Visual Studio Code (@vscode.dev)
The VS Code team builds with VS Code - this is a fundamental principle of how the team works, and it extends to AI capabilities too. Learn more about how the team builds with AI, including how these processes have helped the team move from monthly to weekly releases: https://aka.ms/VSCode/BuildsWithAI
Bluesky Social (bsky.app)
@davidgerard weekly releases (as a system admin i dislike more software having more updates)
-
the VS in VS Code stands for Vibed and Shitty
of course it's fucking vibe coded, how could anyone have ever thought otherwise
Visual Studio Code (@vscode.dev)
The VS Code team builds with VS Code - this is a fundamental principle of how the team works, and it extends to AI capabilities too. Learn more about how the team builds with AI, including how these processes have helped the team move from monthly to weekly releases: https://aka.ms/VSCode/BuildsWithAI
Bluesky Social (bsky.app)
The absolute security disaster that is the remote mode of VS Code (which shipped before Copilot was available even internally) we makes me wonder if this might be a project that LLM slop can’t make any worse.
-
The absolute security disaster that is the remote mode of VS Code (which shipped before Copilot was available even internally) we makes me wonder if this might be a project that LLM slop can’t make any worse.
@david_chisnall @davidgerard no, it's definitely worse now. I switched to it from Sublime Text (after many years of paying for the latter) because VSCode had an actually sensible extension model, especially for language servers and debuggers, and ST never did. unfortunately it's reached a point where I'll have to switch to something else—for which I currently have no alternative because I rely on the "Live Share" extension nobody else has bothered implementing (in a better way or otherwise)
-
the VS in VS Code stands for Vibed and Shitty
of course it's fucking vibe coded, how could anyone have ever thought otherwise
Visual Studio Code (@vscode.dev)
The VS Code team builds with VS Code - this is a fundamental principle of how the team works, and it extends to AI capabilities too. Learn more about how the team builds with AI, including how these processes have helped the team move from monthly to weekly releases: https://aka.ms/VSCode/BuildsWithAI
Bluesky Social (bsky.app)
@davidgerard I saw the change in release schedule from monthly to weekly and I cannot believe anyone can do substantial quality code review on a code of that size in a week.
I do not believe they know what they are shipping nor do I believe they see this as a problem.
Aside from critical bug fixes, why should I need to update my editor more than quarterly or annually? It's just gratuitous risk and churn.
-
@david_chisnall @davidgerard no, it's definitely worse now. I switched to it from Sublime Text (after many years of paying for the latter) because VSCode had an actually sensible extension model, especially for language servers and debuggers, and ST never did. unfortunately it's reached a point where I'll have to switch to something else—for which I currently have no alternative because I rely on the "Live Share" extension nobody else has bothered implementing (in a better way or otherwise)
I was never a fan of the VS Code extension model because it had absolutely no security model at all. This made it trivial for malware to infest the extension-store ecosystem. It was to text editors what ActiveX was to web browsers.
-
R relay@relay.infosec.exchange shared this topic
