4 ms·

Going from Python to Go was very easy for me, and I do feel much more productive. I don't want to work with Python ever again. Rust is a beast though, I tried

Going from Python to Go was very easy for me, and I do feel much more productive. I don't want to work with Python ever again. Rust is a beast though, I tried picking it up several times, but lose interest quickly. The language is interesting, but the learning curve is a problem.

kaamkiya 2y ago
This is exactly my experience. I would just add that I do still use Python, because all tools have their uses. I use it for small scripts, and nothing else. Just places where compilation doesn't really make sense.
jochem9 2y ago
Same. Python has a certain elegance when writing it, but the lack of static typing, a nightmare for dependency management (recently had to do a change in Python and spend about 80% of my time getting the dev env en dependencies right) and runtime compilation (slow and you'll error in production) have put me firmly on the Go train. I do want to do Rust in production too. I'm dreaming of moving data engineers to a staticly typed language (crazy to transform data with dynamic typing) and Rust with Polars seems like a great match. The learning curve is steep though.
krab 2y ago
Regarding Python+Django vs. Go, I have an opposite experience. Concurrency is handled much better in Go but that's about it. ORM, web framework, any library is generally worse. On top of that, I miss my exceptions.
adampwells 2y ago
My journey has been from JVM (Java, Scala, Kotlin) -> Go -> Rust, writing web backends, APIs, integrations etc. I don't write 'clever' code, just sticking stuff into Postgres/PostGIS/Neo4J/Clickhouse, some basic business logic and math, returning JSON etc. I have found Rust to be super-productive and a joy to use compared with Go. I don't use the complex parts of Rust; no messing with lifetimes, a little cloning and using Arc<> to share things across threads/tasks. GitHub Copilot in Jetbrains RustRover is very effective at generating accurate Rust CRUD code, handler methods etc. I don't bother with an ORM because it is so fast to write the SQL queries. Having said that, Copilot sucks at anything even slightly complicated and you take a risk asking it to generate code you can't validate quickly. The whole of Rust might be a beast, but I have had a very productive couple of years just using the 'boring' bits and it took a week or two for me to be more productive than in Go writing bog-standard web backend code.
- juneyi 2y ago
  > it took a week or two for me to be more productive than in Go writing bog-standard web backend code. am i understanding that correctly? you started learning/writing rust and it took 2 weeks to be MORE productive? if so, i'm just in awe at your ability to pick it up so fast. I'm an jr dev so it's understandable that it's going to take me a lot longer but damn, i've been at it for over a half a year and I wouldn't say I'm anywhere near more comfortable/productive than my previous languages. Whatever you're doing, keep doing it. much respect.

kaamkiya 2y ago

This is exactly my experience. I would just add that I do still use Python, because all tools have their uses. I use it for small scripts, and nothing else. Just places where compilation doesn't really make sense.

jochem9 2y ago

Same. Python has a certain elegance when writing it, but the lack of static typing, a nightmare for dependency management (recently had to do a change in Python and spend about 80% of my time getting the dev env en dependencies right) and runtime compilation (slow and you'll error in production) have put me firmly on the Go train. I do want to do Rust in production too. I'm dreaming of moving data engineers to a staticly typed language (crazy to transform data with dynamic typing) and Rust with Polars seems like a great match. The learning curve is steep though.

krab 2y ago

Regarding Python+Django vs. Go, I have an opposite experience. Concurrency is handled much better in Go but that's about it. ORM, web framework, any library is generally worse. On top of that, I miss my exceptions.

adampwells 2y ago

My journey has been from JVM (Java, Scala, Kotlin) -> Go -> Rust, writing web backends, APIs, integrations etc. I don't write 'clever' code, just sticking stuff into Postgres/PostGIS/Neo4J/Clickhouse, some basic business logic and math, returning JSON etc. I have found Rust to be super-productive and a joy to use compared with Go. I don't use the complex parts of Rust; no messing with lifetimes, a little cloning and using Arc<> to share things across threads/tasks. GitHub Copilot in Jetbrains RustRover is very effective at generating accurate Rust CRUD code, handler methods etc. I don't bother with an ORM because it is so fast to write the SQL queries. Having said that, Copilot sucks at anything even slightly complicated and you take a risk asking it to generate code you can't validate quickly. The whole of Rust might be a beast, but I have had a very productive couple of years just using the 'boring' bits and it took a week or two for me to be more productive than in Go writing bog-standard web backend code.

juneyi 2y ago
> it took a week or two for me to be more productive than in Go writing bog-standard web backend code. am i understanding that correctly? you started learning/writing rust and it took 2 weeks to be MORE productive? if so, i'm just in awe at your ability to pick it up so fast. I'm an jr dev so it's understandable that it's going to take me a lot longer but damn, i've been at it for over a half a year and I wouldn't say I'm anywhere near more comfortable/productive than my previous languages. Whatever you're doing, keep doing it. much respect.