G3rn0ti
Joined 5 years ago
Joined 5 years ago
You don't even need to buy the cartridge version if you own an SD card adapter.
Great times, anyways. ;)
#+BEGIN_SRC html
#+END_SRC
If you are writing a technical document with a lot of code blocks you can have yasnippet to create the blocks for you by keyboard shortcut.
https://github.com/blahgeek/emacs-lsp-booster
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.
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.
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.
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.
https://twitch.tv/g3rn0ti