Hacker News new | ask | show | jobs
by metabrew 3799 days ago
Seems like a good analysis of Meteor's shortcomings.

I did some research on related areas a few months ago. My ideal stack at the moment would involve:

* redux or cerebral with immutable model

* react

* css modules

* webpack

* a realtime-enabled version of falcor, which doesn't exist yet.

The last bit is still the missing piece for realtime, as far as i'm aware. Neither GraphQL not Falcor seem to been designed with realtime model updates (via websocket) in mind.

2 comments

Aside from Falcor, this is exactly my current stack and my preferred as well. React + Redux + Webpack + Immutablejs + Bootstrap/Less. I'd be interested to hear your thoughts on Falcor or Relay/GraphQL and see what it can offer. For my backend I run some minimal node webservices. I've recently started making all my stuff "pre-rendered" by statically generating my files (react renderToString -> Mustache -> create a file) , with all my needed data in a json file, and only access the webservices when absolutely needed.
Have you tried Elm? I always found the default mutability of JavaScript to be somewhat hostile to immutable data structures. Elm is very different - but feels very integrated and the functional nature of the language really makes a lot of things simple and easy to debug/test, while being able to still do react-style dom diffing.