Advancing the web framework ecosystem (Chrome Dev Summit 2019)

[@CyberAcidPlanet]

*Advancing the React ecosystem

[@BennyPowers]

Thing is, React is the only framework that needs help working within the web ecosystem... every other framework Just Works with the platform.

[@BennyPowers]

@intrnl 1) React partisans have told me in the past that their solution to compat issues is to "always use react for everything". I'll leave it up to you whether that's a good move. 2) react is certainly captivating when you look at it in terms of stars, npm downloads, and blog posts, but it's not as popular in real numbers (wrt page loads) as it appears from internet hype

[@abnormi101]

Not much love for Angular at the Dev Summit - but much more love for React. What is the future of Angular? Is Angular "dead"?

[@TomsDone]

No, angular is not dead, but it is quite reasonable for Google to focus the most on the most popular framework. Google is good that way: being very open to competitors products, not pushing their own stuff too much or forcing their devs to just use Google tech.

[@johnnycagebringbackdislike9806]

Dead to me, but keeps taking my productive time at work :/ Seems like "zombie" is a better word.

[@Khaltazar]

I believe Angular died when it went to needing to be compiled and something installed on the servers to run it. At least it died to me when they went that way.

[@AundreL]

​@@Khaltazar you do not need to run anything on the server. angular transpiles your projects into pure js, css and html, that you can simply drop into any cPanel or http server folder. On top of that, it automates polyfills, minification, and has high-security standards. Angulars is just a shining example of providing too much, all these useful features as useful as they are in real-world production, just seem like "bloat" if you have never hit all the problem domains Angular tries to solve.

[@sujitkumarsingh3200]

@@AundreL totally agree with you.

[@Xxp0r]

Excited for Vue 3

[@cyb]

Where’s riot.js?

[@arifulislamleeton]

Frimwark ad International Space🌌 and Rocket🚀

[@AceHardy]

👑

[@ELStalky]

While expansive and integrated frameworks have their productivity benefits, you should think hard about adopting one. If you ever have the need to switch away from it, you will probably have a bad time because everything depends on the framework functions being there. Some frameworks are better than others by decoupling the components more (e.g. you can switch out the UI rendering library). Also, working efficiently with big frameworks often requires a lot of knowledge, so if you add a new person to the project there can be an initial loss of productivity. Also, while React is rather popular and is pushed a lot, i would not recommend it. It, like a few other UI libraries, is flawed by design because it is built on virtual DOM, which does not scale well and leads to performance bottlenecks. Once you hit those bottlenecks you can only make trade-offs in how you degrade the user experience or move away from the library entirely, which can be quite expensive. It seems like React is becoming the new jQuery and i am not looking forward to that...

[@jandaans4790]

Secure Internet (in Safety Cloud(s)).

[@christinapotter3905]

Just for fun

[@RafaelCouto]

web !== react

[@arifulislamleeton]

Introduce myself I'm Arif Khan harry software development and Investors and students United States and development Microsoft and Facebook and KZbin development

[@evacserna2281]

Hi

[@kaihendry]

Why not capitalise Web? There is only one Web.

[@sujitkumarsingh3200]

She kept saying use framework rich in features. Yet, ironically they choose React 😅.

[@EzequielRegaldo]

VanillaJS beats every framework in this world ... just create your component, import, enjoy ... full perfomance, no unnecesary code and the same syntax, do u need routing ? just make router component and import components inside. Simpler, smarter and blazing faster. Do u need app ? create manifest.json with services, cache and custom icons, worth

[@danilobrinu]

This only works for you todo app not for real apps

[@Pesthuf]

I‘ve yet to see a vanilla application that is complex, not spaghetti, performant and not just poorly reinventing existing libraries, except with no documentation, bad perf and cross browser/platform issues. The alternative is writing the same code again and again, which is probably even worse. And one has to love state management that is split over objects and the DOM and gets changed by random event listeners.

[@EzequielRegaldo]

@@Pesthuf don't blame a tool for your bad practices

[@guseynismayylov1945]

Or just use EHTML (github.com/Guseyn/EHTML) :)