3 ms·
In my experience, when there's something that offers additional guarantees for additional work, it's very rarely the right solution to completely forgo the guar
by StavrosK 8y ago
In my experience, when there's something that offers additional guarantees for additional work, it's very rarely the right solution to completely forgo the guarantees. This goes for schemas, typing in languages, etc.
Maybe the additional work is too much for the benefit, but it's not that there's no benefit. Forgoing the guarantees usually leads to much more extra work. I think Python's "no types anywhere" was a reaction to Java's "types everywhere", but neither is optimal. Something with gradual typing or type inference has much more bang for its buck, so whenever I see "I use MongoDB because there's no schema to worry about", I always think that it's going to come back and bite someone in the ass.
- kdbeall2 8y ago> I think Python’s “no types anywhere” was a reaction to Java’s “types everywhere” To nitpick, Python actually came before Java. But, the overall sentiment is something I agree with.
- StavrosK 8y agoOh yeah, that's not nitpicking, that's a good point. Replace "Java" with any type-verbose language of the era.