Re: [Pharo-users] Pharo-users Digest, Vol 57, Issue 39

2018-01-15 Thread Richard Sargent
"Worse is that Gemtalk sees Gemstone as a separate entity. Object persistence requires application level integration ie. gemstone requires you to develop your app and have it run in the stone in order to persist. The Gemtalk philosophy is thus flawed on the face of it." I would like to offer som

Re: [Pharo-users] Pharo-users Digest, Vol 57, Issue 39

2018-01-15 Thread Ben Coman
On 15 January 2018 at 21:42, Ian Ian wrote: > > For my money: > > * Gemtalk should integrate development tools directly into Gemstone > > I reiterate that Pharo with built in persistence as in a fully integrated > Gemstone is, IMHO, the best approach to take. Hi Ian, You may find the following

Re: [Pharo-users] Pharo-users Digest, Vol 57, Issue 39

2018-01-15 Thread Ian Ian
W.R.T Database Connectivity: Hi All, The database connectivity issue as discussed is near and dear to my evaluation of Smalltalk(s). It is a huge problem/stumbling block as I see it. Here Is a cut and paste of my replay to the Gemstone users group: > Hi Dale, I