/explore
|
You are here 
|
blog.darklang.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. | |
| | | | |
vickiboykis.com
|
|
| | | | | What are they? Why are they? | |
| | | | |
lexi-lambda.github.io
|
|
| | | | | [AI summary] An article exploring a philosophical shift in programming from viewing types as restrictive constraints to designing data structures via axioms to ensure correctness by construction. | |
| | | | |
danluu.com
|
|
| | | |||
