3 ms·

Exactly, I did startup before, and my take is: Rust is absolutely the worst choice for startups. to survive startup, you need a large pool of talents, mature a

Exactly, I did startup before, and my take is: Rust is absolutely the worst choice for startups. to survive startup, you need a large pool of talents, mature and verified and boring stack, easy to find tutorials, etc. The least thing you want is to spend cycles on fancy new bleeding unstable languages to build your earth shaking product.

Curious_Furious 4y ago
>you need a large pool of talents Forgive me if I'm quoting you out of context but the article mentions receiving 4000 applicants over 8 weeks time. I've hired (primarily) for Java and DBA positions, and we would be absolutely thrilled if we got even 40 applicants.
- linkdd 4y ago
  "pool of talents" vs "pool of people who jumped on the hype train 2 weeks ago" Many people are searching for Rust jobs, but few have a really strong experience with it.
- synergy20 4y ago
  "Many didn’t actually have Rust experience at all and that’s fine, they were just interested in the idea" -- to me, that's _not_ fine. startup needs to move fast to stay above the water, it's not the best place to learn 'coding in Rust 101' IMHO
  - sn9 4y ago
    In a pool of 4000, the fact that many didn't have experience with Rust doesn't mean that there weren't also many that did have experience. You could just filter the CVs for Rust experience and then take the most impressive 10 or 100 to interview.
deleted 4y ago
[deleted]
tialaramex 4y ago
> fancy new bleeding unstable language Where does a language magically go from "new bleeding unstable" to something you think is suitable to use at a startup ? Rust 1.0 was in 2015, seven years ago. Do you think a startup should also avoid the "fancy new" ES6 with "let" and arrow functions ?
- javcasas 4y ago
  When I see people complaining about "experimental", "new bleedy unstable" I always picture some weak developer complaining about the language not being Java 1.4 and having to learn other stuff that is different from enterprise OO invented after the year 2000. See Rust (7 years already), Haskell (older than Java), React (9 years). They all miss their 5 million LoC mudball at the bank, because that's all they know how to do.

Curious_Furious 4y ago

>you need a large pool of talents Forgive me if I'm quoting you out of context but the article mentions receiving 4000 applicants over 8 weeks time. I've hired (primarily) for Java and DBA positions, and we would be absolutely thrilled if we got even 40 applicants.

linkdd 4y ago
"pool of talents" vs "pool of people who jumped on the hype train 2 weeks ago" Many people are searching for Rust jobs, but few have a really strong experience with it.
synergy20 4y ago
"Many didn’t actually have Rust experience at all and that’s fine, they were just interested in the idea" -- to me, that's _not_ fine. startup needs to move fast to stay above the water, it's not the best place to learn 'coding in Rust 101' IMHO
- sn9 4y ago
  In a pool of 4000, the fact that many didn't have experience with Rust doesn't mean that there weren't also many that did have experience. You could just filter the CVs for Rust experience and then take the most impressive 10 or 100 to interview.

deleted 4y ago

[deleted]

tialaramex 4y ago

> fancy new bleeding unstable language Where does a language magically go from "new bleeding unstable" to something you think is suitable to use at a startup ? Rust 1.0 was in 2015, seven years ago. Do you think a startup should also avoid the "fancy new" ES6 with "let" and arrow functions ?

javcasas 4y ago
When I see people complaining about "experimental", "new bleedy unstable" I always picture some weak developer complaining about the language not being Java 1.4 and having to learn other stuff that is different from enterprise OO invented after the year 2000. See Rust (7 years already), Haskell (older than Java), React (9 years). They all miss their 5 million LoC mudball at the bank, because that's all they know how to do.