The problem with NET and JSF is not what they "do" client side but what they do server side. They are just too heavy and will never scale. This does not mean that they will not have a market. Hopefully they will so that those who love them will have money and leave us alone. But, for people who can code without tools, they are not a viable solution, in my opinion.
On 4/19/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote: > That's actually a good point... We've all heard about JSF and ASP.Net, how > they handle client-side events server-side, which is a concept I've never > been especially enamored with. But, when you see some actual examples of > this in things like what Google is doing, you start to reconsider that > position a bit. This isn't about richer UIs because, let's be honest > folks, GMail is no great shakes interface-wise. What is cool about it is > the overall performance and efficiency of it, and as Jack says, that is > all about interaction with the server, not what the user sees. > > Another benefit of AJAX that I haven't seen mentioned much is error > handling... Instead of seeing 404s or 500s or cryptic stack dumps or > whatever else the server spews out, the user only sees what the AJAX > developer wants them to see. Error handling no longer results in the > entire flow of a web app breaking down, it can be handled considerably > more gracefully than before, especially now that try...catch is a > supported JS function (it wasn't always as I recall). All this is of > course in the realm of client-server interaction as Jack is talking about, > but in this case it ALSO results in a better user experience. > > -- > Frank W. Zammetti > Founder and Chief Software Architect > Omnytex Technologies > http://www.omnytex.com > > On Tue, April 19, 2005 1:23 pm, Dakota Jack said: > > I have another perspective on this. Rich UIs are good, but what I > > like about AJAX in addition to that somewhat peripheral concern (to > > me) is that it cooperates with the serverside and allows the > > serverside to be more efficient. The relationship between the server > > and the client in AJAX is what is most interesting and is what makes > > it so useful. There is a reason why the sites using AJAX, e.g. > > Google, do so. It is not because they are seeking, necessarily, any > > sort of rich clients. They are seeking robustness and usefulness. > > That is where AJAX is at, I think. All this other talk is fine, but > > it misses the main point of what makes AJAX interesting for Struts. > > The rich client stuff can be a dark hole for serverside discussions. > > AJAX is not. > > > > Jack > > > > On 4/19/05, Vic Cekvenich (netsql) <[EMAIL PROTECTED]> wrote: > >> Michael J. wrote: > >> > >> > > >> > People just should stop thinking in terms of "client-side scripting" > >> > and start thinking > >> > >> .... in terms of "client-side rendering" :-) > >> > >> (XAML, XUL, Flex, JDNC, DHTML(Ajax, JavaScript)). > >> > >> UI naturaly should be done on "client" side, asking for domain and other > >> services from the .... server. > >> > >> The more you do "client-side" the richer the UI. > >> > >> .V > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > > > -- > > "You can lead a horse to water but you cannot make it float on its back." > > ~Dakota Jack~ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- No one ever went blind looking at the bright side of life. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
