Explore >> Select a destination
|
You are here 
|
typesanitizer.com | ||
| | | | |
tech.preferred.jp
|
|
| | | | | Most computer applications can be configured to behave a certain way, be it via command line flags, environment variables, or configuration files. For you | |
| | | | |
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. | |
| | | | |
blog.jooq.org
|
|
| | | | | Sometimes there are these moments of truth. They happen completely unexpectedly, such as when I read this tweet: https://twitter.com/whileydave/status/536422407297171457 David is the author of the lesser-known but not at all lesser-interesting Whiley programming language, a language that has a lot of static type checking built in it. One of the most interesting features of the... | |
| | | | |
boxbase.org
|
|
| | | Dart and TypeScript introduce optional static typing, which is then used in every example. It makes me feel troubled. Are they implying that all production code should always be statically typed? Probably no. Is someone getting that idea? | ||
