The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ckeck@texoma.net (Cornelius Keck)
Subject: [TUHS] Re: TUHS digest, Vol 1 #159 - 12 msgs
Date: Sun, 1 Jun 2003 23:05:22 -0500 (CDT)	[thread overview]
Message-ID: <Pine.BSF.4.05.10306012252140.18452-100000@ppp-151-110-2.texoma.net> (raw)
In-Reply-To: <20030530033124.GB39668@wantadilla.lemis.com>

> As far as I can see (somebody please correct me if I'm wrong), most of
> the key players at SCO have changed over the last 12 months.  They
> ppear to have few engineers left, which is presumably one reason wh
> they gave the UnixWare and Linux code to outsiders to compare.  I'm

I'm not surprised. Considering SCO's pricing policy (ever looked at
that? They charge for every little bit of configuration above and be-
yond, say, Sony PS2 multiplayer environment, like extra users, more
memory, more processors, ..., uname it, they charge for it), the place
looks more and more like a dominion of marketing folks, and lawyers,
with the latter no longer being considered a defense entity against
unfriendly intrusion, but rather a business division, expected to
generate substantial revenue. If a company trades innovative head-
count (i.e. developers and engineers) for headcount unaware, or un-
familiar with the prime business objective, then the second rate
headcount will come up with many "interesting" schemes to justify
their continued employment.

I might be overdoing it just so. But then I have seen this happen
thrice during my career, so there is a pattern.

Thank you for listening to a not-too-old man rambling ;)

Regards,

Cornelius


-- 
                             Cornelius Keck
                 cornelius at keck.cx / ckeck at texoma.net



  reply	other threads:[~2003-06-02  4:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200305300130.h4U1UMJ8091290@minnie.tuhs.org>
2003-05-30  2:42 ` Larry McVoy
2003-05-30  3:31   ` Greg 'groggy' Lehey
2003-06-02  4:05     ` Cornelius Keck [this message]
2003-06-02  2:51 Norman Wilson
2003-06-02 15:30 Ian King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.BSF.4.05.10306012252140.18452-100000@ppp-151-110-2.texoma.net \
    --to=ckeck@texoma.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).