Congratulations, this is awesome. One of those "why hasn't someone done this already?" projects.
I can see this becoming transformative and superseding Excel, which is a bold claim to make. But this is compliant (with Excel), performant, extensible, free, and in-browser. This could easily become almost an emacs-level editor.
Think of the interfaces that could be built to this in this?
Why would there be any reason for this to kill excel? Seriously you should try to replace excel entirely rather than merely get a better version of it. If you want to get a better excel just buy excel and actually learn how to use it.
One of the things I love about hacker news is that there's no AI content. The other is that it's like reading a commentary on our encyclopedia. I get to read thought happening.
Apropos of nothing, just saying, and this thread is a great example.
I always want to read more books after a good dose of hacker news.
One of the things I love about hacker news is that there's no AI content. The other is that it's like reading a commentary on our encyclopedia. I get to read thought happen.
Apropos of nothing, just saying, and this thread is a great example.
I always want to read more books after a good dose of hacker news.
Digital stupidity is rife, spreading like a common cold, leaving children everywhere immunocompromised, adults ethically stunted, and technologists waving their conceits like handkerchiefs at a soccer game.
Don't eat rotten fruit. Go read a fuckdamn math text instead, with a nice cup of tea or coffee and a view of the local vegetation in the background. Then take a walk and count your fingers and toes.
The core should be in rust, verfied in lean, and the runtime should be in guile. Literate programming in org-mode should be a hard requirement. Package management should require patch algebra. Macros should be submitted to a leaderboard in a blockchain and yield flair in EUDC. M-x measure-beard-length should require 10000 hours of logged usage and unlock the major mode infinity-categorization.
Tongue-no-longer-in-cheek:
I reckon the C core of Emacs is some of the most battle-hardened code out there. Verification, a-la SEL4, is probably irrelevant but still nice. Guile is modern and performant but Elisp is still its own little joy. Literate programming is always nice until it gets in the way. Straight is good enough for me now. Macros are always cool and a leaderboard would be fun, but patch algebra is really nice, see jujutsu nowadays. And beard length is gendered and so only partially admissable. Infinity categories are way out there and always good for a reference.
Implemented mostly in Guile, with just some native primitives/kernel bits in Rust, makes a lot of sense, for a programmer's application platform in the spirit of Emacs.
> The core should be in rust, verfied in lean, and the runtime should be in guile. Literate programming in org-mode should be a hard requirement. Package management should require patch algebra.
Since I agreed with all of these, I’ll add some more non-ironic, idealistic wishes:
Plugins must be written in sandboxed WebAssembly so you can know what a plugin is capable of without reading the source code. The runtime must be portable so it can run in wasm32-wasi.
When I saw “should be in rust” my instinct was to flame like nobody’s business, glad I kept reading. Lmao. Good slow burn.
Though, not to put too fine a point on it, I know it was in jest, but the core implementation language is the least of my concerns. As long as it is extremely portable, compiles fast, and runs on virtually anything, then whatever the core is, doesn’t matter much to me.
The rest is noise in an expanding universe