My 2 cents is that GUI is good for exploring new software, while TUI is wonderful if you already have a mental map of what you're doing. So for everyday used software I would definitely hope that more TUI's where used.
I'm looking for something that you can embedd in your own application. LaTeX would be great but it's not really nice to have WEB code in your C application. It's also has a bit troublesome license.
Om working om a distributed erp system. The goal being native ui in android, iOS, Mac OS, web, windows, Linux and curses with crazy fast response times. No user operation takes longer than 100 ms.
I'm working with SBoM, one fun side effect is that you can scan SBoM's for vulnerabilities. Suddenly hackers, your customers and your competitors starts do to this and you need to make sure your third party dependencies are updated.
This reveals the cost of dependencies (that often are ignored).
I hope that we in the future will have a more nuanced discussion on when it's okay to add a dependency and when you should write from scratch.
I also switch between a lot of computers (work computer at home/work computer at work) but have to develop on "big powerful machine at work". My current solution is tmux + nvim and it works really good. I can just pickup a session from whatever computer I'm in front of at the moment.
Am I correct in that neither Zed nor VS Code support this usecase yet?
I strongly disagree. You should always keep the code as simple as possible and only add abstractions once you really need them.
Too many times I've found huge applications that it turns out be most scaffolding and fancy abstractions without any business logic.
My biggest achievement is to delete code.
1. I've successfully removed 97% of all code while adding new features.
2. I replaced 500 lines with 17 lines (suddently you could fit it on a screen and understand what it did)
Personally I don't see the difference between this and submodules. Repo stores the information in xml files, vdm stores it in yaml files and git submodules in the git database. I don't really care.
The real headache for me is the trouble of traceability vs ease of use. You need to specify your dependencies with a sha1 to have traceable SLSA compliant builds, but that also means that you'll need to update all superrepos once a submodule is updated. Gerrit has support for this, but it's not atomic, and what about CI? What about CI that fails?
The beauty with a static site is that if you have a copy of the generated output, using the site generator becomes optional. You can always move away from using it (but not moving back).
This means that a "custom buggy sitegenerator" is never a bad dependency to have.
Git is actually using that approach which means that libgit is pretty useless to embed, which noone does anyway since it's GPL and everyone instead uses libgit2.
Developers has solved this is most VCS by merging changes. The trouble with merging is that it's hard to explain and hard to visualize for non technical users. Once that problem is solved, there's a lot of nice tools to use for collaborative experiences.