The iterative nature of art
👋 This page was last updated ~12 years ago. Just so you know.
“Some people don’t understand the iterative nature of art, design and game design.”
“Instead, they try to reach the final version on the first try and get frustrated when it’s not as good as they thought.”
“Aim for the best you can, but know that you will have to iterate, work on it again. Know that it’ll get better on the next step!”
— Dominique Ferland, aka @Dom2D
Here's another article just for you:
A dynamic linker murder mystery
I write a ton of articles about rust. And in those articles, the main focus is about writing Rust code that compiles. Once it compiles, well, we’re basically in the clear! Especially if it compiles to a single executable, that’s made up entirely of Rust code.
That works great for short tutorials, or one-off explorations.
Unfortunately, “in the real world”, our code often has to share the stage with other code. And Rust is great at that. Compiling Go code to a static library, for example, is relatively finnicky. It insists on being built with GCC (and no other compiler), and linked with GNU ld (and no other linker).