News for hackers. Stuff that matters.
Re:Performant Front-End Architecture by nickserv on Tuesday February 11, 2020 @02:43AM (#22296796)
Depends on the target audience. Many customers will be sold on how pretty an app is, sometimes to the point of overlooking missing features. Having a good looking app becomes a competitive advantage, and therefore important to spend time on. Such is life.
Re:Performant Front-End Architecture by pjmlp on Tuesday February 11, 2020 @05:02AM (#22297327)
That can be achievable with designers that actually know their way around HTML and CSS.
Re:Performant Front-End Architecture by otabdeveloper4 on Tuesday February 11, 2020 @03:03AM (#22296876)
Your point is orthogonal, even if true. My point is that SPA frameworks are necessarily buggy and inefficient - after all, their whole point is to reimplement in a bespoke fashion the stuff that the browser already implemented.

Buggy and inefficient stuff sometimes makes sense to a business, this is true.

Re:Performant Front-End Architecture by jiofih on Tuesday February 11, 2020 @03:29AM (#22296975)
That’s a common misunderstanding and absolutely not true. They are abstractions and not reimplementation, and in practice can help achieve way better performance than what would naively come out. React is not a particularly good example of that.

They also solve problems like state synchronization and mutations that the browser has zero facilities for. As mentioned in another comment above, in any medium sized project you’ll have implemented more than half a framework abstracting the DOM already.

Re:Performant Front-End Architecture by SirHound on Tuesday February 11, 2020 @04:56AM (#22297301)
Trying to remember the last bug I encountered in React. I’ll be a while.