Skip to Content.
Sympa Menu

internetworkers - Re: The list isn't blowing up yet?

internetworkers AT lists.ibiblio.org

Subject: Internetworkers: http://www.ibiblio.org/internetworkers/

List archive

Chronological Thread  
  • From: "Chris Owens" <internetworkers_box AT reality-v2-dev.com>
  • To: "'InterNetWorkers'" <internetworkers AT franklin.oit.unc.edu>
  • Subject: Re: The list isn't blowing up yet?
  • Date: Fri, 7 Sep 2001 13:23:05 -0400


Regarding the C# standards, isn't it following a similar model to that
of Java and other products such as AppForge? The published plan is to
allow for the Common Language Runtime (CLR) to be ported as necessary or
desired to other platforms. This would allow code written in C# to run
on other platforms. The JVM operates in a similar fashion does it not?


Chris Owens
chris.owens AT reality-v2.com
919.345.4339 mobile


-----Original Message-----
From: Michael S Czeiszperger [mailto:czei AT webperformanceinc.com]
Sent: Friday, September 07, 2001 12:59 PM
To: InterNetWorkers
Subject: [internetworkers] Re: The list isn't blowing up yet?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 07 September 2001 11:54 am, you wrote:
> The key word here is "proprietary". Most technical standards
like
> railroad gauges, 60 hz AC, and so forth are established by agreement
> among several players within a given industry and controlled by the
> government (NSI) or trade groups. Most industry standards are
> established and managed openly. Microsoft wants to establish
standards
> for a huge segment of our world and control them from behind closed
> doors. Brutal, yes.
>

I've found that the open source movement has taken focus away from open
standards, which is unfortunate. With open standards, it doesn't matter
if
you have access to the source, since anyone can implement the standard,
and
there's no question of ownership. Companies can cooperate with regards
to
defining standards, and then compete on the quality of the
implementation.

Open source without open standards isn't quite as useful, as source
quite
often isn't cross platform, and can be quite complex so the protocols,
file
formats, etc, can be obfuscated.

The next big thing to look at in terms of standards is .NET. Microsoft
will
make C# the language a standard of some sort, but in typical fashion is
hiding the fact that most of the C# code won't run on non-Microsoft
platforms. The reason is only the bare language itself will be a
standard,
not the libraries, and the libraries will mostly be wrappers around
existing
Windows APIs, which are proprietary. This way they can claim to support
standards, while making sure that no one will either be able to
implement a
competing product, or port the C# libraries to other platforms.

- --
Michael S Czeiszperger
czei AT webperformanceinc.com

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQA/AwUBO5j8yVgOl/a4Fw2AEQKLJgCeJbsal9rku8eBzO5Ge03EKdbrJF8AnA6O
CipUc//Y4wxXbAWBBkL4baZP
=tZyY
-----END PGP SIGNATURE-----

---
Come and play at the InterNetWorkers Web site!
http://www.ibiblio.org/internetworkers/
You are currently subscribed to internetworkers as:
internetworkers_box AT reality-v2-dev.com
To unsubscribe send a blank email to
$subst('Email.Unsub')





Archive powered by MHonArc 2.6.24.

Top of Page