|
|
|
|
|
by zmmmmm
2622 days ago
|
|
Fascinating to see the circle turn further back towards strong / static typing. One of the major things that has kept me using Groovy over the last 10 years was the reluctance to leave optional / gradual typing behind. Now, nearly every major dynamic language has given in and introduced types, so it seems like this idea of hybrid dynamic/typed languages is now fully mainstream. The problem of course, is they are all built on a legacy of untyped code, not to mention giant communities of people with no culture or habit of tying their code. So it's not clear to me that any amount of added language features can actually compensate for that. |
|
Some languages are better from a static POV, and offer some auto features. Some languages are better from a dynamic POV and offer some hinting feature.
You don't want to type your code to do data exploration and analysis, but you may want to extend the original project later to something bigger and move on to types.
There is no such thing as the perfect language for everything anyway. Plus, it's very good that some languages integrates unnatural features to them, for the case where you want to go beyond their initial best case scenario. It won't be perfect, but I don't need perfect, I need programmatic.
The world of programming is vast, the pool of programmers very heterogeneous, and the constraints are super diverse.