|
You are here |
gavinhoward.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. | |
| | | | |
aradaelli.com
|
|
| | | | | [AI summary] The author discusses their experience with the programming language D, highlighting its features, advantages over C/C++, and reasons for preferring it despite its niche status. | |
| | | | |
www.interviewbit.com
|
|
| | | | | One of the most frequently asked questions by people who have just started out their careers in the field of computer science or related fields is which... | |
| | | | |
fsharpforfunandprofit.com
|
|
| | | Building a parser combinator library from scratch | ||