[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] Chilisoft ASP
- Subject: RE: [cobalt-users] Chilisoft ASP
- From: "Lyle Scheer" <lyle@xxxxxxxxxxxxx>
- Date: Thu Feb 3 15:44:58 2000
> I am not so much irritated at the fact that they are adopting
> it, but at the
> fact that they are ignoring PHP. We have a proven, tested,
> superior product
> that is not in any way attached to Microsoft, and Cobalts is
> choosing to go
> with hack of a hacked Microsoft product (which was a hack to
> begin with)?!?!
> Its nutz.
It's interesting. Cobalt has a business development group that works with
companies that want their software on our product. Those companies provide
the resources to put that code on our products. Cobalt has a finite
engineering staff that is dedicated to creating and maintaining products.
I'm not trying to excuse Cobalt by not focusing on PHP, which is obviously
useful... I'm just pointing out that the mechanism we are using to create
more and varied custom servers and services out of our core product requires
an outside team to spend resource creating a particular solution. Because
Chilisoft has that resource that they are willing to dedicate, we end up
selling a "Chilisoft box".
I don't think it is a matter of someone at Cobalt saying, "Hmmm... PHP or
Chilisoft? I think I'll go Chilisoft." It's more like Chilisoft preparing
and creating an installable product that gets placed on our machine, but
there is no advocate group from the open source community working with our
business development group creating a PHP package to be put on our machine,
merely some users asking why Cobalt isn't expending the resource to do so
itself.
I'm in no way advocating any particular practice or model, I am pointing out
a business model that we are using that may give you an insight into how
solutions may get on our products.
Now, I am fully prepared to agree that PHP is superior to Chilisoft even
though I don't know much about either, but I believe in the open source
model producing good code. I am also in the terms of this discussion going
to assume that our business model is not likely to change. The question I
come up with is: How can third parties that aren't really interested in
developing their solution commercially but have useful applications have
their code available on Cobalt products?
- Lyle