<<Pharo has the easiest deployment in any language I have used.>>
Only if you think deployment means shipping your entire development
environment to users and telling them to get on with it.
Pharo is absolutely the worst language for deployment in the world. This is
why, after all these years, there have only ever been three desktop
applications written in it - phratch, dr geo, and the a legal database
thing. (i suppose you could be generous and include pharo launcher as well -
though that's a bit incestuous).
We are concerned with that aspect. This is not by accident that
Guillermo spent
3 years working on bootstrapping a kernel. This is not by accident that
Pavel
is producing small images. This is not by accident that we want to manage
the ***Complete*** image and eco systems with dependencies and that we
are fighting with
cycles and layers. This is not by accident that we are revisiting all
the places that write on disc believing that
they can.
Now we should probably invest in a solution like the one of Hernan to
build application wrapper
I think that also having a better abstraction for user deployment is
needed.
Right now we are working on a bootstrap in production for multiple
reason but the main one is
to get a clean 'small' kernel so that we can build using normal
dependency small applications.
If you think that we are going slowly. We are getting slowly and too
slow for my taste.
I did you analysis back in 2002 :)
Now if you want to help us going faster. Help the community fixing bugs.
The less other things we have to do the more we can focus.
Stef
All other applications written in pharo are web apps so deployment is not an
issue.
There may be good reasons for the lack of attention paid to the deployment
of apps but pretending there is no problem is crazy.
--
View this message in context:
http://forum.world.st/standalone-runtime-executable-tp4911677p4912370.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
