14 ms·
Show HN: Goatee – Redis, WebSocket notifications in Go
Hey guys and gals! I'm learning Go at the moment and LOVING it. I was hoping to get constructive feedback on a project I'm working on - goatee - which is a notification server that utilizes Redis pub/sub and WebSockets. It's fairly bare-bones at the moment but I'm hoping to add in a lot more features as time goes on such as queueing and WebSocket channel subscriptions (via Go Socketio possibly).
- johnernaut 13y agoHey guys and gals! This is a project I'm undertaking to help myself learn Go - which I think is AWESOME so far. Any suggestions or criticisms would be appreciated. I hope to add more features as time goes on (and possibly swap out the generic WebSocket implementation with go-socketio).
- almosnow 13y agoThat name almost made me not click on the link...
- gyepi 13y agoIt's hard to come up with good names for software projects. I agree, some are silly, but goatee seems pretty OK. I have an unreleased template system, also written in Go, named goatee. I choose it because I thought it was a nice riff on moustache.
- almosnow 13y agoYeah it's cool, just reminded me of goatse
- TeMPOraL 13y agoEnglish is not my first language, so it might be because of that, but... I can't see any connection between "goatee" and "moustache", neither in spelling nor pronunciation. With "goatse", on the other hand...
- sprobertson 13y ago(The connection there is that mustache is an existing templating system, and goatee is another kind of facial hair)
- dec0dedab0de 13y agoI can't see any connection between "goatee" and "moustache" A goatee is a style of facial hair.
- TeMPOraL 13y agoAh, ok, now I got it, thanks :).
- TeMPOraL 13y agoFor me, it made this link stand out. I was thinking "am I so tired, or did Goatse-inspired something just got to the frontpage of HN?". With dogecoins being all the craze this days, I wouldn't even be much surprised...
- sauerbraten 13y agoWhat a coincidence, I see you use JSON config files: I wrote a tiny package to parse commented JSON files not long ago, maybe it would be a good fit for Goatee? https://github.com/sauerbraten/jsonconf https://github.com/sauerbraten/jsonconf
- johnernaut 13y agoAwesome! I'll check it out.
- rch 13y agoWhere's the license?
- johnernaut 13y agoUpdated with MIT.
- rch 13y agoWell done. Thanks!
- ukd1 13y agoWhy does this have zero tests?
- gyepi 13y agoI have noticed that there are generally three kinds of software releases. 1. No code, just vaporware. 2. Some code, no to few tests, very little documentation. 3. Well written code, lots of tests, lots of documentation. The first is annoying. The second sometimes contains interesting snippets if you're willing to dig. I read the code but am unlikely to use it. The last kind, when I find it, is gold. I use it, read the code, and refer back to it. I have a theory that these kinds of code correspond to intent. Some people want to get something out (sometimes just words) and others want to provide something useful. My zen koan is: if it were not for the chaff, you might not have wheat.
- johnernaut 13y agoThanks for checking out the repo! I'm hoping to have tests up in the next couple of days. This started out as a fool-around project and I wasn't actually anticipating it getting any attention. Tests are the top priority at the moment.
- AYBABTME 13y agoI don't understand, you've submitted the project here yourself?
- zimbatm 13y agoI while ago I wrote something similar with a friend for fun. Redis, ServerSentEvents and Go: https://github.com/vivienschilis/eddy/ https://github.com/vivienschilis/eddy/ It's not so well documented but it's practically the same except that it uses ServerSentEvents on the client and has buffers so no message is ever dropped. Each messages contains the payload, a TTL and a channel size. The TTL is used to expire a channel automatically and the channel size can be used for example to create 1-deep channels for updating values like progress.
- johnernaut 13y agoThis is really great - thanks for sharing! I'll definitely check it out more when I have some time.
- zimbatm 13y agoFeel free to PM me if you want to discuss the architecture/code/... @zimbatm on twitter
- calgaryeng 13y ago404.
- zimbatm 13y agoEDIT: sorry I didn't notice that the project is set to private and I don't have the perms to change it. It's not secret, contacting vivien to fix this.
- saiko-chriskun 13y ago404 for me as well. and don't see it on https://github.com/vivienschilis?tab=repositories https://github.com/vivienschilis?tab=repositories
- j_s 13y agomay be a private repo
- jonpaul 13y agoShameless plug, but I also have a Go module named Goatee. However, it's a testing package: https://github.com/jprichardson/goatee-go https://github.com/jprichardson/goatee-go It's too bad that discoverability of modules in Go sucks.
- malandrew 13y agoI'm not a Go developer (...yet), so I was wondering what about the discoverability of it sucks. I ask because I'm working on package management tooling for JavaScript and it's always interesting to see what is done well and poorly in other ecosystems.
- pornel 13y agoIf you're only pushing data realtime to down the client and don't need realtime upload, then consider Server-Sent Events (http://www.w3.org/TR/eventsource/ http://www.w3.org/TR/eventsource/) as an option. SSE is HTTP-compatible, so for example works on mobile networks that force port 80 to go through "transparent" WebSocket-disconnecting HTTP proxy. Additionally you get Flash-free polyfills for IE7+ and automatic reconnection on error built into browsers.