I really don't like the over-dependence on JavaScript with XPages. The beauty of the best JS frameworks is their un-obtrusive design, so if JS is not supported on the user's browser then the site is still usable, albeit with more limited functionality. You just don't get that with xpages.
For example, disable JavaScript and all links in an xpages view will break. Even with JS enabled in Firefox, if you click on a link with the scroll wheel to open in a new tab (something I do all the time to increase productivity - opening numerous documents at the same time saves waiting for the page to load each time) you don't get the document you were hoping for, just the view again in a new tab. Not very helpful at all (try it out on the new OpenNTF catalogue).
There is a lot of talk about traditional domino development and how it is not possible to do the stuff XPages can do. That's just not true. Domino in its traditional form is so flexible that if you just use a framework like JQuery with it you can create equally stylish, web 2.0 style web apps. Those who say otherwise are probably stuck in their ways doing things the same way as 10 years ago, and so are more likely to be blown away by XPages. It may not be as drag-and-drop quick to create the app, but so long as you know your stuff it doesn't take a great deal longer.
Like Jake, I am concerned by accessibility as most things I do in Domino are client facing, so must meet accessibility guidelines. I see the lack of functionality without JavaScript enabled to be a big problem in this sense.
I have played with XPages, and undoubtedly some things are cool; most notably the repeat container, and I may use them for internal apps that can be knocked together quickly to serve a limited purpose, but large-scale customer facing apps? No, I just don't believe that they're ready for that yet.
I really don't like the over-dependence on JavaScript with XPages. The beauty of the best JS frameworks is their un-obtrusive design, so if JS is not supported on the user's browser then the site is still usable, albeit with more limited functionality. You just don't get that with xpages.
For example, disable JavaScript and all links in an xpages view will break. Even with JS enabled in Firefox, if you click on a link with the scroll wheel to open in a new tab (something I do all the time to increase productivity - opening numerous documents at the same time saves waiting for the page to load each time) you don't get the document you were hoping for, just the view again in a new tab. Not very helpful at all (try it out on the new OpenNTF catalogue).
There is a lot of talk about traditional domino development and how it is not possible to do the stuff XPages can do. That's just not true. Domino in its traditional form is so flexible that if you just use a framework like JQuery with it you can create equally stylish, web 2.0 style web apps. Those who say otherwise are probably stuck in their ways doing things the same way as 10 years ago, and so are more likely to be blown away by XPages. It may not be as drag-and-drop quick to create the app, but so long as you know your stuff it doesn't take a great deal longer.
Like Jake, I am concerned by accessibility as most things I do in Domino are client facing, so must meet accessibility guidelines. I see the lack of functionality without JavaScript enabled to be a big problem in this sense.
I have played with XPages, and undoubtedly some things are cool; most notably the repeat container, and I may use them for internal apps that can be knocked together quickly to serve a limited purpose, but large-scale customer facing apps? No, I just don't believe that they're ready for that yet.