But not also... Because right now the way changes are integrated is using the same update mechanism if I'm not mistaken.
The very challenge of the update is that you are updating your image, which has your objects, and your changes! So, what if you made some changes in the core classes? update may fail on merge or even remove your changes. If you keep your method you may lose a bugfix If there was a rename of that method you changed? what should the update do? If you configured some shortcuts? the update may reset them The changesets? they may be reset And the list goes on... On Wed, May 21, 2014 at 2:49 PM, Esteban A. Maringolo <emaring...@gmail.com>wrote: > 2014-05-21 7:11 GMT-03:00 stepharo <steph...@free.fr>: > > So we should probably remove the software update button. > > +1 > > > > Stef > > PS: the last time I updated my iPhone it blocked and I had to fully > > reinstall everything. > > And once when I updated my mac my mouse got blocked forever on the left > top > > corner. > > You might be one of the lots of unlucky persons that got issues while > updating iOS/MacOS, but sill you probably represent less than the 1% > of the total userbase (of which the rest updated with no issues). > > The hard thing here is Pharo tries to update itself while running, it > is like trying to modify a plane while flying. > > > > Esteban A. Maringolo > >
