17 ms·
Guide to JavaScript Frameworks
- madmaniak 9y agoIt's lacking the best - Imba. The rest are just funny toys. Sad it's lacking documentation. Hope it will change soon because it kills with performance and developer experience.
- naiyt 9y agoThis is the first I've heard of it. What, in your opinion, makes it so much better from a developer experience perspective?
- madmaniak 9y agoIt has a syntax dedicated to DOM operations. Doesn't change principles from React perspective - it's component based. So what I do for example: I can copy and paste react code, quickly parse it to Imba notation, and the result is 58 of original 198 lines of code. It's clear and nice to read. And outperforms React tens times. How could I not love it? :)
- burlesona 9y agoHmm, “lacking documentation” and “great developer experience” seem mutually exclusive to me.
- madmaniak 9y agoSome people read documentation, some tests (lol) to know what's going on. I read code - and Imba has really nice code to read. Also they are responsive on Gitter. But as I said. It's a pity.
- deleted 9y ago[deleted]
- paul7986 9y agoDid you learn Jan2018.js yet? If not your behind and your skills are outdated.....
- ourmandave 9y agoWhat? You're still using a JS framework in 2018? If you haven't already switched to WASM you're about as fullstack as one pancake.
- Klathmon 9y agoI know people love to shit on JS for being blisteringly fast, but does it really apply here? All 3 of "the big 3" are over 4 years old, making all of them older than windows 10... And of the notable category: Aurelia: around 2014 Elm: around 2013 Inferno: around 2015 Polymer: 2014 Preact: 2016 ReasonML: 2016 Svelte: late 2016 So most a few years old. Yes, it's faster than older technology stacks, because the web is still evolving quite quickly, but it's not as blisteringly fast as many make it out to be.
- dandersh 9y agoYea I'd say the big churn appears to be around tooling and paradigm thinking (state management, functional programming, etc.), the latter of which driven in part by the rapid expansion of the language itself.
- ourmandave 9y agoIt's not the frameworks, it's the build tool daisy chain with it's countless dependencies.
- expertentipp 9y agoThey appear and disappear as fast as startups and projects which use them:)
- Klathmon 9y agoDo you have any information or statistics or studies to add, or did you just want to post your quippy oneliner?
- davedx 9y agoRead with interest to see what it said about Vue: better performance than React and Angular. Is this true? Any real world benchmarks to back it up?
- ricardobeat 9y agoLinked at the top of the article: https://rawgit.com/krausest/js-framework-benchmark/master/webdriver-ts-results/table.html https://rawgit.com/krausest/js-framework-benchmark/master/we...
- keithnz 9y agohttps://vuejs.org/v2/guide/comparison.html https://vuejs.org/v2/guide/comparison.html that was a collaboration between react and vue guys...
- ebbv 9y agoOne non-trivial thing my team has experienced using Angular over the past year; the decision to abandon version numbers makes searching for answers or documentation a nightmare. Ironically the company that should understand search the best hobbled the ability for developers to search for answers. TypeScript is nice. Actually writing code in angular is a fine experience. It’s all the stuff around that which isn’t great. We recently upgraded our app from Angular 4 to 5 without much fuss and that was nice. But the team should really go back to using version numbers. They exist for good reason.
- patientplatypus 9y agoReasons why Vue will rock your socks off - Don't need to know jsx! - Sane way of scripting puts the script in an object and each component is <template>html</template> <script>javascript</script> <style>css</style> - Event buses allow sharing of variables between child components without either redux or pushing variables down one child at a time (finally!) - v-for looping is saner than reacts mapping - v-if allows v-if statements without renderIf component or multiple render statements in react (antipatterns boo!). - two way data binding with vue-model - native vuex with an index file that holds state sanely, rather than just having state held in each reducer as done in react - Great documentation! - Yay !
- jmschlmrs 9y agoThis sounds very much like Angular 1.
- kowdermeister 9y ago"Some of Vue’s syntax will look very similar to AngularJS (e.g. v-if vs ng-if). This is because there were a lot of things that AngularJS got right and these were an inspiration for Vue very early in its development" https://vuejs.org/v2/guide/comparison.html https://vuejs.org/v2/guide/comparison.html
- jmschlmrs 9y agoSo is it fair to say that Vue is for people that wish Angular had stayed on the V1 path and not diverged to be more like React for V2 onward?
- lobo_tuerto 9y agoNo, I think it would be fairer to say that it's like if AngularJS and React had a child and named it "Vue.js". Because in the end, Vue.js has stuff in common with React, like the virtual DOM (you don't see this in Angular 2+) and has stuff in common with AngularJS (the good parts). Check this out: https://vuejs.org/v2/guide/comparison.html https://vuejs.org/v2/guide/comparison.html Don't go thinking you are going to read a biased comparison, the Vue.js vs React section has the blessing from a core React contributor (Dan Abramov): https://github.com/vuejs/vuejs.org/issues/364#issuecomment-244575740 https://github.com/vuejs/vuejs.org/issues/364#issuecomment-2...
- JepZ 9y ago> Vue.js: Current job market is less than that for React and Angular Sounds more like a pro to me as it is the up-coming alternative.
- marsRoverDev 9y agoThis is good for Vue
- jcloud_dev 9y agoI wonder if Cambrian explosion of JS frameworks stops, will there be a small number of "one-size-fits-all", widely used solutions?
- GoToRO 9y agoSEO friendly? Server-side rendering support?
- chuckdries 9y agoVue and react have SSR frameworks, as I'm sure many others do as well. I'm not sure if it's a big enough feature to include in the tags this site uses. ¯\_(ツ)_/¯
- http-teapot 9y agoFor React, could you link a few? I am genuinely interested
- chuckdries 9y agoI don't actually use any of this, so I'm not intimately familiar, but I found a promising looking framework and a help article on redux itself. https://github.com/zeit/next.js/ https://github.com/zeit/next.js/ https://redux.js.org/docs/recipes/ServerRendering.html https://redux.js.org/docs/recipes/ServerRendering.html
- deleted 9y ago[deleted]
- mahmud 9y agoVue is SEO friendly and has native support for SSR. Use Nuxt to get started. https://nuxtjs.org/ https://nuxtjs.org/
- expertentipp 9y ago> SEO friendly? Server-side rendering support? No no no, you think wrong - like an unhirable dinosaur. Sometimes I just chuckle when I see yet another SEO growth-hacking startup doing full client-side rendering in React/Angular.
- kapauldo 9y agoThey should add the licensing risks around react.
- gatkinso 9y agoChoo is pretty underrated IMO. Very small and fast, vanilla js, real DOM node diff, simple state management and routes built in. Also a very supportive community, esp Yosh.
- owlfarm 9y agodomvm is the most underrated in this list. one of the fastest and smallest out there that's dependency free. https://github.com/leeoniya/domvm https://github.com/leeoniya/domvm
- jim_combinator 9y agoI concur! I've been going knee deep in experimenting with this over the weekend. I like the ala carte approach if that's the right way to describe it.
- LeoNatan25 9y agoThe Ultimate Guide to JavaScript Frameworks: Use pure HTML, CSS and JS.
- debaserab2 9y agoWhat is pure HTML and when does it become impure?
- LeoNatan25 9y agoWhen you build a browser insider a browser (aka React), it’s impure.
- debaserab2 9y agoSo JavaScript dom manipulations are pure? but one specific technique of dom manipulations are not?
- LeoNatan25 9y agoIt's not specifically the DOM modification but the way those frameworks are designed. With React you have hundreds of dependencies, which have hundreds of dependencies. You lost me right there.
- debaserab2 9y agoReact has zero dependencies to use it, actually. https://github.com/facebook/react/blob/master/package.json https://github.com/facebook/react/blob/master/package.json
- RobertRoberts 9y agoCan you use react without Node or NPM or a compiler/transpiler or build tool?
- netcraft 9y agoWhats the right choice for building a repacement for an existing app that has survived for 15 years and you want the replacement to last at least another 10? Whats the long term hedge?
- ggregoire 9y agoIf you think Facebook will still be there in 10 years, then you can safely pick React.
- amclennon 9y ago> If you think Facebook will still be there in 10 years, then you can safely pick React. At the same time, you could've made that same argument at some point with Google and AngularJS, Dart, Polymer, etc. Not necessarily a safe bet.
- netcraft 9y agoI completely agree re: sponsoring company - although react seems to be orders of magnitude more popular, so someone is going to have to be supporting these apps that people are creating now you'd expect, right?
- HatchedLake721 9y agoThat’s what Ember was made exactly for. Stability without stagnation. LTS versions. Strict semver.
- rk06 9y agoFuture is uncertain, next 10 years is same as next 50 years in js land. There is not hard and fast rule. That being said, Between rolling-your-own vs Angular/React/Vue. I recommend Angular/React/Vue.
- amildie 9y agoMore like 'The Ultimate Vue Shill Article'.
- JohnMunsch 9y ago"Polymer is a Google-backed libary focused on Web Components, a proposed group of technologies that are currently not well-supported in browsers." Ha ha ha ha ha ha ha. Wow.
- Fifer82 9y agoI gave up on Polymer. I can't really explain it well but nothing worked as you expected it to. v2 was just hacked v1 (hybrid?) and so trying to actually figure out how to use v2 was impossible since every major custom element was hybrid. The documentation was bad, and the things you might want to use were somewhat depreciated, but you had to figure that out on your own. Then the standard glacial pace of development means that v3 was announced over half a year ago and as far as I can see, nothing has happened.
- joaodlf 9y agoI come from a pure HTML + CSS + JS (mostly via jQuery) background. My career has headed in a direction that focusses a lot less in the frontend web, but every 2 months or so I read one of these guides and I get giddy - "Finally, I will teach myself angular/vue/react/backbone/knockout". After about 10 minutes I am filled with dread. I expect to learn about a specific piece of software, instead, I am greeted with requirements of previous knowledge on a whole bouquet of other technologies: node, webpack, babel, grunt... It's just discouraging. This whole thing feels like a farce. I watch colleagues investing time in this and I feel sorry for them.
- naiyt 9y agoI'd recommend trying out create-react-app if you want to learn React without having to worry about all the build tooling craziness. Eventually you'll have to start fighting with those if you build some real life stuff, but create-react-app is great for just getting up and running so you can learn the actual library (the fun stuff) first.
- B4TMAN 9y agoI am in the same boat. I tried learning js. I have a background in CS so its primitive part don't bother me much. Its just that after those primitive parts to see something in action I will need to go through such a steep learning curve that I end of abandoning the whole process. I only know basic js syntax so that I can do thing that I was able to do in C?/C++/Java. How do I make it more useful? I didn't learn this extra language just do the things which I could already do in other languages.
- ricardobeat 9y agoForget about Babel / Webpack. Pick one of the simple ones that can be used without a build process: choo, Hyperapp, Preact. Read the source. The change in paradigm is the main takeaway.
- dclowd9901 9y agoIt discourages us full time FEs too. Webpack and a full transpile pipeline is still relatively new to JavaScript but it seems like we’re starting to land on some assumptions (and thus making this a more turnkey process) ES6 Route based lazy loading Some sort of typing (TypeScript or FlowType) CSSModules React with JSX Redux The reason it’s been so difficult is because we’ve had a sort of Wild West mentality where we want to throw everything at the wall and see what sticks. Hence the extreme configurability of Webpack. But this seems to be the preferred configuration. I speculate we’ll see a more turnkey build pipeline in the next year rise.
- dandersh 9y agoWow, Dojo is still alive and kicking! I'm going to have to find some time to take it for a spin. I really like the idea of framework that looks to address a few needs, making framework selection easier and less reliant on "Oh Framework X is popular now? Let's use that and hire a bunch of devs for it..." While Dojo is there, I'm surprised ExtJS is not. I haven't worked with it directly for quite a few years but I know it is still being supported. I seem to recall some backlash around licensing issues so maybe that's caused a dip in market/mindshare? I liked Elm when I played with it, especially the similarities with Haskell. Unfortunately they had moved away from some of the Haskell like syntax shortly after I started with it, and I didn't feel like I fully understood how to use JSON properly. Kind of surprised to not see Meteor on there. Haven't used it for awhile, and iirc there were concerns around security, deployment, MongoDB lock in (which I thought they were moving away from?) at the time. For smaller, personal use projects I felt I got moving quicker and easier with Meteor than anything else. I'd love to see something like this for libraries and tooling. Really feels like a lot of worthy choices, and therefore a lot of high-level knowledge needed to understand which to choose and when.
- rmrfrmrf 9y agoDojo is literally Satan. Stay far away!
- 3pt14159 9y agoThe rumours of Ember's demise are greatly exaggerated. I have yet to hear of people making the same amount in any other framework. Seniors are making $200k to $500k in remote positions (the people I know live in Toronto, but they could be anywhere). It is hard to learn, and I'm far from an expert, but the highest I've heard another JS developer who knew both Angular and React completely and he was responsible for migrating a company from one to the other and he was just starting to get into that range. Large SPA JS applications are easier to structure in Ember because there are so many best practices. The problem with Ember is the learning curve because it doesn't usually let you take shortcuts.
- adjkant 9y agoI'd point out that often rare and often unused skills get higher pay due to simple supply and demand. I've heard similar salary ranges for Assembly programmers for example. Angular and React are widely used, and there are many people out there that know them. No need to pay a ton. > The problem with Ember is the learning curve because it doesn't usually let you take shortcuts. I'm guessing that's precisely one of the main why it's not used widely. Why train an entire dev team on it only to have half leave in a year and have to be constantly retraining on a language with a large learning curve?
- HatchedLake721 9y agoIt’s not a language, it’s a framework. You can take any experienced JS developer and make them proficient in either Ember or any framework mentioned in the article within days. People overexaggerate how difficult each framework is. They’re all front end frameworks made to do one job. Yes, each of them have their own nuances, but nothing that cannot be understood spending few days coding, reading docs and speaking with someone experienced in this particular framework.
- tbranyen 9y agoCompletely untrue. I was at Bocoup and we wanted to standardize on Ember. It took weeks to get devs doing the basics in a large app. Ember isn't gone because its misunderstood. Its gone because we can build the same apps using more suitable libs/frameworks, in a fraction of the time, with less code, less magic, and less upgrade burden. Ember sucked at upgrades, even though they tried to make it better.
- yesimahuman 9y agoShameless plug, but I think Stencil should be on this list: https://github.com/ionic-team/stencil https://github.com/ionic-team/stencil It's going to be running behind all Ionic apps in the near future, that's hundreds of thousands of apps in the app stores and the web. Also, SkateJS is missing. Both Stencil and Skate are Web Component libraries, "frameworks" insofar as React is a framework.
- Tehnix 9y agoStarting from fresh, I would honestly recommend PureScript or Elm (and eventually Haskell/GHCJS when that moves to WASM). The benefit you get from the amazing type systems and compilers these have, is worth so much when it comes to refactoring, and later on boarding new people, giving them the confidence to make changes thanks to the help of the compilers.
- ggregoire 9y agoIf you want type-checking, going with React + Flow/Typescript is a wiser decision than choosing Elm. Better support, better ecosystem, much bigger community by a huge difference.
- ZenoArrow 9y agoPurely from an outsider perspective, it's interesting to see all the different frameworks out there, but for front end devs I can't help but feel that this type of comprehensive list hinders more than it helps. One key thing JS needs less of is fragmentation. If I were in the front end dev community I'd want to see people making the front runners more mature and flexible, not endlessly fragmenting just because they slightly disagree with what a more established framework does. Looking through a number of the entries in this list you read that it was "inspired by React". Why not just make React more flexible so that your alternative way of handling code fits within it? Does each of these new approaches really require a whole new framework? Contrast this with something like the .NET Framework (which is something I'm more familiar with). Whilst the CLR has the potential to run frameworks other than the .NET Framework, you don't see the same churn in frameworks that you see with JS. I'd suggest this is due to a mixture of two things: 1. A greater focus on getting things done over code elegance. 2. The more mature a framework becomes, the more work is required to match its feature set. On this second point, if JS continues its constant framework churn, it'll be stuck with immature frameworks. I'd suggest that JS devs should be doing what they can to get past this stage, and if that means (for a few years) treating new frameworks as interesting experiments rather than the next big thing, then that may be a cost worth paying.
- RobertRoberts 9y agoI actually think fragmentation is ideal, it demonstrates the failures in a system more cleanly. For example, I started with Protoype.js many years ago, after a bunch of research at the time. But then later switched to jQuery, because it was simply better in every way. There simply was no fixing the problems with Prototype.js, they were inherent in the system. I think when a fragmentation occurs in every framework, its for the same reason. Consider Angular 1 to Angular 2, they broke backwards compatibility because they had too. Angular 2 could have been called something else, and it would be viewed as "fragmentation" not an "upgrade", but in effect, it was fragmentation. This is the exact reason why I think all of these frameworks will ultimatly end up in the dustbin of history. Does any major programming language in the last 30 years use a framework that requires multiple build systems, multiple "dialects" of differing syntax just to do what is inherently available already? (but just faster and easier?) This sounds like the end result is Webassembly, not the "perfect framework".
- phillipcarter 9y ago> What is less apparent is that Vue has had roughly double the growth rate over the past year compared to Angular. Given that you cannot see its growth over the past year in in the chart this guide shows, some might say it's "not apparent at all".
- djsumdog 9y agoIt doesn't mention http://vanilla-js.com/ http://vanilla-js.com/ :-P I know it's just a joke, but maybe there should be a section about not using frameworks at all? I'm also curious about the weight of these frameworks. Once you minify and treeshake everything, what's the minimum you can get down to in order to deliver an app? Also, do any of these frameworks have a way to degrade for people without Javascript enabled? From what I understand, the only way to do this seems to involve some server-side rendering (and it looks like JS is still required). I'm also really curious how heavy React/Vue/etc are compared to the original gmail implementation back in 2004 (only of the oldest major javascript/ajax applications that minimized page refreshes).
- dsego 9y agoSince when does a small library or even a single function count as a framework? Shouldn't a framework provide some sort of structure and I just plug in my app-specific code?
- tgafpc 9y ago"JavaScript Framework" = "I really don't know how to write software." Don't hate me, but it's true.
- electrotype 9y agoI'm still using Jquery and some of the millions js libraries available only when you do not bind yourself to a SPA framework taking control of the DOM. And it work pretty well I must say! My opinion is that for 80% of the websites out there, a SPA framework is not only overkill, but is also a bad choice. Your website is probably not Gmail or Facebook. Server side rendering is perfectly fine. We should start a competition where any framework/no-framework could be used to develop a project and judge the winners using metrics such as : time it took to develop it, compatibility, accessibility, fun to interact with.
- expertentipp 9y agoWeb 1.0 (html and hyperlinks) is still valid and working perfectly. Web 2.0 (AJAX and DHTML) is still valid and working perfectly. Web 3.0 ([MVC][MVC][MVC][MVC]) is basically a fully client side application. It takes a professional to identify which solution will be the most optimal given the requirements. ...and yeah - most likely you don't need React+Rxjs+Redux for a wizard-like prev/next multi-select online-quiz, but it's me looking for a job so you're right. Hell - let's throw in async/await as well. You'll need a space shuttle to debug this thing.
- RobertRoberts 9y agoNope, I think regular people are completely able to judge. Which do you prefer, Youtube from a couple years ago, where every page was a page? Or now, where every page is 15 weird loads of something with blank blocks and comments taking a minute or more to display? Regular users' opinions should matter more than a developers, as they are the ones who use it.
- expertentipp 9y agoIn case of youtube the clients are copyright owners and advertisers, not users/viewers. Apparently for the former two this is the perfect experience.
- tw1010 9y agoYes, it's a lot. But imagine the opposite. Imagine nothing new came out, and everything just stagnated. Evolution, experimentation, testing things out, this is a good thing.
- watty 9y agoWhat are the "clear best practices" for Angular? I'm just starting in Angular 5 and I'm starting down the ngrx path. From what I can tell there's many different ways to structure the project and ngrx is in version hell - the current docs on master reflect an unreleased version.
- bcit-cst 9y agoHonest Question. What is breakdown of market share angular versions market share? does anyone have these stats? I know not a lot of new projects are being done in angular 1 but I am under the impression that majority of jobs are still for angular 1.
- andrew_wc_brown 9y agoCome on. Where the heck is Mithril.
- ralmidani 9y agoI am trying to transition from Ember to React, but calling Ember "historically significant" is odd given adoption by big name companies (including Apple and LinkedIn) and very active development (3.0 should be out in a few weeks).
- szines 9y agoYou are totally right... Ember is adopted and actively used by more and more places, people loves it and very easy to work with. Ember evolve a lot all the time, definitely one of the best choice nowadays.
- azangru 9y agoHow did ReasonML (a dialect of a language), or Elm (a language) end up in the list of JavaScript frameworks? Whereas ClojureScript (a language) or Purescript (a language) didn't make it, but libraries/frameworks built on Purescript did. It doesn't make sense :-/
- mstijak 9y agoAuthor of CxJS here, which is also missing from the list. Please consider CxJS if you're looking for an enterprise-grade framework with ready to use form elements, form validation, advanced grid (data-table) control, navigational elements, tooltips, overlays, charts, routing, context-sensitive layouts, theming, drag & drop, culture dependent formatting and more. https://cxjs.io https://cxjs.io https://github.com/codaxy/cxjs https://github.com/codaxy/cxjs
- bricss 9y agoMithril is a good one
- pdfernhout 9y agoI second Mithril as a great choice. Two things I wrote in it: https://narrafirma.com/try-narrafirma/ https://narrafirma.com/try-narrafirma/ https://github.com/pdfernhout/Twirlip7 https://github.com/pdfernhout/Twirlip7 Combining Mithril ( https://mithril.js.org/ https://mithril.js.org/ ) with Tachyons ( http://tachyons.io/ http://tachyons.io/) or a similar CSS approach is also a great option to avoid having to write that much CSS. That way almost all your code can be in one language and easy to refactor -- especially if you use TypeScript.
- tomkinson 9y agoI'd like to see pro and cons for all the lower 'smaller' frameworks and methods. Maybe we can contribute? I have used many of them. Seems like the ones with pros and cons, React, Vue, Angular etc everyone already knows. I think there is opportunity here to give more depth to lesser known frameworks. The top 5 are pretty well discussed at this point.
- ausjke 9y agoto me the war is already over, for new projects, just start with react, react-ecosystem probably will become the dominant framework from 2018 on.
- CryoLogic 9y agoEmber isn't anywhere close to dead. LinkedIn, Apple, Microsoft Store, DigitalOcean, Twitch.tv... Still actively developing on Ember.js. Version 3.0 is coming soon. Unlike React/Vue EmberJS has LTS support releases as well which is less risky for corporations.
- keithnz 9y agoI like that the only con for Vue is there's no jobs for it. Having done two major projects in React and Vue, Vue is my preference. While vue is supposedly faster, speed has never been an issue for either. I think the biggest thing for me is it's just easy. While I like React, I think vue is nicer and often more concise, and if you really want jsx, it also supports that. I also use Bulma for the visual side which works nicely with vue.
- swyx 9y agoi mean its also because the author is obviously biased toward vue. see the other comments here for why people actively pick react over vue. dont confuse the printed word for fact.
- keithnz 9y agoalso don't be confused that even when biased it doesn't change the facts. I built major things with both react and vue, I like both, but I like vue more.
- tenaciousDaniel 9y agoToday I was playing around with a webpage, and realized it was the first time I had directly touched the dom in like a year and a half. It was so simple and joyful. I miss it.
- arvinsim 9y agoWhat do you think is the long term prospects of frontend development? I have come to terms with continuous learning in frontend but I can't help but feel that I am standing on unstable ground. That one day, all the knowledge that I have accumulated would become irrelevant. I have come to the point that I am learning backend using Python just to have a fallback.
- lmiller1990 9y agoNot really sure I get the constant Vue v React debate. They both do basically the same thing and each support almost all the concepts the other does. Both are great, neither is significantly better (after about a year full time with both in various projects).
- wetpaws 9y agoHere is a guide: All of them suck (with the exception of react which is not actually a framework). Wait for 10 more years.
- pdm55 9y agohttps://jrsinclair.com/articles/2018/react-redux-javascript-architecture/ https://jrsinclair.com/articles/2018/react-redux-javascript-...
- pdm55 9y agoThat link was recommended to me as a simple, clear explanation of React. I'm a real minimalist - just plain vanilla Javascript serves my purposes - but I'm glad I read parts of that explanation, as I got familiarity with the term "render" and could see that React is the go-to framework for mobile.
- mhale 9y agoEmber is the PostgreSQL of JavaScript frameworks. Similar to the way Postgres has deep roots that trace back to Ingres[1] in the days before SQL was a solidly established standard, Ember traces it roots back to SproutCore[2] in the JS framework pre-historic era of 2010. And the same way PostgreSQL was seen as a second-tier or only "historically significant" open source database, the PostgreSQL team just kept at it, toiling away year after year, steading churning out awesome code and excellent documentation, getting better and better with each release. Like clockwork. In the same way PostgreSQL is now, finally, enjoying more popularity and getting the recognition (long overdue in my opinion) for the awesome platform that it is, I expect that in time more developers will come around to appreciating Ember. The Ember leadership is definitely approaching the project and the processes around it like they intend to be not just relevant but pushing the boundaries for a long time to come. For one example this boundary pushing, you should not miss @tomdale's talk at ReactConf about GlimmerJS (the view layer extracted from EmberJS). It is, in my humble opinion, simultaneously mind-blowing and and inspiring.[3] [1] https://www.postgresql.org/about/history/ https://www.postgresql.org/about/history/ [2] http://yehudakatz.com/2011/12/12/amber-js-formerly-sproutcore-2-0-is-now-ember-js/ http://yehudakatz.com/2011/12/12/amber-js-formerly-sproutcor... [3] https://www.youtube.com/watch?v=nXCSloXZ-wc https://www.youtube.com/watch?v=nXCSloXZ-wc