Explore >> Select a destination
|
You are here 
|
acorwin.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. | |
| | | | |
java-source.net
|
|
| | | | | [AI summary] The article discusses various open-source scripting languages and tools compatible with the Java platform, such as Groovy, Jython, BeanShell, Rhino, JRuby, and others, highlighting their features and use cases. | |
| | | | |
128bit.io
|
|
| | | | | I'm still on my journey with exploring F# but I want to look at something with the .Net Core platform itself, so this will apply to both C# and F#. Ahead-Of-Time (AOT) compilation isn't a new concept. Languages like C and C++ need to be compiled before (or ahead of) execution time. The JVM and CLR took a different approach, creating "virtual machines" or runtimes that could run your code, giving us the promise of "write once, run anywhere" or anywhere that has a virtual machine at least. | |
| | | | |
nedbatchelder.com
|
|
| | | Seems like testing and podcasts are in the air... First, I was interviewed on Brian Okken's Python Test podcast. | ||
