3 ms·

years ago we switched from python to go. super happy we didnt go for rust, C++ or elixir. go is the get stuff done and make it fast language. my startup would h

years ago we switched from python to go. super happy we didnt go for rust, C++ or elixir. go is the get stuff done and make it fast language. my startup would have had a hard time and not grown as much if it wasn't for go

greenavocado 2y ago
The Rise of ``Worse is Better'' https://web.stanford.edu/class/cs240/old/sp2014/readings/worse-is-better.html https://web.stanford.edu/class/cs240/old/sp2014/readings/wor...
- hot_gril 2y ago
  If you really want "worse is better," it's Javascript. Idk what the use case is here exactly, but if the thing worked in Python, JS was probably a fit.
  - justincredible 2y ago
    [dead]
littlestymaar 2y ago
That's cool if you're happy with Go. I'm pretty sure you'd have been equally happy going to Rust though. Once you go over the first few days of learning curve Rust is very similar to Go I'm terms of productivity. I like the syntax and type system more in Rust, but at the end of the day the language are pretty similar in terms of developer experience if you're doing back end stuff[1]. (Fun fact I learned Rust and Go roughly at the same time in 2015, and Go's tutorial was a big help for my understanding of concurrent programming in Rust, with channels and mutexes, for someone who came from a JavaScript background and had never been exposed to threads before). [1] A cool thing about Rust is that you can use it to learn new stuff that aren't web back-end, but that's a good reason to pick it for side projects, not for using it as a company. Edit: four downvotes in three minute? I must have say something offensive…
- hot_gril 2y ago
  I'm not a downvoter, but in my experience Rust was a learning curve even after a month, causing me to switch a project (software-defined network research prototype) mostly back to C.
  - littlestymaar 2y ago
    It depends where you come from and how surrounded you are with people familiar with the language. If you're working on your own, it can take some time for the key concepts to click. But if you have a mentor that can help you go through the core concepts, then it can be pretty quick. I've been on both sides, I leaned Rust very early and it took me a while to even understand what lifetimes were and wth was `Copy` and `static`, but after that I've been onboarding complete beginners at several companies and they got proficient very quickly with some guidance from me for key concepts. Rust isn't hard, it's just has a few concepts that you need to understand otherwise you're just confused by everything you encounter. But to me wasn't not too different from the effort it took me to understand "wtf are prototypes" when learning JavaScript 15 years ago. When you come from a certain language paradigm and you're learning a language with another paradigm everything sounds so confusing at first, even though the difference aren't actually that big in reality. But you need to be able to overcome the difference before you see the similarities.
    - hot_gril 2y ago
      It was indeed only me working on it. I forget what was the issue exactly, something about constantly forgetting what the "mut", "&", "*", etc symbols did in different contexts. I conceptually understood it since a lot of things were similar to the N languages I already knew, but the syntax was a lot.
- theshrike79 2y ago
  The difference between Go and Rust is that I can (and have) teach any Java coder to be productive in Go in about a week. I couldn't teach _myself_ Rust in a week. Yes, if you're making something where being Correct is a hard requirement - Rust is perfect. But you do need to acknowledge that there is a definite learning curve and the average Job Coder (works from 9-5 and doesn't think about it on their free time) isn't cut out for Rust. If your team is hand-picked 10x coders, Rust is again by far the best choice. It's got fancy PL bells and whistles that keep the dopamine running for experienced people =)

greenavocado 2y ago

The Rise of ``Worse is Better'' https://web.stanford.edu/class/cs240/old/sp2014/readings/worse-is-better.html https://web.stanford.edu/class/cs240/old/sp2014/readings/wor...

hot_gril 2y ago
If you really want "worse is better," it's Javascript. Idk what the use case is here exactly, but if the thing worked in Python, JS was probably a fit.
- justincredible 2y ago
  [dead]

littlestymaar 2y ago

That's cool if you're happy with Go. I'm pretty sure you'd have been equally happy going to Rust though. Once you go over the first few days of learning curve Rust is very similar to Go I'm terms of productivity. I like the syntax and type system more in Rust, but at the end of the day the language are pretty similar in terms of developer experience if you're doing back end stuff[1]. (Fun fact I learned Rust and Go roughly at the same time in 2015, and Go's tutorial was a big help for my understanding of concurrent programming in Rust, with channels and mutexes, for someone who came from a JavaScript background and had never been exposed to threads before). [1] A cool thing about Rust is that you can use it to learn new stuff that aren't web back-end, but that's a good reason to pick it for side projects, not for using it as a company. Edit: four downvotes in three minute? I must have say something offensive…

hot_gril 2y ago
I'm not a downvoter, but in my experience Rust was a learning curve even after a month, causing me to switch a project (software-defined network research prototype) mostly back to C.
- littlestymaar 2y ago
  It depends where you come from and how surrounded you are with people familiar with the language. If you're working on your own, it can take some time for the key concepts to click. But if you have a mentor that can help you go through the core concepts, then it can be pretty quick. I've been on both sides, I leaned Rust very early and it took me a while to even understand what lifetimes were and wth was `Copy` and `static`, but after that I've been onboarding complete beginners at several companies and they got proficient very quickly with some guidance from me for key concepts. Rust isn't hard, it's just has a few concepts that you need to understand otherwise you're just confused by everything you encounter. But to me wasn't not too different from the effort it took me to understand "wtf are prototypes" when learning JavaScript 15 years ago. When you come from a certain language paradigm and you're learning a language with another paradigm everything sounds so confusing at first, even though the difference aren't actually that big in reality. But you need to be able to overcome the difference before you see the similarities.
  - hot_gril 2y ago
    It was indeed only me working on it. I forget what was the issue exactly, something about constantly forgetting what the "mut", "&", "*", etc symbols did in different contexts. I conceptually understood it since a lot of things were similar to the N languages I already knew, but the syntax was a lot.
theshrike79 2y ago
The difference between Go and Rust is that I can (and have) teach any Java coder to be productive in Go in about a week. I couldn't teach _myself_ Rust in a week. Yes, if you're making something where being Correct is a hard requirement - Rust is perfect. But you do need to acknowledge that there is a definite learning curve and the average Job Coder (works from 9-5 and doesn't think about it on their free time) isn't cut out for Rust. If your team is hand-picked 10x coders, Rust is again by far the best choice. It's got fancy PL bells and whistles that keep the dopamine running for experienced people =)