3 ms·
Doing less work is pretty much the programmer creed. But that statement has several dimensions. Including having to do less configuration and tweaking work. I
by kamaal 6y ago
Doing less work is pretty much the programmer creed. But that statement has several dimensions. Including having to do less configuration and tweaking work.
I think a modern lisp based editor, with concurrency/threading built in. With Racket/Clojure/CL backend with modern controls builtin would be all we need.
You still keep the emacs spirit, but with modern outlook.
- _emacsomancer_ 6y ago> I think a modern lisp based editor, with concurrency/threading built in. With Racket/Clojure/CL backend with modern controls builtin would be all we need. Sure, but it's the same as the "replace (La)TeX" problem: part of the value of the ecosystem is the huge collection of packages/extensions. But if there was a reasonable way of porting packages over to a CL/Scheme new editor base, I agree that would be good. > Including having to do less configuration and tweaking work. Sure, but a bad, unconfigurable tool is more work.