Explore >> Select a destination
|
You are here 
|
www.honeybadger.io | ||
| | | | |
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? | |
| | | | |
blog.appsignal.com
|
|
| | | | | Let's discover the differences and similarities between Sorbet and the recently released RBS through some practical examples. | |
| | | | |
gavinhoward.com
|
|
| | | There are 8 questions that must be answered to design a good type system. In this post, I attempt to do just that. | ||
