This is an old post. Information here may be out-dated, or the post may re­flect opin­ions or be­liefs I no longer share.

I had re­cently posted on Mastodon about want­ing to learn and use Ember.js for a side-pro­ject. The re­sponses were very sim­i­lar at first: folks ask­ing me why I wanted to learn Ember.js when ABC frame­work or li­brary was more pop­u­lar, or better,” which I think is a very loaded and sub­jec­tive term. Or, you know, that Ember.js' mo­ment/​time/​train is long gone.

That's ex­actly the thing for this side-pro­ject — I am not look­ing to get on any train, or use a cool-new-tech. ReactJS and its ecosys­tem — for ex­am­ple — are a main­te­nance headache, whereas what I'm seek­ing is sta­bil­ity and con­ven­tions.

Ember.js, at least on pa­per, of­fers that. It's in­cor­po­rated a lot of ideas for com­mon prob­lems. Consequently, it fits my needs. I don't need to be opin­ion­ated to de­velop in Ember - I can look at the doc­u­men­ta­tion and to its com­mu­nity to fig­ure out what's the best way to solve any and every prob­lem. It does come with its bag­gage, but that's a trade-off I have to un­der­stand and make for my­self.

It's eye-open­ing and a good re­minder that the an­swer to every­thing is not React/Angular. Or client-side JavaScript web apps, as far as that goes. Not to give the Mastodon folks a bad rep, they were very un­der­stand­ing once I ex­plained my rea­sons. 😄

How The Web is Really Built by Lea Verou on CSS-Tricks