| ▲ | robertoandred 7 hours ago | |
Eh, this argument falls apart for many reasons: - His main example of bloated client-side dependencies is moment.js, which has been deprecated for five years in favor of smaller libraries and native APIs, and whose principal functionality (the manipulation and display of the user's date/time) isn't possible on the server anyway. - There's an underlying assumption that server-side code is inherently good, performant, and well crafted. There are footguns in every single language and framework and library ever (he works for WordPress, he should know). - He's right to point out the pain of React memoization, but the Compiler now does this for you and better than you ever could manually - Larger bundle sizes are unfortunate, but they're not the main cause of performance issues. That'd be images and video sizes, especially if poorly optimized, which easily and immediately dwarf bundle downloads; and slow database queries, which affect server-side code just as much as browser-side code. | ||
| ▲ | afavour 5 hours ago | parent | next [-] | |
> There's an underlying assumption that server-side code is inherently good, performant, and well crafted To me it’s an assumption that server side code is going to be running on a server. Which is a known quantity and can be profiled to the nth degree. It’s extremely difficult to profile every possible device your site will run on, which is crucial with low powered mobile devices. > Larger bundle sizes are unfortunate, but they're not the main cause of performance issues. That'd be images and video sizes Not really, no. Large bundle sizes prevent the initialisation of the app, which means the user can’t do anything. By comparison images and videos download asynchronously and get processed on a separate thread. JS bundles also need to be parsed after being downloaded, if you pair a crappy Android phone with an 5G connection the parsing can literally take longer than the download. | ||
| ▲ | youngtaff an hour ago | parent | prev [-] | |
> Larger bundle sizes are unfortunate, but they're not the main cause of performance issues. That'd be images and video sizes, especially if poorly optimized, which easily and immediately dwarf bundle downloads; and slow database queries, which affect server-side code just as much as browser-side code. In network terms JS tends to be downloaded at a higher priority than both images and video so has a larger impact on content appearing JS is also the primary main thread blocker for most apps / pages… profile any NextJS app and you’ll see what a horrendous impact NextJS has on the main thread and the visitor’s experience | ||