What they don't teach you about sockets
In order to effectively write applications that communicate via sockets, there were some realizations I needed to make that weren't explicitly told to me by any of the documentation I read.
Hi, I'm Macoy Madson. I am a software engineer doing independent software contracting. You can check out my résumé .
Visit macoy.me → RSS feedOn Hacker News Dec 2020 – Oct 2022
Systems & Performance 2Software Engineering 2Programming Languages 1Games & Graphics 1
In order to effectively write applications that communicate via sockets, there were some realizations I needed to make that weren't explicitly told to me by any of the documentation I read.
Update: See the Hacker News thread , /r/programming , /r/ProgrammingLanguages , /r/gamedev , and /r/lisp posts for discussions on this article and Cakelisp.
I'm writing a linker. It's an unusual linker. It's focus is not on producing executable files. Instead, its focus is to facilitate rapid iteration on a program without having to re-link or re-open it after making changes. It is hot-loading of code at an object-file granularity.