Posted by
pdigonzelli1 on
Aug 18, 2015; 4:32pm
URL: https://forum.world.st/Fwd-ANN-Magma-1-5-tp4843768p4843845.html
Yes I checkesd. It is by far better approach to pharo and I like it very much.
The problem i found was when i stress mongo, it lost some transactions (i.e 10000 rewrites lost about 80 or more don't remember exactly) .
In bussiness apps i cannot take that risk.
Ing. Pablo Digonzelli
Software Solutions
IP-Solutiones SRL
Metrotec SRL
25 de Mayo 521
San Miguel de Tucumán
Email:
[hidden email]
[hidden email]
Cel: 5493815982714
----- Mensaje original -----
De: "Esteban Lorenzano" <
[hidden email]>
Para: "Any question about pharo is welcome" <
[hidden email]>
CC:
[hidden email], "Torsten Bergmann" <
[hidden email]>,
[hidden email]
Enviados: Martes, 18 de Agosto 2015 12:45:05
Asunto: ***UNCHECKED*** Re: [Pharo-users] [ANN] Magma 1.5
> On 18 Aug 2015, at 17:20, Pablo R. Digonzelli <
[hidden email]> wrote:
>
> I can colaborate. I do not know if i have the time and technical skills to do it alone, but for shure i can colaborate.
> I think magma will be a very interesting option for object persistence in pharo.
> I am currently working with garage and glorp and i suffers the innecesary complexity and other bad things thet persistence layer introduce in developing pharo apps.
have you checked voyage? (to work with a MongoDB)… it will avoid all the pain of using a relational database.
Esteban
ps: But yes, I do believe having magma would be cool too.
>
> Pharo
>
>
> Ing. Pablo Digonzelli
> Software Solutions
> IP-Solutiones SRL
> Metrotec SRL
> 25 de Mayo 521
> San Miguel de Tucumán
> Email:
[hidden email]
>
[hidden email]
> Cel: 5493815982714
>
> ----- Mensaje original -----
> De: "Torsten Bergmann" <
[hidden email]>
> Para: "Any question about pharo is welcome" <
[hidden email]>
> CC:
[hidden email],
[hidden email],
[hidden email], "Pablo Digonzelli" <
[hidden email]>
> Enviados: Martes, 18 de Agosto 2015 10:26:44
> Asunto: Fwd: [ANN] Magma 1.5
>
> Stephan Eggermont wrote:
>> It is possible, and it needs someone who can deal with low-level
>> details. Magma has its own mailing list. Chris has repeatedly said he'd
>> be willing to help out, but is not willing to be the Pharo port maintainer.
>
> I asked Chris directly and you can find his answer here on the magma list:
>
>
http://lists.squeakfoundation.org/pipermail/magma/2015-August/001955.html>
> As ever it requires someone to move this forward to make it happen.
> But as there was an initiative with Magma 1.3 for Pharo 1.3 already it does not
> seem impossible.
>
> Also - as Stef already pointed out - community services like CI could be used
> to maintain it once an initial up to date port was done.
>
> Bye
> T.
>