I have recently been working with someone on a project that is very ajax intense. All calls are made to web services using ajax and the data logic is handled on the client side. The server side code just acts as the data access layer and does little else. How much javascript is too much?
The code was easier to read, write, and maintain, and the barrier to entry was incredibly low, since it was incredibly easy to include JavaScript code in a website by simply copying and pasting JavaScript code into a web page's HTML file.
Most of what you'll be doing with a JavaScript framework is building web applications. Yes, JavaScript can help make those applications become more interactive, dynamic and exciting, but there are times when JavaScript is overkill and will slow down the performance of the site.
How much does JS bundle size really matter? Simply put, JavaScript bundle size matters a lot. From some of the folks that help steer the ship: Companies with high-traffic applications save millions of dollars by tweaking and optimizing their performance.
It's easier to develop a site if the scripts are separate but usually better to combine them for delivery as long as they aren't going to interact with each other. The reduction of requests will usually make the page load faster.
Javascript may be too much when it reveals too much to the client, so I would look from the security perspective. From the performance perspective in general using Javascript is better.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With