The README doesn't say much about whether and how the rewrite would differ from the main Emacs implementation in terms of threading architecture. A major problem (I think this is an uncontroversial statement) with the main Emacs implementation is that it is fairly common, in every day use, to block the main thread responsible for accepting keyboard input and repainting the screen etc. This (again, uncontroversial I t…
Remacs – A community-driven port of Emacs to Rust
71–80 of 181 posts
Re: Remacs – A community-driven port of Emacs to Rust
#72Re: Remacs – A community-driven port of Emacs to Rust
#73Re: Remacs – A community-driven port of Emacs to Rust
#74This looks like a lot of work for what amounts to very little end-user benefit. Honestly, I'd rather see more progress on the Emacs Lisp/Guile migration than on a putative C/Rust migration. At least with the Guile switch, it's something that will have an obvious (and probably positive) impact on the people that use the editor.
For big rewrites, I like to see someone who's been burned by a failed rewrite at the helm. They'll be much more aware of the pros and cons, and at far less risk of underestimating the effort involved, or the value of working code.
(I'm not saying remacs is the same thing by any means, but the relationship between effort expended and the type of value realized is something I've become more attuned to the older I get. Maybe it's a mild mid-life crisis, but I'm pretty cognizant these days that there's an upper bound on the length of time we have available.)
Re: Remacs – A community-driven port of Emacs to Rust
#75Earlier quoted context omitted.
349,615 lines of C 1,632,280 lines of elisp
Also... I have dug the emacs sources for a while and i can testify that many times, function have two, three (sometimes more) actual implementations that gets actually built depending on configuration (example: sunos va dos vs linux vs win32 version of function foo). So... Yeah. The c lines are in a way, "overcounted".
Re: Remacs – A community-driven port of Emacs to Rust
#76This looks like a lot of work for what amounts to very little end-user benefit. Honestly, I'd rather see more progress on the Emacs Lisp/Guile migration than on a putative C/Rust migration. At least with the Guile switch, it's something that will have an obvious (and probably positive) impact on the people that use the editor.
The sons of Hermes love to play
And only do their best when they
Are told they oughtn't;
Apollo's children never shrink
From boring jobs but have to think
Their work important.
Re: Remacs – A community-driven port of Emacs to Rust
#77Re: Remacs – A community-driven port of Emacs to Rust
#78Not intended to be a port, but I occasionally search for an editor that is customizable in Python to the extent Emacs is. Leo Editor ( http://leoeditor.com ) fits that bill. It's been around since the 90's (and the web page looks like it's from the 90's). Even though it has many users, the documentation is quite poor. If I had another life to live, I would learn it well and improve the docs - and then port over every…
Re: Remacs – A community-driven port of Emacs to Rust
#79Earlier quoted context omitted.
STOP/ I just think that before judging remacs everyone had to read this blogpost: http://www.wilfred.me.uk/blog/2017/04/30/remacs-talk-transcr...
gotta love this line: "We aim to be a drop-in replacement with bug-for-bug compatibility."
Re: Remacs – A community-driven port of Emacs to Rust
#80This looks like a lot of work for what amounts to very little end-user benefit. Honestly, I'd rather see more progress on the Emacs Lisp/Guile migration than on a putative C/Rust migration. At least with the Guile switch, it's something that will have an obvious (and probably positive) impact on the people that use the editor.
I don't know if it's a priority but it would be cool to see rendering speed improved.