Earlier quoted context omitted.
[flagged]
Agreed, we used TUIs because we couldn't afford anything better on MS-DOS, CP/M, 8 bit home computers. People on better systems like the Amiga and Atari were already past that.
IDEs we had 30 years ago and lost (2023)
381–390 of 607 posts
Re: IDEs we had 30 years ago and lost (2023)
#382Earlier quoted context omitted.
You can skip libc on Windows - you can't skip the system DLLs like kernel32. (In fact, Microsoft provided several mutually incompatible libcs in the past.) Well, you can non-portably skip kernel32, and use ntdll, but then your program won't work in the next Windows version (same as on any platform really - you can include the topmost API layers in your code, but they won't match the layers underneath of the next vers…
Yes, it's not literally libc on windows, but the point is that directly calling syscalls is not supported, you have to call through the platform's library for doing so. On some systems, this is just not a supported configuration (like what you're talking about with Windows) and on some, they go further, and actually try and prevent you from doing so, even in assembly.)
Re: IDEs we had 30 years ago and lost (2023)
#383I feel like we should go back to ASCII for programming languages. Does your IDE really need emojis? Parsing unicode is intractable.
Re: IDEs we had 30 years ago and lost (2023)
#384Earlier quoted context omitted.
>One thing that's nearly impossible to replicate on modern systems is the extremely tight feedback loop these TUIs Why? Yes, VSCode is slow. But Zed and many neovim GUIs are extremely responsive. Why would achieving that even be impossible or even that hard? You "just" need software which is fast enough to render the correct output the frame after the input. In an age where gaming is already extremely latency sensiti…
I'm not sure if you know what "terminal" means. I'm not talking about terminal emulators (the "terminal" program on macOS/Linux/Android/etc.) but actual, real terminals. The "terminal" is a text mode rendering mechanism built into computers of the terminal era. The closest modern operating systems come to it is the terminal-like environment you can get on Linux or the *BSDs by disabling the GUI, but even those merely…
Re: IDEs we had 30 years ago and lost (2023)
#385Ok, this post is mostly about text-based IDEs, but I think the point mostly stands as well for IDEs in general. I'm thinking about Visual Basic or Delphi. I think such a IDE for Python would really be helpful for beginners. Not text-based, but more like Visual Basic. But everything integrated, everything easily discoverable (that's very important!). Maybe also with such a GUI builder as in VB. And a built-in debugger…
Exactly. I recently recorded a video of me creating a toy app with VB3 on Windows 3.11 and the corresponding tweet went “viral” for similar reasons as this article.
It’s not really about the TUI: it’s about the integrated experience as you say!
Re: IDEs we had 30 years ago and lost (2023)
#386Earlier quoted context omitted.
You are conflating a method of interaction with a method of drawing things to the screen. These are totally different things. Whether you have a keyboard focused interface like vim or not, has absolutely nothing to do with whether you are drawing graphics by sending escape codes to a terminal emulator to render the interface. Neovim and it's frontends prove that if you remove terminal emulators the applications becom…
Thats_just_like_your_opinion_man.gif
What I said about the separation of user interaction to graphics is also not an opinion.
Re: IDEs we had 30 years ago and lost (2023)
#387Earlier quoted context omitted.
The thing is that emacs predates Apple developing cmd-z/x/c/v and Microsoft copying Apple in Windows. Before that, the most commonly copied keystrokes in programmer's editors were the freaking Wordstar ones e.g. in all the Borland products. Also OP apparently has no knowledge of the far better IDEs we had 30-40 years ago including but not limited to: - Apple MPW, 1986. GUI editor where every window is (potentially) a…
All your example are in the Apple ecosystem. Depending on where the author is from, it may not be that surprising that they wouldn't know about them. In my corner of the wolrd, Apple was basically non-existent until the iPod and iPhone.
Re: IDEs we had 30 years ago and lost (2023)
#388I was expecting to see the most productive IDEs of all time, Visual Basic 6 and/or Borland Delphi, but we're just ahead of those in this article. While it was truly amazing that Borland managed to stuff a full text editor into a TSR under MS-DOS, and every new version of Turbo Pascal was faster and had more features, it all culminated somewhere around Delphi for me, and Visual Basic 6 for almost everyone else. Then t…
Re: IDEs we had 30 years ago and lost (2023)
#389Earlier quoted context omitted.
Failure of Linux Desktop you mean. RDP works great and GUI tooling for Windows and macOS is quite comparable to using VB, Delphi, Smalltalk like experiences.
There are no failures for Linux Desktop; this can never be the meaning. I say this with humor in mind. Requiring me to have a cloud account to format my machine (mac) and requiring me to have a cloud account on only pre-authorized hardware (Windows 11), only to open up Notepad and see they slapped AI inside of it; now that is quite comparable to me slapping Linux on it. Just sayin'