Wow, there's a ton of jerks here dissing the variety of javascript frameworks here.<p>Look, the web is a fast evolving platform. Similarly, the best way to understand the tradeoffs a framework makes is write your own own! You probably shouldn't use it in production, but it's a good exercise. And writingcode is so easy to do (just code for awhile!) that we're getting a proliferation of it. This is a good thing!<p>I just wrote a carousel widget in jquery. Yeah, I know there are 10million carousel widgets I could have downloaded, but I wanted to understand it better so I made it on my own. (And yeah, I know carousels suck, tell my company's marketers that.)<p>We don't hear complaints when people try building new game engines from scratch. Granted, maybe those aren't posted on HN often?<p>@minionslave, @untog, @sergiotapia, looking at you guys.<p>// edit: And looking at the github page, this isn't really a new framework anyway? It's like... the web-dev equivalent of a review paper. He looked at meteor's stack, and swapped a lot of the component pieces. And that's cool and informative.
As someone who works in JS day in day out, I'm becoming less and less sure the entire ecosystem isn't an elaborate parody.<p>Replacing one monolithic structure with another one because the component parts aren't right? Just skip the monolith part and use the components you want.
I made this. Neat!<p>For those that didnt read more than the title, it's database agnostic. It scales vertically and horizontally. It's not a framework, frameworks are dead. Its just a bunch of packages that fit together like Lego pieces.<p>If you don't need these things (or don't know what they are) don't complicate your life! Get off HN and build something :-)
This is far closer to mainstream JS - with the benefits that offers, eg, wide user base, maintained version of node, etc - while offering the same 'change item in browser, DOM updates, DB replicates, other clients see changes' as Meteor did.
I like the idea of this; it's really what Meteor should be but they'd provide support/hosting/etc.<p>One thing I'm concerned with in general with stacks like this is their use in mobile stuff - even React+React Router+Redux+redux-form adds a fair bit to a payload, even before you start developing an app. As nice as it is to use, for mobile I roll my own.
Is this a parody? It must be right?<p>"Meteor is awesome! But after 3 years, it's starting to show it's age."<p>Edit: Reading more into it, this is just a starter kit and not a replacement for Meteor. You lose everything that made Meteor insanely popular, for what exactly? RethinkDB?
Looks interesting - I only briefly tried Meteor, but it seemed like one of those very tightly-coupled frameworks - everything is all nice and sweet as long as you're using all of the official stuff, but try to switch out something, and you're in a world of pain. Sounds like this is trying to both switch out some of Meteor's choices that haven't aged so well and also make the whole package more modular.
Nice project, but wouldn't call it yet Meteor alternative. It looks more like Meteor 0.x, but done with a few different tools.<p>Still it doesn't solve my main problem with Meteor adoption. Right now if you would like to use Meteor you need to start from scratch using specified database. That limit adoption a lot. I would love if Meteor could be adopted more incrementally by companies (e.g. write collaboration layer to your existing app).
JavaScript people have programming ADHD.
"This system works fine, but we've been using it for too long, let's just rewrite it with the latest greatest"
"Angular, let's rewrite that from scratch"<p>Imagine is Microsoft released a totally new version of C# every year, and stops supporting it.
I just don't understand how anyone can make a "best" decision these days.<p>I'm not a frontend person. I'm backend and middleware and infrastructure, although I'm trying to figure out the front end stuff.<p>Maybe I just don't understand what people are trying to accomplish. In fact, I'm sure of that. I can't for the life of me figure out why you would want to have your front end so tightly coupled to you database.<p>Can someone explain to me in simple terms how and where I would use one of these JS frameworks in the context of a Python or Golang or Ruby/Rails app?