Explore >> Select a destination
|
You are here 
|
blog.darklang.com | ||
| | | | |
vickiboykis.com
|
|
| | | | | What are they? Why are they? | |
| | | | |
chadaustin.me
|
|
| | | | | This may be the only time I weigh in on the static vs. dynamic typing discussion. Each side has its extreme proponents, and people differ in their ability and desire to work in systems with implicit invariants. Many years ago, back when Java and C++ were the Mainstream Languages and Python was the shiny new up-and-comer, I read Bruce Eckel's arguments in support of dynamically typed languages, and some of the nonobvious (at the time) ways you can get more done at higher quality in a more flexible languag... | |
| | | | |
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. | |
| | | | |
jamie-wong.com
|
|
| | | [AI summary] Jamie Wong discusses the tradeoffs between dynamically and statically typed programming languages, exploring how modern languages are attempting to blend the best features of both to improve iteration speed, correctness checking, and development support. | ||
