Comment by Mev-Rael on "Will my Angular 2 App go LIVE with Angular 2 Prod build after 5-6 months ? or with just some RC builds ?"

Please stop using this cancer of the modern web. Angular 2 is even bigger then 1. 200kb gzip for I dont know what. Business code will be much smaller then framework itself, lol.

medium.freecodecamp.com/angular-2-versus-react-th…

Keep everything simple.

Better learn JS/ES6, latest web standards and APIs itself. You can find many routers, templates, components in less then 2kb which you can really read and understand in few seconds.

If you "don't know what", how can you even elaborate an educated answer? Please bring your deductions and proof to the table, or just keep your React fanboyism out of here.

I provided you a link, I can provide you also links to Quora, Medium and other sources.
Angular is huge, a lot of extra complexity and is overengineering, it is a fact.
I am not a React or any framework fanboy, I know JS itself and some small and poerfull libraries which are much faster and simplier then React+Angular.
You can keep your Angular fanboyism out of here, cheers.
Framework fanboys are very limited to what they can, most developers don't know JS itself very good, Computer science, Software engineering, Web standards, Functional programming, it is also a fact.
My last discussion with Angular fanboy was about simple native form validation, he told me that for that are required ~10 lines of code without any framework.

When you do it right its not huge: blog.mgechev.com/2016/06/26/tree-shaking-angular2…

Yes, it's huge. But it's so because it's a framework who goes to cover a lot of aspects of implementing a modern SPA. In React, how many modules you do have to bring in and make them coexist in order to achieve the same functionalities? Beware, I'm not saying that the Angular's approach it's better that React's. In fact, as everything in life, there's no universal "best way", it all depends what you need to achieve.

I'm sorry if you got offended about the fanboyism stuff, but believe me, you really sounded like one, just trashing a framework with a 5 lines answer and a link. I'm no Angular fanboy either (even if I worked and I am still working with Angular 1 as of now, and only have a theoretical overview of React), and if you read carefully my previous comment you can easily understand that I didn't even mention Angular, so how can I be defending it? ;)

In the end, I absolutely agree on point 5. That's why I see no sense in defending or attacking one particular technology, and again, I'm not defending or trashing anything here.

And, of course, I'm sorry if I misunderstood your answer.

Rollup, indeed, is a next generation ES6 bundler and does a lot of magic. I am using now it everywhere.

You really don't need to put so much code (at least how Angular provides its architecture) for modern SPAs (which is actually a modern buzzword for DHTML, this technic existed for many years) and you don't need SPAs everywhere like everyone's trying today.

Browser is still browser, mobile network is still same sometimes very slow network, HTTP is still the same HTTP, you don't need to do "back-end engineerig client side". JavaScript was made for scripting browser and it is the simpliest language in the world... well untill back-end developers came to frotnend and started overengineering it trying to simulate classes, interfaces and everything else you really don't need in JS.

For MVC there is very lightweight library http://mithril.js.org/ and a lot of simplier alternatives on GitHub and even 20-line routers.

For template engine, which is 2kb and x100 faster then React - I have found this awesome project http://monkberry.js.org/

There is also my own approach, which is still far away from production release, but you can get main idea from the index page - https://bunnyjs.com

Browser always will be a simple static page, where you need to init some of custom components only when needed. You have a datepicker, you included datepicker - a standalone lightweight library without dependencies, you need a search, dropdown, autocompletes, tab switches, form validation, datatables, ajax (or feth API now), whatever else - again you just include a small package for that. That's why jQuery was so popular and still is - simplicity. With ES6 actually there are so many new web APIs that I can do a lot of things in few lines of vanilla JS.

My favorite comment on the medium article I provided - "Abstraction is great but nothing beats vanilla JS."

Main probolem of front-end today - "The Gorilla and banana problem".

I am also sorry for "funboyism" and you are, of course, right, it always depends on what you need to build.

Try Aurelia http://aurelia.io

Search Hashnode