I think that it is often a mistake to associate code quality with tools. Code quality depends on the developers' quality. I have seen many teams racing to implement the next shiny technology in the hope that it will solve their problems when their main problem is the way they code.
Bad code with types is as bad (or worse) than a bad code without types.
But, yes. Types are convenient, and I hope that there is a good way to introduce them to Ruby, without compromising the natural expressiveness of the language.
I agree, which is why we haven’t rushed to adopt Typescript or other things mentioned here. But I do think it’s the kind of thing that definitely could improve code quality. I’m not itching to be super early adopters though either.
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.
I think that it is often a mistake to associate code quality with tools. Code quality depends on the developers' quality. I have seen many teams racing to implement the next shiny technology in the hope that it will solve their problems when their main problem is the way they code.
Bad code with types is as bad (or worse) than a bad code without types.
But, yes. Types are convenient, and I hope that there is a good way to introduce them to Ruby, without compromising the natural expressiveness of the language.
I agree, which is why we haven’t rushed to adopt Typescript or other things mentioned here. But I do think it’s the kind of thing that definitely could improve code quality. I’m not itching to be super early adopters though either.