Sorry, but you can't compare React and Ember. Yes, just because it's a view library, you have more control on how to manipulate and pass data to your view.
Okay, your view is sorted. If your application has some complexity, what about everything else?
- data modeling
- routing
- network connections
- functional utilities
- build
- styling
- testing
Yes, you can pick and choose all of the above with React. And I used to love myself to spend hours just trying different things and make them all work together. Now, I feel I've grown out of it. Yes, I still love to tinker, but I now care more about teams productivity and shipping quality code and features out of the door, rather than spending hours with the team debating which router to use, or how we should build, test and tie everything together.
I've always worked in small teams. You know what I realised after years of shipping code and running my own business? Neither consumers, or business users care if you use React, Ember, Angular or Vue. They don't care if you use webpack, SASS or jQuery. They don't care if you name your variables CamelCase, underscore_case or dash-case. They don't care if you run on AWS, Heroku, GCE or Hetzner.
They care about what they can see, touch and feel - quality, stability, performance and innovation.
There's nothing really that any single modern front-end JS frameworks can do that others can't. Any popular website you know, done in either of the frameworks, can be done in another.
However, putting a business hat on, I'll choose what will make the team and the business most productive. Again, as a small team, I put my trust that demigods like Yehuda, Tom Dale and all Ember.js contributors have more experience and skill than we do as a small team. I put my trust in Heroku, Apple, LinkedIn, Netflix, Twitch, Groupon, Discource and others. They pay quadruple salaries to their developers and they run their billion worth businesses on Ember. Do I run a billion worth business? No. But I will trust them that Ember's router, build and testing tools together are doing their job to run these huge businesses on, hence it's more than good enough for us. I will trust them, as 99% of developers trust in public key cryptography, encryption algorithms and SSL.
But what about software engineer's curiosity to tinker with technology? I don't believe there's that much left to do on front-end, it became quite boring comparing to advances in the back-end. Yes, you can rewrite your rendering layer to do X instead of Y. It doesn't tickle my fancy at all. I push myself, and my team, to put their curiosity into back-end - operations, Docker, Kubernetes, load balancers, cloud, queueing, messaging, architecture, websockets, real-time, microservices, cloud mesh, circuit breakers, etc. It makes developers smarter, they now think differently when they come up with ideas and design their work. It also progresses their careers.
As a team, and as a business, I believe we should spend time talking about our product, software architecture, as well as our systems, putting everything together, from database, to compute, and storage layers, to cross cloud load balancing and DNS failovers, rather than spend our time deciding which router to use or how to structure folders in our app.
We will focus on shipping quality features instead, to win more customers, to bring more revenue, to work less to achieve the same output and improve everyone's work-life balance. Work hard, but also work smart. I'd rather give my team a day off every other week to spend with their families, than keep reinventing the front-end wheel. It's been done bazillion of times, by bazillion of companies. Just pick what works, and spend your saved time on brainstorming and innovation on how to change the your business, industry and the world.
Hence, I choose Ember.js.
theartofmadeline
blakekathryn
andulkaphoto
vaporwave
kianamaiart