Thanks for your help so far. Now that I've had a chance to get my feet wet, start an eval of VW, watch Peter Fisk's progress, etc. I've hit a scary point. To go the distance, my app needs the maturity and capacity of Squeak/Pharo/VW(?). And, near- and long-term, it needs an elegant, cogent, captivating, intelligent, engaging, interactive front end. I've considered doing it in Flash or Silverlight or AIR (fat client) or straight JavaScript - though splitting the tiers and forgetting the backend seems like a lot of deferred pain. I know I have to worry about deployment. I am. I'd rather do it through the browser. And, even though DabbleDB and others are some of the coolest apps ever, I don't see Seaside cutting the front-end mustard (at least the way I understand things at this point). I sure wish there was a lightening-fast, browser-based, morphic-3-supporting VM so I could run ST on both tiers. A sexy, Smalltalk Lively-Kernel. I'm still trying to get Clamato to work. So, in your professional, experienced opinions, can I get a front end on Pharo (either in-image via Rome/Athens or some cooler-than-I've-seen, through-the-browser front end)? With all due respect to the Founding Fathers, I can't do eToys. Should I just do the whole client tier in in JS for the prototype and then hook to Seaside later? Any thoughts would be deeply appreciated. Thanks, Chip -- View this message in context: http://forum.world.st/big-ui-decisions-tp3160359p3160359.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.