Ember Blog

Meteor, Ember, Derby were the "next big thing" 10 years ago. Principles of Rich Web Applications (rauchg.com) Nov 4, 2014 https://news.ycombinator.com/item?id=8559519 https://www.infoworld.com/article/2612250/application-development-the-… https://shiggyenterprises.wordpress.com/2013/03/11/picking-a-javascrip… https://blog.emberjs.com/inside-fastboot-the-road-to-server-side-rende… It's not just that the idea has been developed over and over, but it is constantly hyped as a return to the golden past, and yet never gets the love that new client side spa messes end up attracting.

Wow. I really didn't realize it was so close! I've just today finished up what took me away from my Ember project. Ember has been freakin' amazing to use, and Octane really, really, makes it shine. I love ember because it includes everything you need to manage state in your application, install and you're ready to go. I don't have to pick my view renderer, state/history management, storage system, networking stack etc... I also don't have to maintain the dependencies between them, like I would with something built using React. Ember also favors convention over configuration; which, I find to be a godsend when visiting the world of JavaScript. Yeah, it's a bit painful sometimes not knowing the convention, but that's just good ol' fashion learning. I also think the opposite, configuration, is incredibly painful in JavaScript, because the ecosystem moves so fast. The Ember team (and community) also have fixed, and continue to fix, a ton of issues from making module loading easier to better support of Typescript. I'd like to give a few getting started tips for anyone about to jump in (as I did the same a few months ago): * Glimmer templates give you nice HTML-esque looking components while separating the HTML from the JavaScript itself (which I like versus embedding it like JSX does) * Use the decorators. Seriously, they're awesome, they're a MUST if you use typescript. * Ember modifiers are really a big improvement over the previous hooks/lifecycle management. It's just…

It’s a good deal older than that. If you’re talking about something like just React (the view layer), you can certainly go back well beyond 2010. If you’re talking about something more full-featured, like Next.js today, the oldest I can think of is Ember with its FastBoot, which was becoming usable by the end of 2014 and well-established by mid-2015 (even if 1.0 took until mid-2017—and there was a major internal restructuring to how building worked). https://blog.emberjs.com/inside-fastboot-the-road-to-server-side-rende… is good background on that, showing also the attitudes of the time. https://blog.emberjs.com/tag/fastboot/ for the other couple of posts about it.

Here's the fixed link: https://blog.emberjs.com/ember-4-0-released/ - any chance a moderator could fix the original post?

alive and well with huge strides in the framework, better than ever. that said ember gets much less press than it's peers, partly due to not being backed by a major fang corp and historical perception. https://blog.emberjs.com/2019/08/15/octane-release-plan.html