![]() ![]() I'd love to chart out relative interest in these frameworks using Google Trends, but it is hard to find specific search terms (i.e. Projects like Meteor seem to be finding an audience, especially among those who are looking for JavaScript front and back ends. ![]() React has gained a small but growing (and seemingly devoted) following. The Angular dominance has not halted the growth of competitive frameworks. It's no longer just about the code I write, but Angular is tied into my entire development experience. The point is, all these integrations not only made the choice of Angular easier, but make leaving harder. IDEs including WebStorm/IntelliJ, Visual Studio, and NetBeans come pre-baked with features specifically for Angular projects. ![]() For example, Angular integration comes pre-built into frameworks such as Telerik's Kendo UI, Ionic,, Wijmo and others. This made the decision to choose Angular easier, especially for larger companies. However, this led to what is probably the more important factor, which is the integration of Angular into other tools and frameworks. No one could realistically keep up with the rate of new frameworks, so it seemed the time was ripe to coalesce around a particular framework, and the fact that it was led by Google probably made it seem like a safer choice. I think multiple factors led to Angular's "dominance" being relatively stable. Angular Interest Over Time According to Google Trends At the time, I thought Angular was just the flavor du jour and that the community would just as quickly move on. I was running a popular site for developers (called Flippin' Awesome, which is now called Modern Web) and it seemed that all any author wanted to write about was Angular. Then, seemingly overnight, things changed and AngularJS appeared to suddenly dominate any framework discussion related to JavaScript. It was beating out more established frameworks like Dojo and keeping upstarts like Knockout and Ember at bay. Just a couple of years ago, it seemed as though Backbone was on its way to becoming the de facto framework for JavaScript developers. This was true even several years ago, before it became de rigueur to have your own framework in order to join the elite, conference-speaker crowd. There are a lot of frameworks in the JavaScript world. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |