[ianamartin]

I just don't understand how anyone can make a "best" decision these days.

I'm not a frontend person. I'm backend and middleware and infrastructure, although I'm trying to figure out the front end stuff.

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.

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?

[cpplinuxdude]

When I had to learn Python to do my job, I read a few pages on python.org, and one of the things it mentioned was that 'a python developer can do in a month what a C++ developer can do in a year".

Expressive, concise code is always a good thing.

Meteor is excellent for MVPs and POCs; there are a lot of people out there with big ideas, but limited budgets to test out those ideas.

In Meteor, you can access your collections from the client and the server; and the vast number of packages on atmosphere makes writing a webapp in Meteor feel more like assembling lego than anything.

The speed at which we can write software is tightly correlated with our ability to innovate quickly; test things out, keep what works and throw away what doesn't.

I've developed things for clients in Meteor, in a matter of weeks what others have failed to deliver in year

90% or so startups fail, not because your front and backend were too tightly coupled, but because of a whole variety of other reasons. Given that most of that code will end up in the bin anyway, might as well focus on quantity, and switch to something more robust when need be.

[ufmace]

Most of this stuff is really designed around doing Single Page Apps, where most of your business logic is in JS that runs on the frontend, and only the critical security and validation stuff and such is on the server. Generally, the server just slings JSON back and forth to the database and does some validations and such instead of rendering full HTML pages with templates. If it makes sense to build a particular app like this, it can result in a really slick user experience.