ymawky is a small, static http web server written entirely in aarch64 assembly for macos. it uses raw darwin syscalls with no libc wrappers, serves static files, supports
GET,HEAD,PUT,OPTIONS,DELETE, byte ranges, directory listing, custom error pages, and tries to be as hardened as possible.why? why not? the dream of the 80s is alive in ymawky. everybody has nginx. having apache makes you a square. so why not strip every single convenience layer that computer science has given us since 1957? i wanted to understand how a web server actually works, something i know little about coming from a low-level/systems background. the risks that come up, the problems that need to be solved, the things you don’t think about when you’re writing python or c.
this (probably) won’t replace nginx, but it is doing something in the most difficult way possible.
↫ Tony “imtomt”
I love this.
One of my good friends had what I consider to be an amazing ability to manually assemble Z80 . It might not mean much these days with GigaFLOPs of processing power in other ISAs but to be able to have that grasp of an architecture and programming for it is really rather cool.
Tony strikes me as being of the same vein, so to speak. Power (heh) to them!
ck3ml,
I wrote a telnet server for DOS in assembly. You’d think it was in the 1990s, but nope I think it was around 2010 when a client needed it and I happened to know assembly.
Looking at it now, it was a 2.7kB .COM file that ran as a TSR. You could run DOS edit and other applications over telnet! It did authentication, keymaps, emulated pressing of CTRL and ALT shortcut keys remotely. Output text screens in full color using ANSI escape sequences and only needed to refresh changed segments of the screen. It was a neat little project.