Live data from Hacker News

Websocketd

websocketd.com

11–20 of 233 posts

Re: Websocketd

#11
post #2

So, all of the same sorts of scaling problems as inetd?

Well, unless it's doing something exceedingly clever, it looks like it will be launching one process per connection.

For communication servers, this could prove a challenge – you'll probably want to use some kind of pub-sub architecture. By the time you've gone down that road, you could've gone down one of the more robust paths.

Still, this looks great for smaller apps. And, it seems a great way to prototype – especially if your favourite language doesn't have great websocket support.

Re: Websocketd

#12
post #10

Ok I know the software-today-is-so-bloated trope is overplayed but... "the UNIX way"? The compiled Linux x86_64 binary is 7 megabytes. All of System V combined was not that big.

SVR4 came out 30 years ago. I think it's time to let it go.

Re: Websocketd

#13
post #10

Ok I know the software-today-is-so-bloated trope is overplayed but... "the UNIX way"? The compiled Linux x86_64 binary is 7 megabytes. All of System V combined was not that big.

SVR4 came out 30 years ago. I think it's time to let it go.

I'm fine with letting it go! I just don't understand why they're claiming this is "the UNIX way" as if that's a good thing.

Re: Websocketd

#14
post #10

Ok I know the software-today-is-so-bloated trope is overplayed but... "the UNIX way"? The compiled Linux x86_64 binary is 7 megabytes. All of System V combined was not that big.

Is unix defined as having small binaries? I don't think that's true. Yes, it's statically linked and as a result somewhat large.

This is a program built around executing programs and communicating over pipes. It's composing programs together. I think that's certainly UNIX-ish.

Re: Websocketd

#15
post #10

Ok I know the software-today-is-so-bloated trope is overplayed but... "the UNIX way"? The compiled Linux x86_64 binary is 7 megabytes. All of System V combined was not that big.

> Written in Go

I have a fairly simple web-app written in go – no websockets, just net/http. I just checked and the binary size is 6.8 megabytes.

There's a lot in there. For starters, there's the go runtime. Then there's the HTTP server.

I suspect there may be ways to improve on the binary size if it mattered so much. xz gets it down to 2.1MB, suggesting there's some redundancy in there.

Re: Websocketd

#17

How do posts like this end up at #2 on the front page with just one comment? Websocketd doesn't strike me as an particularly popular or well known tool.

I think the velocity of the votes and the unique-ness of their geography matters a lot more than comments or discussions.

> unique-ness of their geography

The location of the server is a factor??

Re: Websocketd

#18
post #6

Websocketd is neat. It inspired me to make the websocket directive in Caddy: https://caddyserver.com/docs/websocket

Aha! My first thought was "Why use this instead of Caddy's websocket support?"

Answer: Websocketd came first.

Re: Websocketd

#19
is it me, or does the site look really similar to letsencrypt.org? I looked on both sites and neither say they're using a template.

Re: Websocketd

#20

Earlier quoted context omitted.

I think the velocity of the votes and the unique-ness of their geography matters a lot more than comments or discussions.

> unique-ness of their geography The location of the server is a factor??

The location of the voter.
Post reply on HN