Hi Sven,
On Jan 13, 2018, at 6:01 AM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 13 Jan 2018, at 05:22, Eliot Miranda <eliot.miranda@gmail.com> wrote:
Isn't it important to preserve the ability to exchange code between Pharo, Squeak and Cuis? Don't you care that the VM development is directly affected by this? Is the VM and plugin support not important to Pharo?
Eliot,
Not trying to minimise your contributions (we all love the VM), and I know that you favour collaboration, but
(1) what non-trivial code is actively maintained from a single code base between Pharo, Squeak and Cuis ?
Alien
(2) how/where are you developing in Pharo ? I only see you contributing to Squeak, where only a handful of very experienced developers are making occasional, conservative changes to maintain their own environment.
You may be using the 64-bit version of Pharo. That is my work. If you're using the FFI then I've had a part in it (callbacks being the most specific). And the new release will use the Sista bytecode set. That's me and Clément. Clément and others integrate stuff on my behalf. I also work closely with people in the Pharo community and get work from users of Pharo. Pharo is important to me. But this isn't about me. I disagree with your description of the Squeak community. St Potsdam it is used by students. The raspberry pi scratch was in Squeak until late last year. It is not as you describe.
For me, and many others the VM is a completely closed ecosystem, a black box. A know the simulator is cool, but I have never seen it.
What does that have to do with this discussion?
Your choice to use Squeak is a valid one that probably makes sense to you, but you must also respect the successful alternative that Pharo is.
Again how does my criticisms my the git integration have anything to do with Pharo being a successful alternative? Do you think I want Pharo to fail? Do you think I would bother commenting if I wasn't interested?
Sven
Stef
On Fri, Jan 12, 2018 at 1:09 AM, Torsten Bergmann <astares@gmx.de> wrote: Not having timestamps/authors in Pharo 7 due to git and missing blame support (see [1]) has other bad side effects:
- it clobbers all method stamps in an MCZ package [1] if you use Monticello which can lead easily to trouble/lamenting
- it is not possible to fileout a changeset [2] in the ChangeSorter
Was there any further discussion/decision for P7 on solving this or adding blame support?
Thx T.
[1] http://forum.world.st/Author-name-in-version-Iceberg-td4968472.html [2] http://lists.squeakfoundation.org/pipermail/vm-dev/2018-January/026350.html [3] https://pharo.fogbugz.com/f/cases/20951/