You are here |
gavinhoward.com | ||
| | | |
sswam.wordpress.com
|
|
| | | | In my experience, the C programming language is still hard to beat, even 50 years after it was first developed (and I feel the same way about UNIX). When it comes to general-purpose utility, low-level systems programming, performance, and portability (even to tiny embedded systems), I would choose C over most modern or fashionable alternatives.... | |
| | | |
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. | |
| | | |
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.skylight.io
|
|
| | One of the coolest features of Rust is how it automatically manages resources for you, while still guaranteeing both safety (no segfaults) and high performance. Because Rust is a different kind of programming language, it might be difficult to understand what I mean, so let me be perfectly clear: * In |