2 ms·
It's really pretty straight forward, I pick a simpler project from my list I'd like to do that seems like a good fit for the goals of the language, then I write
by AnIdiotOnTheNet 9y ago
It's really pretty straight forward, I pick a simpler project from my list I'd like to do that seems like a good fit for the goals of the language, then I write it in that language.
Problems and friction are exposed pretty quickly, but you have to push through those to see if the good parts of the language make up for them. I find that if, after a short while, I don't have to force myself to write the code, and if I can dream up ways to solve any problems I encounter without turning to the documentation, then I've found a really good fit. Sometimes you find that the initial friction was largely just a matter of coming from another language's mindset.
If you find instead that you're not wanting to write code, that you're spending a lot of time fighting it or scowering the documentation or getting the build to work, then my opinion is that the language isn't worth learning anyway so it's best to move on.