6,477 LOCs.

A wasted an opportunity to implement it using 7 or 8 microservices.

I think this is sarcasm. But talking to proponents of microservices I am not sure. Can you confirm please

Haha. It is.

But looking at the code made me think how we are capable of shipping software products that are hundred of thousand of lines of code and then we have people trying to break things some much and we end up in a spaghetti of microservices and their connections.

Nice to see that some code I wrote almost 15 years ago is still in use

For some extra fun, click on "Blame" and look at the age of commits on individual lines.

Pretty neat for a piece of software that's been around for 37 years.

The git history goes quite far back too. The first version and the current version look quite different.

https://github.com/emacs-mirror/emacs/commit/1ab256cb9997cf1...

I find the Emacs source code pretty nicely structured and easy to understand (the good commenting helps), especially for something so old.

I certainly agree as far as ELisp code is concerned, but I don’t think it’s true when it comes to the C part.

I’m referring to the C part. What makes you think it’s not well structured?

I thought eMacs was lisp.

Depends on the Emacs, but GNU Emacs has a low-level core written in C with most high-level functionality implemented in various Elisp packages.

And to clarify, in Emacs "move the cursor forward one paragraph" or "kill (~cut) this text" counts as high-level functionality.

Sure, I meant things like interfacing with the OS, the Elisp interpreter itself, performance-sensitive tasks like redisplay, etc.

No, those were just slightly bigger iMacs.

https://en.wikipedia.org/wiki/EMac

Ah, that's why my iphone insists on upper casing the M