7 Exercise Tips How to Stream 'Rabbit Hole' Roblox's AI Efforts 9 Household Items You're Not Cleaning Enough Better Sound on FaceTime Calls 'X-Ray Vision' for AR 9 Signs You Need Glasses When Your Tax Refund Will Arrive
Want CNET to notify you of price drops and the latest stories?
No, thank you

Putting .Net under the microscope

A News.com reader writes that there is some level of misunderstanding in parts of the IT community about Microsoft's .Net technologies.


Putting .Net under the microscope

In response to the Feb. 7 column by Bill Joy, "Microsoft's blind spot":

It's clear to me that there is some level of misunderstanding in parts of the information-technology community about Microsoft's .Net technologies. Bill Joy seems to infer that the ability to write "unsafe" code is tantamount to the .Net framework probably being full of security holes. He uses script vulnerabilities in Internet Explorer and older versions of Outlook as examples of Microsoft's inability to write secure code.

Time will tell, they say, but it doesn't look that way from my vantage point. Indeed, from a platform perspective, Microsoft has been proven to have the least number of vulnerabilities/exploits reported in the last year, while clearly being the more popular platform. It has also been proven to be more responsive to security issues than most of its competitors, including Sun Microsystems.

However, what is clear is that Joy has not really done his homework. C# is a language, similar to Java being a language (which as he readily admits, C# now more standard that Java; I still can't understand why a company so much behind open source insists on keeping Java proprietary) that has the ability to create both managed and/or unmanaged code under the .Net framework. Managed code is "managed" by the common-language runtime environment, and it includes various levels of declarative application and policy-based security. This is also not specific to C#--it's part of the .Net framework as a whole. You can research this, and the information is free. For example, you would need to write device drivers using unmanaged code.

If the CLR did indeed garner anything from Java, it's hard to say. Regarding the Java Virtual Machine concept: Please, it's not rocket science. VMs have been in use far longer than the JVM. Indeed, it seems that Java has benefited from the innovations presented by Microsoft, most namely the adoption--or should we say adaption--of the Microsoft Transaction Server technologies into J2EE.

It's no wonder that hardware companies like Sun are having difficulty keeping the lights on when they truly don't understand some of the basic, core concepts of what their competitors are doing. I would assume this is the case, as Joy's title indicates he is the chief scientist at Sun. Or perhaps misleading the industry perception is the next best way to compete, behind lobbying politicians and launching court cases.

CNET, please keep the commentary coming--it's indeed healthy for the industry.

Joshua Gallant
Toronto, Ontario



Latest Headlines
display on desktop
House backs cybersecurity with dollars
BT prepares to defend Web-surfing patent
NY accuses software maker of censorship
Tabloid to readers: Log off and cough up
Overture bullish despite EarthLink loss
EDS profit surges on others' cost cuts
Stocks fall for fifth straight day
OpenTV files patent suit against Liberate
Power struggle at PalmSource
Microsoft developers feel Windows pain
ABCNews.com scraps Yahoo deal
NPR tunes in to multimedia reporting
Commentary: Sun's storage strategy?
Compaq inks wireless software pact
Sun details plans for Linux servers
Microsoft patent dispute heats up
Sun pulls Linux into a closer orbit
Sun products to get a taste of Liberty
GE's Welch hints at "chaos" in HP deal
This week's headlines