News for hackers. Stuff that matters.

A comment on JavaScript to Rust and Back Again: A Wasm-Bindgen Tale. Parent comment

Re:JavaScript to Rust and Back Again: A Wasm-Bindgen Tale by steveklabnik on Wednesday April 04, 2018 @03:30PM (#16758089)
It's still too early. There's tons of good reasons to write C code today for many projects. Furthermore, there's so much C code out there that even if nobody wrote a single new line of C today, it'd be decades before it would go away.

It's really about growing the pie rather than replacement anyway, in my opinion.

[ Parent | on HN ]
Re:JavaScript to Rust and Back Again: A Wasm-Bindgen Tale by carlmr on Thursday April 05, 2018 @03:08AM (#16762542)
>even if nobody wrote a single new line of C today, it'd be decades before it would go away.

But then we can get sweet sweet COBOL level salaries in 40 years.

[ Parent | on HN ]
Re:JavaScript to Rust and Back Again: A Wasm-Bindgen Tale by mmstick on Saturday April 07, 2018 @10:31PM (#16784276)
Although, a lot of us are working towards replacement of C in a lot of areas. Being able to say you've written something in Rust is one thing, but having the whole stack Rust all the way down is something else. Not to mention, it's fairly simple to create C bindings from Rust libraries using Cargo workspaces and cbindgen.
[ Parent | on HN ]