Earlier quoted context omitted.
The base input of emacs is ‘M-x’. From there, any command is accessible. And you have ‘M-:’ for evaluating any bit of elisp code. There’s a few UI concepts to learn (frame, window, buffers, point, mark, region,…), but that would fit in a single sheet of paper.
The keys I enumerated are sufficient to discover and execute all available operations in that style of TUI. You don’t have to type commands or command-specific keyboard shortcuts, like you have to in Emacs. It’s analogous to how in a traditional GUI you can discover and execute everything just using the mouse. Like in the GUI analogy, you can then choose to remember and use the displayed keyboard shortcuts for freque…
IDEs we had 30 years ago and lost (2023)
141–150 of 607 posts
Re: IDEs we had 30 years ago and lost (2023)
#142(Article is from 2023, so the title should be updated to say "32 years ago", or something) The biggest loss in TUIs is the latest wave of asynchronous frameworks, which bring the joy of dropped keypresses to the terminal. In any TUI released before the year 2000, if you press a key when the system wasn't ready, the key would just wait until the system was ready. Many TUIs today still do this, but increasingly frequen…
so even 41 years seems to be in the scope.
I was expecting
- early projects that ended in Visual Studio 1.0 or NetBeans soon after, (2 to 9 years too early for them)
not
- "vim (1991) was not out yet" (not-a-quote, but my feeiling upon looking at ncurses instead of floating windows)
Re: IDEs we had 30 years ago and lost (2023)
#143I hate it when sites do this. I don't want my window decorations to be restyled in the name of aesthetics. I need them to be usable.
Re: IDEs we had 30 years ago and lost (2023)
#144Good article. I'm more of a GUI guy who is contend with VSCode. I'm intrigued to learn Emacs but don't have the time for it. Back in the 90s, however, Borland TUI was indeed the pinnacle. I remember I played with Turbo C for a while but did not learn anything, but it was fun just to use the IDE.
Re: IDEs we had 30 years ago and lost (2023)
#145For what it's worth it, I'm still developing and using exclusively my own text-based editor/IDE: https://github.com/alefore/edge I wrote recently a bit about my conclusions after ten years of developing it: https://github.com/alefore/weblog/blob/master/edge/README.md
Re: IDEs we had 30 years ago and lost (2023)
#146[1]: https://github.com/microsoft/edit [2]: https://news.ycombinator.com/item?id=44031529
Re: IDEs we had 30 years ago and lost (2023)
#147This right here was the key to super flow state. Lightning fast help (F1), very terse and straightforward manuals. I have tried to replicate this with things like Dash (https://kapeli.com/dash), to some degree of success.
The closest thing I had to this in windows was probably Visual Studio 6 before the MSDN added everything that wasn't C/C++ to the help docs. After that, the docs got much harder to use due to their not being single purpose anymore. The IDE was a little more complex, but you at least felt like you got something for it. After that, too many languages, too many features, overall not great experience.
The keybindings were so simple and fast, Borland IDE on DOS was a very nice tool. Yes, easier than vim and emacs. The reason is because of mouse in TUI so things like complex selection/blocks/text manipulation are not keybindings in the same way so the key combos are more "programming meta"(build, debug, etc) rather than "text meta".
EDIT: also, I feel like this needs to be mentioned: compilers were not free (as in beer) at that time!
In order to develop on my own machine as a teen, I had to sneakily copy the floppy disks the teacher used to install this on the school computers so I could have more than 1h using it at home! COPY THAT FLOPPY
Re: IDEs we had 30 years ago and lost (2023)
#148(Article is from 2023, so the title should be updated to say "32 years ago", or something) The biggest loss in TUIs is the latest wave of asynchronous frameworks, which bring the joy of dropped keypresses to the terminal. In any TUI released before the year 2000, if you press a key when the system wasn't ready, the key would just wait until the system was ready. Many TUIs today still do this, but increasingly frequen…
So disappointing to expect a GUI Smalltalk System Browser and seeing DOS TUIs.
And then delight recalling Turbo C/Pascal and MS C 4.0 with CodeView that even worked in 43 or 50 line modes.
Re: IDEs we had 30 years ago and lost (2023)
#149Earlier quoted context omitted.
Delphi is still very impressive. However, they missed out on a much greater opportunity. Part of Delphi's crown jewels is VCL which can only be used on Windows. If you use Delphi for an OS other than Windows you have to use FireMonkey/FMX. Lazarus has LCL which is VERY similar to VCL, but LCL on Lazarus is not limited to Windows. One can write a LCL application and it works the same on Windows, macOS, and Linux. If D…
Don’t disagree that VCL across all the platforms would be a game changer. However, the quality and reliability of the Delphi experience together with mobile support overcome the VCL/FMX trade off in my books.
Re: IDEs we had 30 years ago and lost (2023)
#150TUIs sucked and they still suck. Programmers are trying to bring them back bc nostalgia I guess? I floated the idea of TUIs to our data engineering team and got very negative responses. (My nostalgia for undergrad turbo pascal TUI I guess lol)
I think TUIs mostly suck for IDEs, but some tools like k9s or htop are nice.