I am a fan of Emacs and I have been using it for years, so a lot of the features described in this chapter were not a surprise to me. Emacs is very powerful. In my team we always juke around: Old folks saying “you kids with Emacs” while the younger team members say “you old folks with VI”. I am not sure if other people have seen the same trend.
I will comment on the questions:
* Is it possible for a system like Emacs to be created in a non-open source way?
I think that everything is possible if the money is invested, but it will probably take a huge investment to do it. Emacs has benefited a lot from the contribution of the community. Developing such an extensible and customizable editor is not an easy task * What are some of the disadvantages of a system like Emacs? I don’t see any for people who take the time to learn and discover the features. It can take a while to assimilate all the important features. Like any free software, there is always the risk of not having support.
* What architecture decisions have allowed Emacs to grow like it has?
The decision of making it highly extensible and customizable.
* When is avoiding complexity a good/bad argument for implementation? It is good to avoid complexity if the added complexity does not add any value necessary for the project. For example if performance is critical to a project, then there will be some complexity added to get the performance out of the system.
* Do you think Firefox will replace Emacs?
I do not see how that is possible. They are 2 different things
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment