/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 ruuda.nl
Abstraction, not syntax
| | nurkiewicz.com
#14: Static, Dynamic, Strong and Weak Type Systems: understand how your language treats data types
7.8 parsecs away

Travel
| | 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.
| | ruudvanasseldonk.com
A type system for RCL: Introduction
1.7 parsecs away

Travel
| | I am adding a type system to RCL, my configuration language. In part 1, I explain what I want from the type system.
| | dehora.net
On Rust - Bill de hÓra
7.9 parsecs away

Travel
| | Back in 2013, I started a series of posts on programming languages I found interesting. One of the languages I wanted to write about at that time was Rust. As often happens, life got in the way, and it's only now that I'm coming round to a long overdue post. This is one of a series of posts on programming languages and you can read more about thathere.
| | blog.derlin.ch
Python, type hints, and future annotations
26.0 parsecs away

Travel
| PEP 563 is activated as soon as you import future annotations. This turns annotations to strings, changing the way we read type information at runtime.