4 ms·

I would imagine because there are many UI features that cannot be easily reproduced in the terminal and maintaining two different interfaces with very different

• jlgreco 14y ago
  Ideally any new system should be made UI agnostic, provided a simple default UI with few features readily accessible (perhaps accessible only though a command line of sorts), and allow users of your editor to craft their own frontends, be they TTY or web-based, or anything they may dream up in the future. Just building the web-based editor that you want this year may be fine for this year, but I am not convinced we should be putting much effort into designing systems that don't learn from their predecessors. The classic editors can feel rickety today because they were made with the TTY, and arguably only the TTY, in mind. A system designed today should keep that in mind, and I think make future-proofing it's first and for-most concern. I think it is also really hard to justify supporting fewer features than classical editors do today. Removing the ability to implement technical features so that you can add support for UI features seems like a step backward to me. I don't think there is much (or anything) that you couldn't add to Vim or Emacs, the question is just more along the lines of "can you make it look how you want it too". An editor designed with UI agnosticy (is that a word?) as a first class feature should not have this problem.
  • johncoltrane 14y ago
    I've already clicked the up arrow but I wanted to express my agreement more directly. I agree. That would be "Agnosticism", I think.