In the initial stages I rely on documentation and examples. I need to quickly see how to do things. I don't care about basic things either, I need actual usable patterns and stuff that gets things done -- I may venture into non-basic territory quite fast.
As long as I can be productive I'll tend to stick with a language a while. My dislike tends to grow as my projects grow and I realize the features that it's missing, or I start to notice the redundancy or inconsistencies in a language. It takes a fairly long time to get to this point.
If frustration comes early I'll be disuaded from the language. This has been my story with Rust so far -- were it not for my stream where I'm forcing myself to learn it, I would have abandoned Rust within the first month or so. I also find it's documentation to be extensive, but quite bad. Lots of filler, not much usable material.
IDE features never factor in for me. As I jump between so many languages I've just come to expect limited and incomplete tooling.
I need actual usable patterns and stuff that gets things done
Definitely, I think a lot of languages neglect the examples beyond the "here's how you use the syntax" ones - ideally there should be some complete projects too, so you can get a vibe of what it's like to actually develop something substantial.
I totally understand your frustration with Rust from time to time - it's one of those languages where everything's wonderful when things are working well, but then you have those days where you end up in borrowcheck hell and nothing seems to work and you want to throw your computer out of the window. I think Rust could use some more documentation for the latter case.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
In the initial stages I rely on documentation and examples. I need to quickly see how to do things. I don't care about basic things either, I need actual usable patterns and stuff that gets things done -- I may venture into non-basic territory quite fast.
As long as I can be productive I'll tend to stick with a language a while. My dislike tends to grow as my projects grow and I realize the features that it's missing, or I start to notice the redundancy or inconsistencies in a language. It takes a fairly long time to get to this point.
If frustration comes early I'll be disuaded from the language. This has been my story with Rust so far -- were it not for my stream where I'm forcing myself to learn it, I would have abandoned Rust within the first month or so. I also find it's documentation to be extensive, but quite bad. Lots of filler, not much usable material.
IDE features never factor in for me. As I jump between so many languages I've just come to expect limited and incomplete tooling.
Definitely, I think a lot of languages neglect the examples beyond the "here's how you use the syntax" ones - ideally there should be some complete projects too, so you can get a vibe of what it's like to actually develop something substantial.
I totally understand your frustration with Rust from time to time - it's one of those languages where everything's wonderful when things are working well, but then you have those days where you end up in borrowcheck hell and nothing seems to work and you want to throw your computer out of the window. I think Rust could use some more documentation for the latter case.