To be honest, same thing is in ASP.NET world. If you enable async postbacks, you suddenly get about 23 javascripts on your web site.
My guess would be that XPages and ASP.NET go by the policy that no matter how many javascript files you have, they will be cached after inital web site load anyway.
I never used XPages for web, but with ASP.NET, it never really got that performance. A site using async postback with all 22 javascript files took about 5 seconds more to load up. In the end, if it is something basic, you are better of writing your own ajax request.
My ruling would be that XPages are fine (much as ASP.NET), but some features are still not useable out of the box. Not for web sites anyway.
To be honest, same thing is in ASP.NET world. If you enable async postbacks, you suddenly get about 23 javascripts on your web site.
My guess would be that XPages and ASP.NET go by the policy that no matter how many javascript files you have, they will be cached after inital web site load anyway.
I never used XPages for web, but with ASP.NET, it never really got that performance. A site using async postback with all 22 javascript files took about 5 seconds more to load up. In the end, if it is something basic, you are better of writing your own ajax request.
My ruling would be that XPages are fine (much as ASP.NET), but some features are still not useable out of the box. Not for web sites anyway.