caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: Richard Jones <rich@annexia.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Google trends
Date: Fri, 02 Nov 2007 14:01:48 +1100	[thread overview]
Message-ID: <1193972508.31239.82.camel@rosella.wigram> (raw)
In-Reply-To: <20071101180535.GA28124@furbychan.cocan.org>


On Thu, 2007-11-01 at 18:05 +0000, Richard Jones wrote:
> On Fri, Nov 02, 2007 at 03:10:17AM +1100, skaller wrote:
> > On Thu, 2007-11-01 at 09:01 -0400, Brian Hurt wrote:
> > > It's weird, and I don't understand it, but there are a lot of people for 
> > > whom Microsoft is a comfort zone- 
> > 
> > Huh? What's weird? Where have you been the last 3 decades?
> > Microsoft put computers on everyone's desktop, just as
> > Bill Gates said he would.
> > 
> > I guess 99% of all desktops run Windows. Quite a lot of
> > servers run Windows too.
> 
> Whew, really trying not to be bated on the Microsoft discussion here,
> but that is a _very_ odd view of history.

This is not history.. it's the current affairs of my life.
I watched it happen, I even helped a bit :)

> Open source developers use crap languages, I agree, but switching to
> C++ would hardly have improved the situation :-)

That's just silliness. C++ is a much better language than C for
application development.

I prefer Ocaml .. but hardly anyone here in Australia has even
heard of it (even companies using *nix).

> FWIW early versions of the Linux kernel could be and sometimes were
> compiled as C++ (though still of course written in C) so it's not like
> people were unaware of the language or lacked solid implementations at
> that point.

Lack of solid implementation was *always* the biggest problem. 
GNU wasn't even a player. It was only recently (last year?) 
that GNU finally released a  C++ compiler (4.X series) that 
could even parse C++ properly.

Don't forget the ISO C++ Standard wasn't ratified until this
millenium .. it's barely 7 years old. I think that is younger
than Linux kernel :)


-- 
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net


  reply	other threads:[~2007-11-02 13:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-01  1:02 Jon Harrop
2007-11-01  2:20 ` [Caml-list] " skaller
2007-11-01  8:37 ` Oliver Bandel
2007-11-01  9:31   ` Ulf Wiger (TN/EAB)
2007-11-01 10:55     ` Oliver Bandel
2007-11-01  9:46 ` Richard Jones
2007-11-01 12:00   ` skaller
2007-11-01 12:46     ` Richard Jones
2007-11-01 15:45       ` skaller
2007-11-01 16:31   ` Jon Harrop
2007-11-01 18:12     ` Richard Jones
2007-11-01 19:47       ` Peng Zang
2007-11-02  3:11       ` Jon Harrop
2007-11-02 13:48         ` Lars Nilsson
2007-11-02 15:54           ` Oliver Bandel
2007-11-01 13:01 ` Brian Hurt
2007-11-01 16:10   ` skaller
2007-11-01 18:05     ` Richard Jones
2007-11-02  3:01       ` skaller [this message]
2007-11-02 15:50         ` Jon Harrop
2007-11-02 16:26           ` Ulf Wiger (TN/EAB)
2007-11-02 16:07         ` Language trends / Caml popularity (Re: [Caml-list] Google trends) Oliver Bandel
2007-11-01 21:00 ` [Caml-list] Google trends Dario Teixeira
2007-11-03  0:02   ` Florian Weimer
2007-11-02 22:45 ` Florian Weimer
2007-11-03  1:32   ` Jon Harrop

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=1193972508.31239.82.camel@rosella.wigram \
    --to=skaller@users.sourceforge.net \
    --cc=caml-list@inria.fr \
    --cc=rich@annexia.org \
    /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).