On 9 déc. 04, at 16:50, Charles A. Monteiro wrote:
Stef:
I have no problems with your move, I mean what can I do. Since I don't
intend to use the Squeak version I guess I will have to enhance
SmallWiki 1 as I go and which I already have. I do have a problem with
with folks not understanding the NC license.
Me too. Because Cincom should do a much better work to communicate
that. And for me this is crucial that VW exist and
get clients but I will not do their job.
It has now officially become annoying to me. I am not
sure why you all
are experiencing 40 minutes on a merge.
I do not know. I discussed with alan and we change the postgres server
but we got even a slow down with the latest
postgres.
I assume that this is not on the SmallWiki code base
because my code
base here is so humongously larger than SmallWiki and it no where
takes me as long. Are you all doing incremental merges?
On Moose which is not that bigger. I can tell you that I went eating
waiting that the merge (really nothing may be ten methods there and
there) was done.
If American Express decides to use a SmallWiki purely
as its Intranet
content server they still should pay. If you are small company and
have your employees telephone numbers on a SmallWiki then don't pay
unless you want support of course. Simple.
I know.
The small companies that don't work on VW
don't because they don't
understand the license.
Exact but what can I do. Cincom should communicate better.
You get what you pay for. Don't get me wrong. I
think Squeak is really
cool. Some very interesting and innovative things have come out of it
and still do and will. However, it is not an enterprise level
development environment. It is really not that well suited for
business development. Some people have, I understand. But one will hit
a wall. The performance is not there, the tools are not there, it is
just not a VW and I mean that again from a business dev perspective. I
like Squeak especially stuff like Croquet.
I know but as I said SmallWiki should first build a strong community
and VWers were not there.
So let us cross our fingers and see. SW II will be really cool (and is
already with seaside components) but
this is open source so people will be able to do what they want with
it, even money if they can.
So I think that we will learn from the experience and the second
iteration will be really better (command, better url, seaside,
metadescription, backend based on a db....)
Stef