Remacs – A community-driven port of Emacs to Rust

Re:Remacs – A community-driven port of Emacs to Rust by stagger87 on Sunday July 16, 2017 @02:18PM (#14783347)

(I hope I'm not misunderstanding your concern), but a quick search reveals that Rust prefers to statically link, so in this case, remacs would distribute as a 'single' binary. Only the developers (of remacs) would need all the dependencies/crates.

[ Parent | on HN ]

Re:Remacs – A community-driven port of Emacs to Rust by falcolas on Sunday July 16, 2017 @02:40PM (#14783479)

This creates its own headaches as a fix for the next Heartbleed becomes not "upgrade this one shared library", but "upgrade these dozens of individual programs when an update becomes available".

[ Parent | on HN ]

Re:Remacs – A community-driven port of Emacs to Rust by SkyMarshal on Sunday July 16, 2017 @03:14PM (#14783649)

There has always been war b/t static vs dynamic linking. The debate will continue forever, but it doesn't really matter anymore. Each side understands and has solutions to its deficiencies.

[ Parent | on HN ]

Re:Remacs – A community-driven port of Emacs to Rust by fiddlerwoaroof on Sunday July 16, 2017 @10:33PM (#14785278)

Fwiw, lisps have a somewhat interesting third way: you distribute everything in a single image like a statically linked program. But, since that image includes the compiler, it can upgrade itself.

[ Parent | on HN ]

Re:Remacs – A community-driven port of Emacs to Rust by lispm on Monday July 17, 2017 @02:32AM (#14786135)

Or they include a loader and can load code, code which may be compiled somewhere else.

[ Parent | on HN ]

Re:Remacs – A community-driven port of Emacs to Rust by Retra on Sunday July 16, 2017 @03:51PM (#14783822)

Programs all need to update all the time anyway.

[ Parent | on HN ]