Explore >> Select a destination
|
You are here 
|
www.sebastiansylvan.com | ||
| | | | |
jamie-wong.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. | |
| | | | |
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. | |
| | | | |
andreabergia.com
|
|
| | | This post is part of the Languages Opinion series. Languages opinion - part one - JVM Languages opinion - part two - Rust ??thispost Languages opinion - part three - Javascript and Typescript Welcome back to my mini-series about programming languages. In this post, we will talk about one of the most interesting programming languages that I have seen in a long while: Rust. | ||
