Explore >> Select a destination
|
You are here 
|
abhyrama.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. | |
| | | | |
dogweather.dev
|
|
| | | | | Ruby now has three distinct mechanisms for matching values case/when: the older form, based on ===. case/in: the newer structural pattern matching (Ruby 2.7+). => operator: an inline pattern assertion that raises if it fails. That's the high-level summary. Each behaves differently and is worth knowing in detail. After programming in Ruby for years, I... | |
| | | | |
drewdevault.com
|
|
| | | | | [AI summary] The article discusses the author's criteria for choosing programming languages, evaluating their strengths and weaknesses across various languages like C, Go, Rust, Python, and others. | |
| | | | |
www.sevangelatos.com
|
|
| | | So, this is an mirror of a post from John Carmack. Recently I learned that his articles on #AltDevBlog are no longer acessible. So, in order to archive them, I am re-posting them here. These articles are definitely good reads and worth to be preserved. Probably everyone reading this has | ||
