Hacker News Reader

Comment by getpokedagain | Hacker News Reader

I think I need to update my sales pitch for the passage of time. Emacs is probably closer to 50 now.

Also notable that the way changes are introduced to the different languages is so different that this is just hard to really look at. Notably, elisp of today is not dramatically different from elisp of 20 years ago. JavaScript? Basically a brand new language after ES6+.

ES6 was released 16 years ago. I'm building on top of ES6 like it's rock solid, and so far I haven't been disappointed. After ES6 the langdev process changed materially, and it now rewards introducing language features that are, in my view, half-baked. I have had to take over parts of the work of the standards committee to be able to do this project at all.

I had to reinvent iteration to get both perf and abstraction at the same time: https://docs.bablr.org/architecture/spacetime

I also had to create records and deep freezing: https://es.discourse.group/t/proposal-records-a-new-one/2546...

Right, but that about halves the age of JavaScript as noted in this thread.

I fully agree that it is reaching a more stable place now than it was 5 or 10 years ago. It is still nowhere near as old as elisp.

Oh for sure. I'm not trying to make a case against Emacs or Elisp or anything. Mature tech is highly, highly valuable. I just wanted to know if JS could do it. Could it, can it host a whole unix-y, emacs-y OS?

Reply on news.ycombinator.com