Librsvg now requires Rust

Re:Librsvg now requires Rust by BuuQu9hu on Wednesday January 04, 2017 @06:52PM (#13323319)

Not sure it is a good idea to depend on a language with only one implementation.

[ Parent | on HN ]

Re:Librsvg now requires Rust by muizelaar on Wednesday January 04, 2017 @10:46PM (#13324549)

https://github.com/thepowersgang/mrustc is getting closer. Currently it can compile rustc through to failing codegen.

[ Parent | on HN ]

Re:Librsvg now requires Rust by flukus on Wednesday January 04, 2017 @07:15PM (#13323470)

I could see that being a concern for a commercial product. but why is it a concern for an open source one?

[ Parent | on HN ]

Re:Librsvg now requires Rust by jasonm23 on Wednesday January 04, 2017 @07:18PM (#13323504)

https://www.w3.org/TR/webdatabase/

[ Parent | on HN ]

Re:Librsvg now requires Rust by flukus on Wednesday January 04, 2017 @07:25PM (#13323555)

That's a completely different situation.

[ Parent | on HN ]

Re:Librsvg now requires Rust by adamnemecek on Wednesday January 04, 2017 @06:56PM (#13323344)

Why?

[ Parent | on HN ]

Re:Librsvg now requires Rust by BuuQu9hu on Wednesday January 04, 2017 @08:23PM (#13323889)

http://www.dwheeler.com/trusting-trust/

[ Parent | on HN ]

Re:Librsvg now requires Rust by db48x on Thursday January 05, 2017 @04:51AM (#13325956)

The only sure way to beat that type of attack is to write your own compiler on your own hardware, not to rely on a different compiler that someone else wrote.

[ Parent | on HN ]

Re:Librsvg now requires Rust by BuuQu9hu on Thursday January 05, 2017 @11:31PM (#13333966)

The linked paper disagrees.

[ Parent | on HN ]

Re:Librsvg now requires Rust by db48x on Saturday January 07, 2017 @10:09AM (#13344451)

Only if the second compiler is trusted. If I can hack one publicly available compiler, I can hack two; your second compiler should be private.

[ Parent | on HN ]