Explore >> Select a destination
|
You are here 
|
blog.ploeh.dk | ||
| | | | |
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. | |
| | | | |
ruudvanasseldonk.com
|
|
| | | | | I am adding a type system to RCL, my configuration language. In part 1, I explain what I want from the type system. | |
| | | | |
blog.samibadawi.com
|
|
| | | | | [AI summary] A developer reflects on the trade-offs between static and dynamic typing systems, discussing their experiences with functional languages like Haskell, Scala, and Clojure in contexts ranging from production stability to NLP exploration. | |
| | | | |
blog.hao.dev
|
|
| | | JavaScript is a dynamically typed language, and that gives it a lot of edge in my opinion. It is one of the most used programming language right now. So definitely worth learning even if people do not want to head towards this direction in their careers. | ||
