Separate Pages Vs Dynamic Content Loading

Many web applications use some kind of dynamic content loading via jQuery or AJAX nowadays instead of just linking to new separate pages, letting the user navigate through the web

Solution 1:

You're probably gonna be shot down, since the question is a discussion more than a specific tech-question, but anyway:

Static vs. dynamic content loading - both have their place. There isn't really anything wrong with using dynamic content loading, as long as you still have a fallback in place in case users doesn't have javascript turned on, create bookmarkable links (so the content can be easily found again), doesn't load too much data (because the load-time for the dynamic content will remove any benefits if the data-load is too heavy).

Static sites are mostly cached, and as long as the content isn't too heavy (again), loading the new page isn't gonna take that much longer. What can be done more easily with dynamic content loading is that you can do preloading in the background, you can create more fancy effects (fade-ins and -outs) easily, and so on.

What you need to do is think about what the page is - is it beneficial to have simple, page-based loading (for instance a webshop or news-site), or is it a simpler site, without the need for several levels deeplinking. If it is the latter, having dynamic content loading might be a better, and quicker, way to go.

Also, there is nothing wrong with using both techniques. Using regular links and pages for main content, and using dynamic content loading for specific content that a user can manipulate. Reloading a table or list of information based on user-interaction within the site, without having to reload, might both be faster and less "jarring" for the user.