3 ms·
I said more in the other thread, but I'll leave another note in this one. What I think Meteor has the most going for them is the ultimate UX experience for the
by dfischer 11y ago
I said more in the other thread, but I'll leave another note in this one.
What I think Meteor has the most going for them is the ultimate UX experience for the developer. If they really hone in on making it enjoyable, and dare I say fun to work on product... then they've won in my book.
Meteor has given me that feeling thus far, and given the new trends in the community I am sure they are moving in the right direction. I've spoken with the guys there and they are carefully reviewing what the best routes are to take that creates the best experience.
Meteor is not just a vision, it's a real experience you can tap into right now that benefits a very powerful suite of tools to get up and running. We have an enterprise app built with it and it's going great. Yes, it'll bite you in the ass if you don't learn how things work (pub/sub/mergebox/reactivity) but just dive in a little and you'll see it's just a library composed of other libraries that are well documented and easy to learn. It's all really quite simple really. The beauty and evil word "magic", is how they all play well with each other.
React is probably a better choice than Blaze at this point, even for the pure fact that it allows Meteor to not worry about the view and focus on the overall UX experience of the developer above all else.
- tonyonodi 11y agoI couldn't agree more, it's a god send not to have to wade through documentation and work around a hundred errors while you set everything up; before you've written any code. The freedom to iterate on new ideas quickly that a NoSQL database gives you is rather nice too (even if that's a terrible reason to choose a performance-critical part of your stack). I'm sure all this magic comes with a penalty further down the line so I'll let you know whether it was worth it when I get there...