Congratulations! The two of you easily became two of my biggest role models after I was introduced to web development; its been a pleasure to follow your general trajectories. Thanks for showing us what is possible when you're willing to actually do something!
Yehuda Katz and Steve Klabnik Are Joining the Rust Core Team
51–60 of 135 posts
Re: Yehuda Katz and Steve Klabnik Are Joining the Rust Core Team
#52Re: Yehuda Katz and Steve Klabnik Are Joining the Rust Core Team
#53Congratulations Yehuda and Steve! We've been using Rust in production for awhile now, specifically because of its combo of native speed and memory safety[1]. This bending of traditional tradeoffs has let us implement features that would have been otherwise impossible. Interfacing with Ruby via its C APIs, we are able to do some pretty crazy stuff, like sample memory allocations in production with imperceptible overhe…
Could you define "low-level bitbangers"? It sounds kind of derogatory, but maybe I am reading it wrong.
Re: Yehuda Katz and Steve Klabnik Are Joining the Rust Core Team
#54Congratulations Yehuda and Steve! We've been using Rust in production for awhile now, specifically because of its combo of native speed and memory safety[1]. This bending of traditional tradeoffs has let us implement features that would have been otherwise impossible. Interfacing with Ruby via its C APIs, we are able to do some pretty crazy stuff, like sample memory allocations in production with imperceptible overhe…
Could you define "low-level bitbangers"? It sounds kind of derogatory, but maybe I am reading it wrong.
Low level in term of programming abstraction, not any kind of hierarchy i.e. banging your head against bits and bytes rather than monads and functors
Re: Yehuda Katz and Steve Klabnik Are Joining the Rust Core Team
#55Earlier quoted context omitted.
I believe Yehuda only started coding in 2006? Maybe 2008?
I did my first real coding in around 2005, and quickly got interested in both jQuery and Rails. Really good timing in retrospect!
Considering you've been coding less than a decade, can you comment on what you think the biggest factor was that lead you to developing such a high level of mastery of solid coding principles? Books, mentoring, reading framework and library code thoroughly?
Re: Yehuda Katz and Steve Klabnik Are Joining the Rust Core Team
#56Earlier quoted context omitted.
I replied to this a bit on the other HN thread on this topic: https://news.ycombinator.com/item?id=8741987 TL;DR embedding small libraries with high-performance or low-memory requirements into programs written in high-level languages.
How much C boilerplate of the Ruby C extensions API do you have to write to get Rust to interop with Ruby nicely? I've played with this a bit but still found myself writing a bit of C to wire it all together. It would be nice to hear your approach to this.
wycats has actually been teasing us for a while with a library for exactly that purpose. Here's hoping he gets to releasing it soon. :)
Re: Yehuda Katz and Steve Klabnik Are Joining the Rust Core Team
#57Congratulations Yehuda and Steve! We've been using Rust in production for awhile now, specifically because of its combo of native speed and memory safety[1]. This bending of traditional tradeoffs has let us implement features that would have been otherwise impossible. Interfacing with Ruby via its C APIs, we are able to do some pretty crazy stuff, like sample memory allocations in production with imperceptible overhe…
Could you define "low-level bitbangers"? It sounds kind of derogatory, but maybe I am reading it wrong.
It's a sort of nickname derived from a technique for communication on very cheap microcontrollers.
Re: Yehuda Katz and Steve Klabnik Are Joining the Rust Core Team
#58Earlier quoted context omitted.
It allows you to predictably squeeze more out of your system than you ever could in a higher level language without the worry of weird undefined behavior, buffer overflows, use-after-frees or segfaults. It also has an expressive static type system that draws a great deal from ML and Haskell.
What would be the reason to learn Rust over Haskell? They seem to be about in the same speed ballpark: http://benchmarksgame.alioth.debian.org/u64q/compare.php?lan... Is that not representative, or is the idea that Rust speeds the learning curve with its similarity to Ruby?
If you actually look at the source code, the benchmarks where Haskell beats Rust rely on unsafe functionality, calling out to C libraries, and are heavily optimised and hard to follow. The Rust code on the other hand is idiomatic, safe, and relatively easy to understand.
Re: Yehuda Katz and Steve Klabnik Are Joining the Rust Core Team
#59Earlier quoted context omitted.
How much C boilerplate of the Ruby C extensions API do you have to write to get Rust to interop with Ruby nicely? I've played with this a bit but still found myself writing a bit of C to wire it all together. It would be nice to hear your approach to this.
wycats has actually been teasing us for a while with a library for exactly that purpose. Here's hoping he gets to releasing it soon. :)
Good to know. I look forward to him releasing that. I was about to start writing one myself, which would probably turn out really ugly.
Re: Yehuda Katz and Steve Klabnik Are Joining the Rust Core Team
#60Earlier quoted context omitted.
It allows you to predictably squeeze more out of your system than you ever could in a higher level language without the worry of weird undefined behavior, buffer overflows, use-after-frees or segfaults. It also has an expressive static type system that draws a great deal from ML and Haskell.
Do you have an opinion on how Rust compares to Go?
Rust and Go do not overlap much other than they are both natively compiled, have curly braces and are backed by 'web' companies. Go was designed for building server software and for encouraging standardized, easy to maintain software. Rust on the other hand is generally targeted at the same areas where C and C++ are used for today.