3 ms·
It definitely encourages its developers to suck. More politely, it comes with non-removable training wheels, which makes it OK if you’re getting started as a d
by hedora 8y ago
It definitely encourages its developers to suck.
More politely, it comes with non-removable training wheels, which makes it OK if you’re getting started as a developer, but a terrible choice for projects that will require experienced developers.
- darkpuma 8y agoI would phrase that as "It doesn't encourage developers to get better."
- hedora 8y agoNot my original wording, but it definitely includes roadblocks that prevent developers from progressing after a point. Examples: Type erasure means the standard library doesn’t quite use generics right, so you end up sprinkling unchecked casts all over the place. It is nearly impossible to handle resource lifetimes correctly, even with autoclosables. No unsigned types, so many advanced algorithms are neigh-impossible to express, let alone rediscover. Encapsulation for primitive types comes with a high runtime overhead (cache misses, gc pressure) Package-private doesn’t quite do what you want for large projects, where you want to split API implementations into multiple packages.