5 ms·
That was a very boring article.
by Romanulus 7y ago
That was a very boring article.
- drngdds 7y agoYeah, I don't think we really need a hundred Modern Frontend Bad articles every week
- newfangle 7y agoWe have 3. React, angular, and vue. Angular isnt even recommended anymore so its really only react and vue. I dont think there has been much change in the javascript world in the last few years that hasnt been strictly beneficial. The biggest paradigm shift is probably the widespread use of typing on the frontend with typescript and flow.
- JMTQp8lwXL 7y agoWho is the authority on not recommending Angular? They're still regularly releasing an actively developed framework.
- ng12 7y agohttps://2018.stateofjs.com/front-end-frameworks/overview/ https://2018.stateofjs.com/front-end-frameworks/overview/ is my favorite source. Angular is losing ground every year.
- JMTQp8lwXL 7y agoIt's losing ground in popularity -- that I don't disagree with. However, it is a perfectly acceptable solution for building SPAs. (Saved my personal bias for the end: Do I feel it enables the highest level of productivity for me versus other frameworks? No).
- Ocerge 7y agoWhat do you mean Angular not being recommended? It's pretty damn straight-forward and does the job just fine if a SPA is what you're after.
- tyingq 7y agoJob boards seem to have (a lot) more Angular than Vue work posted: https://medium.com/zerotomastery/tech-trends-showdown-react-vs-angular-vs-vue-61ffaf1d8706 https://medium.com/zerotomastery/tech-trends-showdown-react-...
- newfangle 7y agoI am not suggesting that vue is in more widespread use than angular. People are reading too much into my comment.
- wolco 7y agoJQuery is still popular
- knicholes 7y agoI just built a simple webapp at work and found that most of what I used JQuery for (cross-browser functionality) was already built into the modern browsers. I'm sure if I had to do something more complex or handle more than the handful of event handlers I wrote I'd reach for more than just plain JS, but shrug. It worked for me.
- techdragon 7y agoYou can’t forget about Ember. It’s still going strong. It’s in widespread use and drives some major projects. It’s just not terrible, so people don’t constantly talk about it or rewrite things in it or replace it, generating a churn of blog posts about itself, it’s out there quietly getting stuff done for a lot of people.
- steve_taylor 7y ago> I dont think there has been much change in the javascript world in the last few years that hasnt been strictly beneficial. Take a look at Svelte 3. https://svelte.dev/blog/svelte-3-rethinking-reactivity https://svelte.dev/blog/svelte-3-rethinking-reactivity
- JMTQp8lwXL 7y agoTwo genuine questions. 1. "Svelte is a component framework — like React or Vue — but with an important difference. Traditional frameworks allow you to write declarative state-driven code, but there's a penalty: the browser must do extra work to convert those declarative structures into DOM operations, using techniques like virtual DOM diffing that eat into your frame budget and tax the garbage collector." Is this a practical concern for folks writing CRUD SPAs? I've never experienced degradation in performance due to virtual dom diffing. 2. "Svelte runs at build time, converting your components into highly efficient imperative code that surgically updates the DOM." Angular has its ahead-of-time (AOT) compiler for applications built in production mode. Is this any different from Svelte? It sounds like Svelte claims to be novel, but Angular too does build-time template optimization.
- ng12 7y agoI'd love answers to these questions too. Svelte looks cool from a technology perspective but honestly it's biggest selling point is solving problems I don't have.
- LyndsySimon 7y agoWhat happened to Knockout.js? Just in case, I'm being serious. I'm a mostly backend dev, and haven't spent significant time working on frontend code in several years.
- draw_down 7y ago+1