On 20 July 2011 14:42, Philippe Marschall
<[email protected]> wrote:
> On 07/20/2011 09:00 AM, Serge Stinckwich wrote:
>> On Wed, Jul 20, 2011 at 1:36 PM, Philippe Marschall
>> <[email protected]> wrote:
>>> On 07/19/2011 09:41 PM, Esteban Lorenzano wrote:
>>>> yes... there is a problem in latest vm's and UUID generation (I don't know
>>>> if it is present at any vm or just mines, but well...). For the moment,
>>>> faster solution is by deactivating uuid primitive, at:
>>>>
>>>> UUID>>#primMakeUUID
>>>> <primitive: 'primitiveMakeUUID' module: 'UUIDPlugin'>
>>>> UUIDGenerator default generateBytes: self forVersion: 4.
>>>>
>>>> just comment the primitive call.
>>>
>>> Guys, srsly? Is this some kind of practical joke? You have been shipping
>>> with a known bug that has a trivial fix and eats peoples code? You are
>>> wondering why nobody takes you seriously and you don't have more users?
>>> You teach software engineering?
>>
>> Hum, you know like in most open-source software project, nothing
>> happens by magic, unfortunately.
>> Human ressources are very scarce as Pharo is a part-time project for
>> most of us. Maybe your problem will required some interactions between
>> VM guys and Pharoers. Not something that could be done in 5 minutes.
>>
>> Did you submit an issue in the bug tracker just to keep track of it ?
>> Did you package some patch that could be used more easily by people
>> who do the release ?
>>
>>> This is exactly the kind of shit that makes me want to never again use
>>> Pharo in production. This is the reason why I don't recommend Pharo to
>>> other people.
>>
>> If you use Pharo in production did you give money to support the project ?
>> Pharo is not supported by a company (not yet), so no commitments could
>> be done on the speed of the adoption of patches.
>> People are just doing their best to enhance the system. And if you
>> help them (by packaging patches that solve some problems), everyone
>> will win in the long term.
>
> And that is completely fine. But then you don't have to be surprised
> when people don't take you serious, you don't have more users and you
> don't have any enterprise penetration.
>
> To quote from the project page:
> "We want Pharo to be the obvious choice for professional development in
> an open-source Smalltalk."
>
> Pro tip: if you want to be the obvious choice for professional
> development don't eat peoples code.
>
Philippe, you are using Cog VMs which are under development.
Of course , we're all expecting that there is no regressions
introduced. But sometimes this happens.
This is normal for development process.
So, you discovered a bug, which needs to be fixed. But blaming pharo
for something, which we're not responsible for is a mistake.
You should know better who to blame. Since you using "cog r2462", why
you addressing your claims to Pharo instead of VM developers?
Pharo images run on top of different VMs, and depending which one you
using, you mileage could vary.
Well, maybe it wasn't clear to you. But keep in mind, depending on
what VM you using, you may have or not have bugs.
At the end of this week (i hope) i will set up a test runners for VMs
we're building, so we can automatically track regressions from change
to change,
including one you discovered.
Feel free to submit an additional test for UUID to prevent this
regression in a future. Something like:
size := ((1 to: 100) collect: [ :i |
UUID new asString ]) asSet size
self assert: size = 100
and we will happily integrate it.
> Cheers
> Philippe
--
Best regards,
Igor Stasenko AKA sig.
