On that note... Database ID's! They're like pointers. Only untyped. And you might not even get an error if you use the wrong type, just silently get the wrong row. A wrapper class like Id<Person> would have prevented so many of my bugs from compiling (In C#).

Having a garbage collector doesn't prevent a programmer from needing to care about ownership of types, it just means you need to do it less. If I pass a FileStream to a function in C#, is it meant to dispose of it or am I? You need to read the documentation to know. So you're no better off than C's manual management of pointers. Ways to explicitly say "This function will use the object but will not dispose of it" are useful.

yes i write rust how can you tell


Sponsored by:


...and a couple bottles of Afri cola

A cozy space for everyone (* ^ ω ^) ✨

This server doesn't have a specific theme or topic and everyone is welcome to join :)

koyu's personal website

Server Status

Shop on koyu.space Shop

Donate using Liberapay


Proud member of the: Keep The Internet Quirky Association