/explore
|
You are here 
|
blog.hao.dev | ||
| | | | |
yieldcode.blog
|
|
| | | | | Take a good look at the following function and try to understand what it's doing. function do_magic(a, b) { return a + b; } | |
| | | | |
yotam.net
|
|
| | | | | A blog about free software and programming | |
| | | | |
www.alfredo.motta.name
|
|
| | | | | [AI summary] Alfredo Motta shares details about upcoming coding workshops in London covering Ruby, Rails, and Javascript to help attendees learn programming and enter the tech industry. | |
| | | | |
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. | ||
