Re:Remacs – A community-driven port of Emacs to Rust
by hyperpape on Sunday July 16, 2017 @06:54PM
(#14784528)
If it's hard to upstream code in emacs, doesn't that improve the case for a rewrite/fork?
Re:Remacs – A community-driven port of Emacs to Rust
by swhipple on Sunday July 16, 2017 @11:38PM
(#14785491)
The mkstemp you are seeing is probably the one from gnulib. A lot of GNU software uses their own versions if they detect the platform one is broken; it may be incorrectly replacing it in this case.
https://www.gnu.org/software/gnulib/manual/html_node/mkstemp...
https://github.com/emacs-mirror/emacs/blob/65eee8392ff95f58f...
Re:Remacs – A community-driven port of Emacs to Rust
by mixedCase on Sunday July 16, 2017 @03:21PM
(#14783686)
I don't see how it is any more incremental than what Remacs is trying to do. They're doing a parasitic rewrite of GNU Emacs, it's not a from-scratch implementation.
Re:Remacs – A community-driven port of Emacs to Rust
by ajross on Monday July 17, 2017 @10:19AM
(#14788680)
To be fair: emacs was written in an era where the idea of a "standard" C library was kind of a joke. Those functions provide "no value" today on systems that have been POSIX-valid for decades. They certainly did in the mid-80's when Unix portability was the biggest hassle of the day.
That said, though: wouldn't that argue for things like "remove custom mkstemp" and not "rewrite it all in rust?"
A lot of people have already written about the difficulty of getting changes to fix things like this (or eliminate dead code, etc.) landed in upstream GNU Emacs. Rewriting parts of Emacs in Rust is an interesting idea, and I applaud it as a fun project. But for people who are interested in making more incremental improvements to Emacs, there's a lot of work to be done in the existing C code base to make it smaller and more secure.