Crimson Editor.
IDEs we had 30 years ago and lost (2023)
51–60 of 607 posts
Re: IDEs we had 30 years ago and lost (2023)
#52It took many decades for me to get that kind of flow back for mainstream programming languages on modern computers. And modern IDEs still have higher latency than they should.
Re: IDEs we had 30 years ago and lost (2023)
#53Finally! Someone who still remembers the best software ever written. I looooved Sidekick and we used it throughout our small company. It's so long ago. I remember only parts of it now but it was such a useful tool.
Re: IDEs we had 30 years ago and lost (2023)
#54Now that CLI tools are in fashion again... has nobody thought to recreate a modern version of Turbo C++/Pascal? I know there's Emacs and vim, but they're far too programmable and bloated compared to the elegance of TC++, which did one job, and one job only, very well. Also, despite being an Emacs power user at this point, it's never going to be as ergonomic and well thought out with its arcane chords, while TC++ conv…
Have you seen tvision[0] and turbo[1]? [0] https://github.com/magiblot/tvision [1] https://github.com/magiblot/turbo
[0] https://i.imgur.com/Qvkt3W0.png
[1] https://www.gnu.org/software/texinfo/manual/texinfo/html_nod...
Re: IDEs we had 30 years ago and lost (2023)
#55You could throw together a CRUD app in under an hour interactively.
Re: IDEs we had 30 years ago and lost (2023)
#56The arguments for using TUI IDEs are just very poor. Developers should not be relying on something as loaded with legacy bloat like the terminal, to do development. Zed has remote editing support and is open source. Resource consumption is a bizarre proposition, considering what abstractions the terminal has to be forced into to behave something like a normal window. Really, TUIs are not very good. I get it, I use th…
One thing that's nearly impossible to replicate on modern systems is the extremely tight feedback loop these TUIs had. Keyboard latency was near non-existent while basic calculators these days will happily take a hundred milliseconds to process a key press. We don't need to go back to the 66MHz era, but it's embarrassing that programs running on a dozen computer cores all executing at several gigahertz feel less resp…
Re: IDEs we had 30 years ago and lost (2023)
#57Moved to Dev-C++
Nowadays just any editor and using GCC directly
Eternally greatful for open source, Microsoft charged thousands for Visual C++ back then.
Re: IDEs we had 30 years ago and lost (2023)
#58I think Emacs still does all of this; the argument the author makes is that it is "arcane", it just uses conventions he is not used to. It is however fully self-documented and interactive. For me the best textual interface I've ever used remains Magit in Emacs: https://magit.vc/ I wish more of Emacs was like it. I actually use emacs as my git clients even when I'm using a different IDE for whatever reason.
I think that after 25+ years of usage, I'm "used to it" by now.
Re: IDEs we had 30 years ago and lost (2023)
#59Now that CLI tools are in fashion again... has nobody thought to recreate a modern version of Turbo C++/Pascal? I know there's Emacs and vim, but they're far too programmable and bloated compared to the elegance of TC++, which did one job, and one job only, very well. Also, despite being an Emacs power user at this point, it's never going to be as ergonomic and well thought out with its arcane chords, while TC++ conv…
(That doesn't imply I went with VS or similar fat ide, just that I didn't end up using xwpe for real. I tried code::blocks for a while but mostly just use geany or a plain editor.)