Why would you say GUI based workflows are better (ignoring LLMs for now)? I would maybe give you debugging with breakpoints but for anything else I love my neovim with tmux setup
I don't think setup time is a fair comparison here. Any dev who cares to use CLI tools has a dotfiles repo that sets up everything in "under a minute".
I mean yeah, there are tools to automate it. I think you may have a point if both of the following hold true:
1. You very frequently have to install your setup from scratch.
2. Preconfiguring something that aids in installing from scratch is not viable or sensible. (Perhaps you work in an environment where you're not allowed access to your personal dotfiles repo, for example.)
But I think most people will fail at least one of these checks.
I find that (neo)vim enable code navigation to be much faster than any GUI as well, once past the learning curve. If you’re going to work with code long term (eg: years), the learning curve pays off quickly.
I knew someone who created a mandelbrot set viewer that would display over an VGA port, you had a game controller to move around and zoom into it. Something like that?
An RTOS compared to bare metal just means it is some nice abstractions that you would expect from an OS : tasks, mutexes rtc.
An RTOS compared to an OS like linux basically just means it is deterministic, you can guarantee some interrupt is handled within a certain time. Not necessarily faster
Cool, thanks for the clarification. The Wiki article was kind of confusing and seemed to refer to a bunch of topics from back in the tape punching days.
reply