It's tiny; might have embedded use?

tambourine_man · on July 13, 2018

Embedded x86_64? Is that a common thing?

alxlaz · on July 13, 2018

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-Indus... is an industrial computer; 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 · on July 14, 2018

Security is enough of a consideration that any well-established webserver without corporate or foundational backing is instantly unsuitable for serious use.

oneweekwonder · on July 14, 2018

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

imtringued · on July 14, 2018

It is written in Go. That alone makes it safer than an unproven web server written in assembly.

stingraycharles · on July 13, 2018

Definitely looks like it. No library dependencies such like libc, makes it an ideal use case for embedded software.