/explore
|
You are here 
|
blog.quaddmg.com | ||
| | | | |
yotam.net
|
|
| | | | | A blog about free software and programming | |
| | | | |
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. | |
| | | | |
boxbase.org
|
|
| | | | | I came up with an idea when studying type theory. I am a vehement proponent of dynamic typing but there are several ideas that require me to explore into type theory so I am studying it. | |
| | | | |
lepisma.xyz
|
|
| | | [AI summary] The author discusses the benefits of adopting optional static type checking with Python 'mypy' and gradually typed languages to improve code maintainability and reduce errors. | ||
