3 ms·
That's an interesting opinion. Could you mention one that wasn't fragile? Just to get a sense of the shape of these classes.
by delusional 1y ago
That's an interesting opinion. Could you mention one that wasn't fragile? Just to get a sense of the shape of these classes.
- Expurple 1y agoThey are all fragile for different reasons: dynamic typing (that always leaks through bolted-on type hints anyway), implementation inheritance, null, exceptions, uncontrolled mutation, abuse of reflection and downcasts, weak leaky interfaces that the compiler doesn't check, no help with issues in multithreaded code, insecure defaults, poor semver practices in the ecosystem, poor tooling, fragile runtime dependencies. I use Rust. From what I've read, Swift seems better than the others, with Typescript and Go following closely. All four happen to be widely praised in this thread. To clarify, I don't have "professional experience" with every popular language, including Swift and Typescript too.