From: "Michael T. Richter" Date: 2007-10-22T19:29:22+09:00 Subject: Re: IronRuby...will it be like J++? --=-FmaSx9fCO7BCKUK37y/n Content-Type: multipart/alternative; boundary="=-/mc3+Ezwfeprk3iPyG+k" --=-/mc3+Ezwfeprk3iPyG+k Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2007-22-10 at 19:05 +0900, Clifford Heath wrote: > Thufir wrote: > > Could it be that Microsoft won't fully implement the language=20 > > specifications, a la the J++ versus Java scenario? >=20 > They have no need to do that. >=20 > > What are some potential issues down the road? >=20 > The issue is that many Ruby programs will be built that rely on > (i.e. benefit from) using facilities only available on MS platforms. > That's good if you need those programs, but the rest of us won't be > able to run them. The sheer size of the MS installed base means that > over time, there'll be no certainty for anyone new to Ruby about how > to find a program they can use. Almost all cross-platform Ruby program > will spawn MS-specific forks, and the community will divide into those > whose programs work on Microsoft and those who don't. >=20 > Classic divide and conquer, combined with a swamping strategy, > regardless of licensing issues. Divide the community and make the > smaller group irrelevant. Yeah. Because that worked really well for them with Java. --=20 Michael T. Richter (GoogleTalk: ttmrichter@gmail.com) Never, ever, ever let systems-level engineers do human interaction design unless they have displayed a proven secondary talent in that area. Their opinion of what represents good human-computer interaction tends to be a bit off-track. (Bruce Tognazzini) --=-/mc3+Ezwfeprk3iPyG+k Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Mon, 2007-22-10 at 19:05 +0900, Clifford Heath wrote:

Thufir wrote:
> Could it be that Microsoft won't fully impleme=
nt the language 
> specifications, a la the J++ versus Java scena=
rio?

They have no need to do that.

> What are some potential issues down the road?<=
/FONT>

The issue is that many Ruby programs will be built =
that rely on
(i.e. benefit from) using facilities only available=
 on MS platforms.
That's good if you need those programs, but the res=
t of us won't be
able to run them. The sheer size of the MS installe=
d base means that
over time, there'll be no certainty for anyone new =
to Ruby about how
to find a program they can use. Almost all cross-pl=
atform Ruby program
will spawn MS-specific forks, and the community wil=
l divide into those
whose programs work on Microsoft and those who don'=
t.

Classic divide and conquer, combined with a swampin=
g strategy,
regardless of licensing issues. Divide the communit=
y and make the
smaller group irrelevant.

Yeah. Because that worked really well for them with Java.

--
Michael T. Richter <ttmri= chter@gmail.com> (GoogleTalk: ttmrichter@gmail.com)
Never, ever, ever let systems-level engineers do human interaction desig= n unless they have displayed a proven secondary talent in that area. Their = opinion of what represents good human-computer interaction tends to be a bi= t off-track. (Bruce Tognazzini)

--=-/mc3+Ezwfeprk3iPyG+k-- --=-FmaSx9fCO7BCKUK37y/n Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQBHHHtqLqyWkKVQ54QRAtSYAJ4xTjPbnKg+GJNhHPlDYUzsAcQjSwCfXRYB 5WjZDnjOUZAagAQ9s8nTPOA= =w9oQ -----END PGP SIGNATURE----- --=-FmaSx9fCO7BCKUK37y/n--