HN2new | past | comments | ask | show | jobs | submitlogin

Yep. Everything comes in cycles, old becomes new again, etc. This is particularly true in the software industry. We're very fad-driven.


Is this the case here too though? My impression was that dynamic languages grew popular because of deficiencies in static type systems, making it hard to express things while requiring a lot of boilerplate and not providing enough runtime safety (e.g. NullPointerException), and a faster feedback cycle, as you need a compile step and need the entire program to be free of type errors. For the first point, type systems have been improving in these regards, and for the second you get instant feedback in statically typed languages without needing to even run anything. Some languages like Roc even let you run code while there are type errors in other code paths.


> Is this the case here too though?

I have no working crystal ball, so I don't know. But I don't see any obvious reason to think it isn't.

If history is any guide, then this is just the latest cycle, and the new hotness will become dynamic again.

Your list of improvements is correct, but I'll just point out that with every cycle, a similar list of improvements is cited as the reason why whatever the fashion of the day is will become The One True Way. So far, such expectations have never been fulfilled.


Counterexamples: structured programming, version control, null safety, unicode. I don't think we're going backwards on those.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: