Mariano Martinez Peck wrote:
Because of all the things I already have said: why to duplicate efforts? In that case, you the Seaside one click. What cab be easier than that ? And it would be FAR more stable than ours. Do we create PharoGlassClient image ? no. Do we create PharoMoos image? no. Because it is obvious that they know better than us what versions to include. Of course, if Seaside ready images doesn't exist we will probably do it. Give me only one reason why spending time and resources in PharoWeb? (taking into account you have other several alternatives better than this)
I don't see it as duplicating efforts, the Pharo-Web image is (should be) more than Pharo-Seaside and having this sandpit image will probably give a lot more feedback than just having a Pharo-Dev image ... in my view. Mariano Martinez Peck wrote:
There is no such thing of "Pharo team". Pharo team are us. You. The community. Pharo has NO employee. There is the board but doesn't mean they are working full time in Pharo.
Settle down mate ... anyway, the Pharo Team is doing great stuff :) -- View this message in context: http://n2.nabble.com/What-about-killing-PharoWeb-images-tp4249050p4256091.ht... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.