sente

Hello HN, This is a tiny little thing that me and a frequent collaborator [0] wanted to express in these challenging times. What if people miss something as awkward and forgettable as elevator small talk? Right now, there are virtual places where we can meet, collaborate, do yoga, talk about books, watch content together, and rave. This virtual space gives you an analog that is a little more from the daily inbetween times. After long days of video calls at work, we ended up doing more video calls each evening to get this wrapped up. Overall this small concept took four weeks to finish. In the process I primarily learned that there have been notches in screens for a few years now. The whole thing is built with Clojure and ClojureScript. And largely leveraged Sente [1], a wonderful front+back end WebSocket story. The characters are customiz

The most novel use of transit is in the Sente [1] library for clojure/script. It is an abstraction over long-polling / websockets that lets us treat it as a core.async channel (which is like a go-block in Go). It's worked awesome for updates, and using Transit to keep the transmissions minimal has let us focus on the API for a realtime system. [1] - https://github.com/ptaoussanis/sente#sente-channel-sockets-f...

Sente is a good library that allows you to do something like this: https://github.com/ptaoussanis/sente You would have to do the database code yourself, however.

I have not worked at the scale discussed by Joseph Wilk, but I am pleased so far with my ability to build out micro-services with Clojure. The eco-system around Clojure seems to get stronger every day. I'll mention a few of the libraries that I'm using. For building out a RESTful API, I found Liberator to be very clever and original: http://clojure-liberator.github.io/liberator/ For handling internal queues, I use Lamina: https://github.com/ztellman/lamina For instance, when saving something to the database, I usually put the data in a closure, put the closure in a Lamina "channel" and let some workers execute the closure when the thread-pool and IO constraints allow. I just started experimenting with the Ribol conditional restart system, for error handling: http://docs.caudate.me/ribol/ For the integration of frontend with backend (Mongo

An Om question: what do you store in the app state and what do you store in component local state? In my own application, I started off storing everything in app state, using local state only for short-lived transient data, but over time I found that having a bunch of information like what tab is currently visible in the app state became difficult to manage and made the app state a nightmare. So now I like to keep a strict separation: app state is basically my model - the data being processed (if I were writing a text editor, its the document being edited) and local state is everything else: which dialog is open, which tab is selected, button toggle state, mouse state etc (in a text editor, whether bold is selected, whether I'm in print preview mode or edit mode, etc). Basically app state is what is being processed and local state is how