The fundamental issue is Emacs its JSON parser is currently still rather slow (not sure why actually). But in LSP mode it needs to parse the LSP server's many JSON response messages very quickly. The aforementioned booster converts all JSON into ELISP byte code so Emacs can process LSP messages much faster.
I guess, the Emacs project will have to tune their JSON parser in the future.
While I agree with you, I think, having cognition is not black and white. There are animals with great cognition skills especially among predators. Our brains are essentially anticipation machines capable of predicting the future — a trait uniquely advantageous when hunting other animals. We just happen to have specialized on this trait to the extreme (and otherwise lack good sensory organs or impressive innate weapons).
Whenever this topic comes up I have to think about this octopus who escaped an aquarium. [1]
Perl originated from shell programming and inherited some of its patterns. If you ever looked at a bash script using arrays you will immediately recognize "@" to access the array as a whole and the switch to the "$" sigil to access a single element from that array. Perl was designed to make it easy for shell script writers to pick it up.
> They threw away their user-repairable mantra when they made the Desktop
You forget the value proposition of Framework products is not only they allow you to bring your own hardware but they also promise to provide you with replacement parts and upgrades directly from the vendor.
In this case they could not make the RAM replaceable (it’s a limitation of the platform) but you can expect an upgrade board in about 2 years that’s actually going to be easy to install for much less cost than buying a new desktop computer.
That's less of a thing here since this is "just" an ITX motherboard, a case, and a power supply. With the laptops replacing the board saves a bunch of other parts but here the board is basically the only part that matters.
I am working for a company maintaining an enterprise grade software system that is primarily driven by Perl 5 and Postgres. It generates about EUR 50 million in revenue every year.
To avoid creating new Perl code from scratch we created a REST API many years ok which new frontends and middlewares use instead of interacting with the core itself. That has been successful to some extent as we can have frontend teams coding in JS/TypeScript without them needing to interact with Perl. But re-writing the API‘s implementation is risky and the company has shied away from that.
Fixing API bugs still require to dive into a Perl system. However, I found it easier turning Python or JS devs into Perl devs than into DB engineers. So, usually, the DB subsystem bears the greater risk and requires more expensive personnel.
You can type pretty well on it after a week or so of usage. I am actually mainly planning on using it as a small lab device for collecting data and on the couch for note taking. So far I've been typing notes in Obsidian and also editing a literature review in latex on it using neovim.
> It looks like adding a defcustom that would disable macro expansion, and basically any attempts to eval the code being edited
Probably, yes. „org-babel“ can execute shell code inside an org document but always asks the user before it does. You can disable this if you want to. No big deal. Should totally work like this in elisp-mode, too.
reply