The work for performance on the web feels endlessly lost because of the framework-ization, 3rd party integration, application-ization of the front end.
Nevertheless, here are some tips from me:
With service worker, the rarely changed resources could go offline, Even without the not- modified http call,
I rarely see someone use progressive PNG (Even I haven't used them a lot).
Well I somewhat disagree, frameworks like React have all these optimisations baked into the core
Of course a framework will never be as fast as vanilla is, but the trade-off is it wouldn't be feasible to create a lot of modern web apps without a framework
While you have few dependencies, the optimizations will/may work. I agree - there are tons of advantages about using a framework, beyond speed. If we still code long enough, will may see performance with the help of - for example - WebAssembly embedded in the cores of frameworks - that is unthinkable done vanilla.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The work for performance on the web feels endlessly lost because of the framework-ization, 3rd party integration, application-ization of the front end.
Nevertheless, here are some tips from me:
Well I somewhat disagree, frameworks like React have all these optimisations baked into the core
Of course a framework will never be as fast as vanilla is, but the trade-off is it wouldn't be feasible to create a lot of modern web apps without a framework
While you have few dependencies, the optimizations will/may work. I agree - there are tons of advantages about using a framework, beyond speed. If we still code long enough, will may see performance with the help of - for example - WebAssembly embedded in the cores of frameworks - that is unthinkable done vanilla.