5 ms·
Use the right tool for the job. If you need to barter with your compiler about the most efficient way to store data in memory, going for a strongly typed langu
by beders 3y ago
Use the right tool for the job.
If you need to barter with your compiler about the most efficient way to store data in memory, going for a strongly typed language is ... advisable.
Building a fintech solution that requires supporting ever changing data models over time alongside business logic that also changes over time: use a Lisp :)
- klysm 3y agoChanges over time is a situation where I'd prefer static types. If I change the shape of some data, why would I ever want a system that didn't tell me what I just broke at compile time?
- shepherdjerred 3y ago> ever changing data models over time alongside business logic that also changes over time This is the exact case where a statically typed language shines. If you update your business logic or refactor, the compiler can let you know what needs to be updated for the new data model.