Live data from Hacker News

TCP HTTP Server written in Assembly

canonical.org

21–30 of 74 posts

Re: TCP HTTP Server written in Assembly

#23

Earlier quoted context omitted.

This is obviously a toy, or PoC.

I don't know about calling it a piece of crap. Seems a little harsh. :-)

I don't normally see 'piece of crap' written as PoC. I'm used to seeing PoS used often. I usually see PoC as 'proof of concept'.

Re: TCP HTTP Server written in Assembly

#26

Earlier quoted context omitted.

This is obviously a toy, or PoC.

I don't know about calling it a piece of crap. Seems a little harsh. :-)

Definitely meant it's ROFL web scale, asynchronous, non-blocking, event driven, message passing, nosql, sharded, clusters of highly available, reliable, high performance, real time, bad ass, rockstar, get the girls, get the funding, get the IPO, impress your mom, impress your cat ... applications.

Re: TCP HTTP Server written in Assembly

#30

As a web developer who isn't familiar with assembly or any web server more barebones than nginx, what benefits does something like this provide? Speed? Could this be a solution for an extremely simple directory/static file web server?

This is normally the kind of question I ask about anything involving HTML/CSS only or JS only =D PoC's based on low-level concepts are the ones that make you curious about everything from top to bottom. Even though assembly is the least abstract and most esoteric of programming (some would argue opposite) spaces, the program actually reveals itself quite quickly knowing just a few tid-bits. This is how you get to see that even the most low-level aspects of programming are quite accessible.
Post reply on HN