4 ms·
I agree. It’s a tall order to replace all the pieces. You need: - programming language not oriented around files - PL compiler designed first and foremost for
by xixixao 3y ago
I agree. It’s a tall order to replace all the pieces. You need:
- programming language not oriented around files
- PL compiler designed first and foremost for incremental complication / interpretation
- New source control that’s syntax-aware and watch not commit based
- New IDE that allows navigating the tree and space
And any of these are a reason for people to not use it:
- CommonLisp? Most people don’t like it. Could you adapt TS? Rust?
- If it’s not Git, can’t use GitHub
- Emacs? Could it be a VS Code plugin? A fork?
Where is a billionaire techie who could foot the bill to build this? It’s a mammoth effort.
- MarceColl 3y agoThats exactly why I started with common lisp, I have a working prototype of all of this (not a complex version control system yet) in about 60 lines of code. The IDE was a hacked 50 line emacs major mode, it's really not that much work to get started. It has of course a lot of rough edges. About the reasons not to use it, thats fine for me, for now this is for me and to serve as inspiration, I want to work with CL. If anyone else wants to tacke it in another language, all the best for me :) Git compatibility and output to files is something that the system should have, indeed