Explore >> Select a destination
|
You are here 
|
blog.samibadawi.com | ||
| | | | |
nurkiewicz.com
|
|
| | | | | When choosing or learning a new programming language, type system should be your first question. How strict is that language when types don't really match? Will there be a conservative, slow and annoying compiler? Or maybe a fast feedback loop, often resulting in crashes at runtime? And also, is the language runtime trusting you know what you are doing, even if you don't? Or maybe it's babysitting you, making it hard to write fast, low-level code? Believe it or not, I just described static, dynamic, weak and strong typing. | |
| | | | |
blog.darklang.com
|
|
| | | | | And their influence on Dark After two decades of coding professionally in a dozen languages, I've come to a conclusion about static and dynamic types: * Static types help you ensure that your changes work, especially for changes that span large parts of the program. This leads to long-term productivity | |
| | | | |
www.bedtime-science-stories.org
|
|
| | | | | I have a 3 years old daughter who has taken a bit of an interest in science. I started this blog after reading the back cover of the book Ba... | |
| | | | |
vit.baisa.cz
|
|
| | | A personal blog and a digital garden of Vít Baisa | ||
