[Mono-list] About WinFx
Xavier Amado
xavier@blackbloodstudios.com
Mon, 27 Oct 2003 23:39:25 -0300
--=-bStF3AkQ4DfHlPZnPZ4y
Content-Type: multipart/alternative; boundary="=-/ErIC5Yh7Dv9Wlslls/l"
--=-/ErIC5Yh7Dv9Wlslls/l
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
Besides that that's not true as miguel and jasper replied, even If MS
ever did such a thing of letting Mono out of the .NET updates scoop, it
will never become useless, I mean, it might not become .NET compliant,
but it will still be a great environment to develop linux desktop
applications on, wheter or not they would run on windows or not (which I
never really cared about yet). If such thing happened the Mono team
could even improve the Mono Class library in ways they wanted.
But anyway, that won't happen for the reasons that were already stated.
By the way, what's that guy in /. talking about? .NET not supporting
unmanaged code, drm signing, etc...=20
On Mon, 2003-10-27 at 17:28, Maurizio Colucci wrote:
> Someone on the slashdot forum said that WinFx is going to make mono usele=
ss.
> How much is true about that?
>=20
> http://slashdot.org/comments.pl?sid=3D83739&threshold=3D1&commentsort=3D0=
&tid=3D109&tid=3D185&tid=3D187&tid=3D190&mode=3Dthread&pid=3D7321209#732137=
6
>=20
> _______________________________________________
> Mono-list maillist - Mono-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list
=20
________________________________________________________________________
Xavier Amado (xavier@blackbloodstudios.com)
CTO Black Blood Studios
--=-/ErIC5Yh7Dv9Wlslls/l
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; CHARSET=3DUTF-8">
<META NAME=3D"GENERATOR" CONTENT=3D"GtkHTML/3.0.9">
</HEAD>
<BODY>
Besides that that's not true as miguel and jasper replied, even If MS ever =
did such a thing of letting Mono out of the .NET updates scoop, it will nev=
er become useless, I mean, it might not become .NET compliant, but it will =
still be a great environment to develop linux desktop applications on, whet=
er or not they would run on windows or not (which I never really cared abou=
t yet). If such thing happened the Mono team could even improve the Mono Cl=
ass library in ways they wanted.<BR>
<BR>
But anyway, that won't happen for the reasons that were already stated.<BR>
<BR>
By the way, what's that guy in /. talking about? .NET not supporting unmana=
ged code, drm signing, etc... <BR>
<BR>
On Mon, 2003-10-27 at 17:28, Maurizio Colucci wrote:
<BLOCKQUOTE TYPE=3DCITE>
<PRE><FONT COLOR=3D"#737373"><I>Someone on the slashdot forum said that Win=
Fx is going to make mono useless.
How much is true about that?
</FONT>
<A HREF=3D"http://slashdot.org/comments.pl?sid=3D83739&threshold=3D1&commen=
tsort=3D0&tid=3D109&tid=3D185&tid=3D187&tid=3D190&mode=3Dthread&pid=3D73212=
09#7321376"><U>http://slashdot.org/comments.pl?sid=3D83739&threshold=3D=
1&commentsort=3D0&tid=3D109&tid=3D185&tid=3D187&tid=3D1=
90&mode=3Dthread&pid=3D7321209#7321376</U></A>
<FONT COLOR=3D"#737373">
_______________________________________________
Mono-list maillist - Mono-list@lists.ximian.com</FONT>
<A HREF=3D"http://lists.ximian.com/mailman/listinfo/mono-list"><U>http://li=
sts.ximian.com/mailman/listinfo/mono-list</U></I></A></PRE>
</BLOCKQUOTE>
<PRE><TABLE CELLSPACING=3D"0" CELLPADDING=3D"0" WIDTH=3D"100%">
<TR>
<TD>
<DIV ALIGN=3Dright>
<HR>
</DIV><BR>
<DIV ALIGN=3Dright><B>Xavier Amado</B> (<I>xavier<B>@</B>blackbloodstudios<=
B>.</B>com</I>)</DIV><BR>
<DIV ALIGN=3Dright>CTO Black Blood Studios</DIV>
</TD>
</TR>
</TABLE>
</PRE>
</BODY>
</HTML>
--=-/ErIC5Yh7Dv9Wlslls/l--
--=-bStF3AkQ4DfHlPZnPZ4y
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQA/ndbdp6L3ZcohV58RAgYDAJ4uq55do5KDlwkOXrPvMyHTNJyslwCgkq9w
6b05B3laYXEpV+lXsyoS5rM=
=imHc
-----END PGP SIGNATURE-----
--=-bStF3AkQ4DfHlPZnPZ4y--