2 ms·
> if it seems to work, that is good enough I think that's where many people would disagree with you. Also static types are not only about correctness. They al
by IshKebab 3y ago
> if it seems to work, that is good enough
I think that's where many people would disagree with you.
Also static types are not only about correctness. They also greatly help with understanding, documentation and navigation.
The two biggest third party codebases I've contributed to are VSCode and Gitlab. VSCode was about 10x easier than Gitlab simply because I spent so much time in Gitlab just trying to find the code that a function called, or the code that called a function. (I think Ruby also encourages ungreppable code styles which makes this even worse.)
In VSCode it was pretty much just one click. (Occasionally more because of abstract interfaces, but even then way way nicer.)
Anyway yeah obviously if you don't really care about your code working or being readable then you are going to feel like static types are a waste of your time. That's kind of like saying that showering is a waste of time because you don't need to be clean.
- auggierose 3y ago> I think that's where many people would disagree with you. And they would be wrong, because for some classes of software, if it seems to work, that is actually the definition of working and fulfilling its purpose. Because there is no clear definition of what "correct" would mean. But that's not the point. Read my comments to see where I am coming from.
- IshKebab 3y agoI guess you are talking about art projects? Yeah I don't think you can base a generic argument on a tiny niche programming domain.
- auggierose 3y ago"some" is an existential quantifier. To prove an existential statement, you only need a single example. So of course I can base an argument on that, especially if it just illustrates the range of different purposes of software.
- IshKebab 3y agoThis is a debate, not a mathematical proof.