5 ms·

For devs, equally familiar in rust and python and ignoring libraries, would you say development speed in both languages is almost the same?

siscia 9y ago
I really don't think that I could code any faster of what I code in rust. Especially if you consider the overall quality of the work. In my humble opinion python give the impression to move fast, but when you need to maintain the code base the rust compiler is simply too wonderful.
- chc 9y ago
  I suspect people probably can do it a bit faster in Python, but like you say, you wouldn't necessarily end up with the same quality of work. The Rust code is likely to be quite fast and very solid, whereas the Python code is likely to be "eh, fast enough" and "stable as long as nobody says the word 'thread' within a 10-block radius."
mlindner 9y ago
For me writing Python is fast, until you need to rewrite it when you inevitably refactor. For Python that's an agony, for me.
mquander 9y ago
I'm more familiar with Python than Rust right now, but I feel like after adjusting for amount-I-have-to-look-up-standard-library-things my development speed is similar. The biggest advantage Python gets is IPython.
staticassertion 9y ago
I write python for most of the day, professionally. I write Rust at home. I'd say I spend similar time on the same problem with both, maybe a bit more upfront on Rust and a bit more on the tail with Python. This is, of course, disregarding libraries.
always_good 9y ago
Higher dimensional things are trivial in other languages while they are nonobvious in Rust. For example, this week I was working on a mechanism for one request to start a future and then all further requests for that resource to await that same future. I implemented it in less than 5 minutes in Node by just storing Promises in a map. But I'm still not sure of the ideal solution in Rust. It's definitely outside of my familiarity zone. But what I'm finding over the months is that my routine Rust code is pretty fast now once I've run the gauntlet of experiencing the same compiler errors over and over. And when I reach for Rust instead of Node or Python, it takes longer but my executable is 3mb and it's much faster without much additional expense. Also, it's tough to do async work in an ecosystem that isn't async-everything, something easy to take for granted in Node and Go.

siscia 9y ago

I really don't think that I could code any faster of what I code in rust. Especially if you consider the overall quality of the work. In my humble opinion python give the impression to move fast, but when you need to maintain the code base the rust compiler is simply too wonderful.

chc 9y ago
I suspect people probably can do it a bit faster in Python, but like you say, you wouldn't necessarily end up with the same quality of work. The Rust code is likely to be quite fast and very solid, whereas the Python code is likely to be "eh, fast enough" and "stable as long as nobody says the word 'thread' within a 10-block radius."

mlindner 9y ago

For me writing Python is fast, until you need to rewrite it when you inevitably refactor. For Python that's an agony, for me.

mquander 9y ago

I'm more familiar with Python than Rust right now, but I feel like after adjusting for amount-I-have-to-look-up-standard-library-things my development speed is similar. The biggest advantage Python gets is IPython.

staticassertion 9y ago

I write python for most of the day, professionally. I write Rust at home. I'd say I spend similar time on the same problem with both, maybe a bit more upfront on Rust and a bit more on the tail with Python. This is, of course, disregarding libraries.

always_good 9y ago

Higher dimensional things are trivial in other languages while they are nonobvious in Rust. For example, this week I was working on a mechanism for one request to start a future and then all further requests for that resource to await that same future. I implemented it in less than 5 minutes in Node by just storing Promises in a map. But I'm still not sure of the ideal solution in Rust. It's definitely outside of my familiarity zone. But what I'm finding over the months is that my routine Rust code is pretty fast now once I've run the gauntlet of experiencing the same compiler errors over and over. And when I reach for Rust instead of Node or Python, it takes longer but my executable is 3mb and it's much faster without much additional expense. Also, it's tough to do async work in an ecosystem that isn't async-everything, something easy to take for granted in Node and Go.