undefined | Better HN

0 pointsrekoros10y ago0 comments

We implemented them ourselves, and it took quite a bit of work.

Our magic weapon is Erlang, which is a wonderful language for working with protocols, and a wonderful runtime for working with many things happening at the same time.

The other magic weapons are the Cowboy webserver and the Gun http client -- both written by Loïc Hoguin. Loïc doesn't work for us, but we've been sponsoring him financially for over two years (https://medium.com/@abs/what-we-learned-from-sponsoring-an-o...).

Our frontend doesn't really matter as much, since it's just a dashboard, but we use TypeScript with Flux and React (it's been great).

0 pointsrekoros10y ago0 comments

We implemented them ourselves, and it took quite a bit of work.

Our magic weapon is Erlang, which is a wonderful language for working with protocols, and a wonderful runtime for working with many things happening at the same time.

Our frontend doesn't really matter as much, since it's just a dashboard, but we use TypeScript with Flux and React (it's been great).

0 comments

6 comments · 2 top-level

seivan10y ago· 3 in thread

Care to share your webpack config for getting React and TypeScript to play ball? I'm collecting a bunch to try to figure out what works best.

jlarky201210y ago

That's actually interesting topic :) Right now we use gulp and gulp-typescript. So far, I like approach that is used in https://github.com/Microsoft/TypeScriptSamples/tree/master/e... but I'm not sure if we are going to use it any time soon. As far as gulp config, what we use is pretty much close to gulp-typescript README examples

seivan10y ago

Thanks! Yeah it's hard to find good UP TO DATE reading material on this. I genuinely appreciate this.

scrollaway10y ago

You can take a look at ours: https://github.com/hearthsim/joust

derefr10y ago· 1 in thread

I was just considering advocating within my employer (Cloudant, i.e. clustered-CouchDB-as-a-Service) to back Loïc too. CouchDB is still stuck in the past with Mochiweb, and while switching that out for Cowboy 1.X would be a nice-to-have, getting our hands on a stable release of Cowboy2 (i.e. "the HTTP/2 version") would let us optimize Couch's replication story immensely. I've just been trying to set up a single trivial Event Stream HTTP/2 loop_handler with the Cowboy2 master, and it's really just not there yet, so we could probably give him a push.

rekorosOP10y ago

That would be great - I can put you in touch if you're not already (andrei@sameroom.io).

j / k navigate · click thread line to collapse