Nevermind that it's easy to add types to JS these days if you really want them.
How you architect a system and manage state (and how simple you keep it) has far bigger implications than types.
Nevermind that it's easy to add types to JS these days if you really want them.
How you architect a system and manage state (and how simple you keep it) has far bigger implications than types.
Looking from the other side, this seems like "static typing gives me illusion of safety, and I miss it in dynamic languages". Sure, it might be justified for large projects in the long run, but
> taking the convenience of an untyped language is usually a poor/lazy architectural decision.
sounds like not understanding (or unwilligness to use?) trade-offs involved, due to personal preference.
I don't like these (unintentional?) claims of superiority based purely on personal preference. Static typing is just a tool, with its pros&cons.