The iterative nature of art

👋 This page was last updated ~12 years ago. Just so you know.

Thanks to my sponsors: medzernik, Corey Alexander, Beth Rennie, Leigh Oliver, Tyler Schmidtke, Das Gürteltier, Sarah Berrettini, Lennart Oldenburg, Matěj Volf, Benjamin Röjder Delnavaz, traxys, Samit Basu, Yann Schwartz, Valentin Mariette, Alex Krantz, Daniel Wagner-Hall, hgranthorner, Mateusz Wykurz, Jesse Luehrs, Beat Scherrer and 261 more

“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

Comment on /r/fasterthanlime

(JavaScript is required to see this. Or maybe my stuff broke)

Here's another article just for you:

ktls now under the rustls org

Sep 26, 2024

3 min #rustls · #ktls · #rust

What’s a ktls

I started work on ktls and ktls-sys, a pair of crates exposing Kernel TLS offload to Rust, about two years ago.

kTLS lets the kernel (and, in turn, any network interface that supports it) take care of encryption, framing, etc., for the entire duration of a TLS connection… as soon as you have a TLS connection.

For the handshake itself (hellos, change cipher, encrypted extensions, certificate verification, etc.), you still have to use a userland TLS implementation.