3 ms·
It can never be the Emacs of web browsers because the browser engine is written in C/C++, not Lisp and therefore minimally extensible through a very restricted
by armitron 3y ago
It can never be the Emacs of web browsers because the browser engine is written in C/C++, not Lisp and therefore minimally extensible through a very restricted API that is not even controlled or influenced in any way by the Nyxt team. I guess they could fork an engine but good luck with that.
Last I checked, it didn't even support uBlock origin. That alone makes it a no-go for me and I imagine most folks who visit HN.
- greggyb 3y agoThe Emacs of text editors, Emacs itself, has a core written in C, not Lisp. The scotsmen are looking pretty sparse by your threshold (;
- armitron 3y agoExcept: - The Emacs team is in full control of both the C parts and the Lisp parts of Emacs. Exposing a C bit to Lisp, or introducing changes to the C core to benefit the Lisp parts, is frequently taking place. - What most people perceive as Emacs is implemented in Lisp and is extensible in Lisp. The C "core" is mostly the GC, low-level VM implementation and OS interface. Hardly bits and pieces that one would like to extend in Emacs Lisp.
- slondr 3y agoNyxt is designed to be engine agnostic, which means it had a defined api you could plug any engine into, even one you theoretically write yourself. Obviously this is impractical, but I’ve seen criticisms that emacs doesn’t have that exact ability — see the project mage docs for a detailed explanation of one of those criticisms.
- lproven 3y ago> Last I checked, it didn't even support uBlock origin. That alone makes it a no-go for me and I imagine most folks who visit HN. Privoxy? Although I use both, myself: Privoxy and µBlock Origin.