4 ms·

That's impressive, but I couldn't find the reason for it. Was it done just for the challenge, or can their be a use for this kind of server?

yjftsjthsd-h 8y ago
It's tiny; might have embedded use?
- stingraycharles 8y ago
  Definitely looks like it. No library dependencies such like libc, makes it an ideal use case for embedded software.
- tambourine_man 8y ago
  Embedded x86_64? Is that a common thing?
  - alxlaz 8y ago
    It's quite common. "Embedded" doesn't mean just "low power and little number crunching ability", it's just a fancy way of saying "special purpose". E.g.: https://buy.advantech.com/Industrial-Computers/Fanless-Industrial-PCs/model-MIC-7700H-00A1.htm https://buy.advantech.com/Industrial-Computers/Fanless-Indus... is an industrial computer; https://www.edge-core.com/productsInfo.php?cls=&cls2=&cls3=15&id=1 https://www.edge-core.com/productsInfo.php?cls=&cls2=&cls3=1... is a "whitebox" switch, but it's a representative of many OEM/ODM designs. x86-64 is a great architecture for many applications. It's cheap (due to volume), well-understood, has great compatibility, and is pretty much the best-supported architecture when it comes to software. Edit: that being said, no, this doesn't have any embedded use today. Embedded x86 isn't 386 processors anymore. The typical scenario for an embedded x86-64 is "I need to drive this specific application and I want to leverage the Linux/FreeBSD/Windows environment for programming". That already puts you way ahead of the point where writing assembly code is useful performance-wise, and you probably don't want to put ASM code you downloaded off the Internet in a network-facing position :-).
- ashleyn 8y ago
  Security is enough of a consideration that any well-established webserver without corporate or foundational backing is instantly unsuitable for serious use.
  - oneweekwonder 8y ago
    I was under the impression caddy web server mostly developed by one person[0]. I see people these day comparing it to nginx. Everything needs to start somewhere. [0]: https://github.com/mholt/caddy/graphs/contributors https://github.com/mholt/caddy/graphs/contributors
    - imtringued 8y ago
      It is written in Go. That alone makes it safer than an unproven web server written in assembly.
nemasu 8y ago
Yup, initially it was for the challenge and to learn some x86_64 assembly. As for usefulness, personally I use it all the time when I need to serve some static content and don't want to set up Apache or nginx or something else.

yjftsjthsd-h 8y ago

It's tiny; might have embedded use?

stingraycharles 8y ago
Definitely looks like it. No library dependencies such like libc, makes it an ideal use case for embedded software.
tambourine_man 8y ago
Embedded x86_64? Is that a common thing?
- alxlaz 8y ago
  It's quite common. "Embedded" doesn't mean just "low power and little number crunching ability", it's just a fancy way of saying "special purpose". E.g.: https://buy.advantech.com/Industrial-Computers/Fanless-Industrial-PCs/model-MIC-7700H-00A1.htm https://buy.advantech.com/Industrial-Computers/Fanless-Indus... is an industrial computer; https://www.edge-core.com/productsInfo.php?cls=&cls2=&cls3=15&id=1 https://www.edge-core.com/productsInfo.php?cls=&cls2=&cls3=1... is a "whitebox" switch, but it's a representative of many OEM/ODM designs. x86-64 is a great architecture for many applications. It's cheap (due to volume), well-understood, has great compatibility, and is pretty much the best-supported architecture when it comes to software. Edit: that being said, no, this doesn't have any embedded use today. Embedded x86 isn't 386 processors anymore. The typical scenario for an embedded x86-64 is "I need to drive this specific application and I want to leverage the Linux/FreeBSD/Windows environment for programming". That already puts you way ahead of the point where writing assembly code is useful performance-wise, and you probably don't want to put ASM code you downloaded off the Internet in a network-facing position :-).
ashleyn 8y ago
Security is enough of a consideration that any well-established webserver without corporate or foundational backing is instantly unsuitable for serious use.
- oneweekwonder 8y ago
  I was under the impression caddy web server mostly developed by one person[0]. I see people these day comparing it to nginx. Everything needs to start somewhere. [0]: https://github.com/mholt/caddy/graphs/contributors https://github.com/mholt/caddy/graphs/contributors
  - imtringued 8y ago
    It is written in Go. That alone makes it safer than an unproven web server written in assembly.

nemasu 8y ago

Yup, initially it was for the challenge and to learn some x86_64 assembly. As for usefulness, personally I use it all the time when I need to serve some static content and don't want to set up Apache or nginx or something else.