Today I just received an email inviting me to join this web seminar. Yes
that’s right…it’s October 1st and I got an invite via email to join the
seminar on September 29th. Did anyone else get this?
QSSL, you guys need to get your crap together. This looks bad. You’re a
technology company…you shouldn’t be making mistakes like this!
The webcast itself was rather short of expectations too. The usual ritual
talk about the microkernel vs monolithic for an appetizer, as if people
still haven’t figured that out a decade after Mach3… Then goes the
entree
served in form of a statement that an ethernet driver was ported in some
12
hours while preserving 80% of the original code. Great, except there was
no
details whatsoever, save for few macros to make already OS-independent
code
compile. The rest 20% (that would be the point of such a presentation
IMHO)
were left as an exsercize for the audience… Then the desert came - ‘we
will gladly answer any questions…’
I did not know what to ask, still feeling like I haven’t ate anything when
the dinner was over. I’ve been tempted to ask why the hell people would
consider moving in the first place, since I haven’t noticed an answer to
that main question anywhere in the menu… but decided not to make a
public
scandal. So, no tip for you this time. Stale food that was not even good
when it was fresh anyway, thank you very much.
– igor
P.S.
I’ve been down that road three times myself and I know there is more to
tell and to do to help people along…
“QNX” <kevin@ffllyyiinnggrroobboottss…ccoomm> wrote in message
news:bla9je$7an$> 1@inn.qnx.com> …
I’ve been sitting here working on things, and I had a few thoughts I
wanted
to add.
If you’re going to attack Linux. Attack it. But attack it head on. It
is
inferior product when compared the QNX in many ways. Stop with the
cheap
shots with regards to legality. There is no respect in that.
If you have case studies as to how much it really costs to use Linux
compared to QNX. Show them. If you have industry examples how a
product
was brought to market cheaper and faster, use it. If you want to show
how
QNX is more reliable, faster, etc, etc. Do it. Make those claims.
Make
'em loud and make 'em big and make 'em long. BE BOLD
I favor gettring aggressive against Linux. I think a problem that you
will
have is that once it is chosen, it is more difficult to change
directions.
I realize that this web seminar is supposed to help out with that, but
they
aren’t going to change directions today because there is some threatened
lawsuit against it.
I think that if you want people to change today, you need to contrast
the
product with yours. This is harder and much more difficult and even
expensive to do. But this is what needs to be done. Stop with the
cheap
shots and get serious.
Kevin
“Kevin Stallard” <> kevin@ffflyingrobots.com> > wrote in message
news:bl9lg9$mpm$> 1@inn.qnx.com> …
Still, QNX is proposing something to people who by implication are
already
involved with Linux, using a cliche FUD statement. That will if
anything,
annoy them very much and turn off the interest. Very short sighted
and
unimaginative. The author of that statement also has mixed up the
target
audiences… If this is for managers, the webcast should not be
technical.
If this is for engineers, they don’t need such silly baits. And in
any
case,
QNX should have balls to propose their stuff because it is BETTER
not
because SCO has a lawsuit…
Now that almost any company has some project going using Linux, the
scare
tactics does not work even with managers anymore - they are more
afraid
to
use QNX than Linux because of the black sheep syndrome. But if you
can
show
a real technical and/or financial merit, anyone with brains will
give
it
a
consideration.
– igor
I have to agree. Even though technacally QNX is better, the fact is
people
are being succesfull in their embedded/RT Lunux apps or there would be
a
backlash against it. You’d read about it a lot more.
This web seminar thingy looks like QSSL betting that SCO will prevail.
It’s
too bad QSSL doesn’t have more confidence in themselves and their
product.
Kevin
\