5 ms·
C or Rust would be perfect. No GC runtime, no name mangling, fast, great ffi story. Rust needs to start edging out Go for new tools. Kubernetes, Envoy, IPFS, e
by echelon 7y ago
C or Rust would be perfect. No GC runtime, no name mangling, fast, great ffi story.
Rust needs to start edging out Go for new tools. Kubernetes, Envoy, IPFS, etc. would have benefitted from it.
It might not have been time four years ago, but it's time now.
- momack2 7y agoThere's actually a new Rust-IPFS implementation looking for more contributors. Seems to be moving pretty fast - https://github.com/ipfs-rust/rust-ipfs https://github.com/ipfs-rust/rust-ipfs
- spsoto 7y agoEnvoy is written in C++, not Go.
- echelon 7y agoI'm aware. The creator occasionally pokes fun at the Rust folks for arguing that Envoy should have been written in Rust. And rightly so--Rust wasn't mature at the time Envoy was written. If we revisit that now, C++ is the wrong language to start Envoy in today.
- ncmncm 7y agoCitation needed.
- keeganpoppen 7y agoa citation is most definitely not needed. it's obviously a fucking opinion. and they are under absolutely no obligation to meet your standard of proof to demonstrate anything to you. clearly citations are not a necessary condition to posting-- this comment has no citations, but yet... hey look-- it's been posted! the horror! classic HN obnoxious "citation needed" commentary strikes again. i swear i'm just gonna keep doing this every time i see this... until i get bored and give up, i guess.
- ncmncm 7y agoJeez, calm down. "Citation needed" generates no more obligation than the original unsupported opinion did. Would you blow up the same way about "I disagree"? The fact is, most opinions about what language somebody else ought to write their next library in are worth about what they cost to post. Another is that, trendiness notwithstanding, Rust right now is best suited for a library few people will need. That may change in five or ten years. It might well not.
- keeganpoppen 7y agoCitation needed.
- tadfisher 7y agoKeybase and KBFS as well.
- stryan 7y agoRust will start edging out Go once Rust becomes easier than Go to prototype/start projects. Rust is a great language, but right now I can start a project in Go and have someone else start a project in Go and have something up and working in a week. Rust still takes significantly longer to learn and/or find skilled developers for. Go is up there with Python in terms of "Get something out now".
- thefounder 7y ago>> Rust will start edging out Go once Rust becomes easier than Go to prototype/start projects. I guess that time will never come...unless Go somehow looses its way
- rosywoozlechan 7y agoRust isn't that difficult to prototype or start projects with? What trouble do you run into? I think the hardest parts to understand are the concepts of borrowing, lifetimes, and ownership, but you don't have to know all the subtleties of that to prototype. A basic understanding is fine to get started with. Just like a developer doesn't have to understand all the subtleties of generics to get started with either, lots of devs don't know what covariant or contravariant means and use generics.
- plerpin 7y agoUnderstanding the concepts is one thing, applying them is another thing entirely. The Rust compiler is an incredibly difficult beast to placate.
- drudru11 7y agoRust does name mangling by default. However, you can turn it off per symbol just like in C++.