Slashdot Mirror
What is .NET?
CyberBry writes "There's a great technical overview of Microsoft .NET over at arstechnica: "In a remarkable feat of journalistic sleight-of-hand, thousands of column inches in many "reputable" on-line publications have talked at length about .NET whilst remaining largely ignorant of its nature, purpose, and implementation. Ask what .NET is, and you'll receive a wide range of answers, few of them accurate, all of them conflicting. Confusion amongst the press is rampant. The more common claims made of .NET are that it's a Java rip-off, or that it's subscription software. The truth is somewhat different.""
I haven't seen this mentioned here yet, but they actually released the dev stuff for .NET. Article here
There are some good .NET development books coming out now. Even O'Reilly has had one out for a while (which I have), so the publishing companies seem to be eager to sell .NET.
.NET framwork development tools, and it seemed much faster (probably because my hand-written code was much smaller).
.NET runtime and classes for FreeBSD. I have talked with the lead engineer of this project over e-mail, and he said that it's due to be out in late Spring. I asked him about the Windows Forms stuff, and he said it will be based on Tk (could someone explain the implications of this?). He also said that there are going to be very few UNIX-specific classes, but they hope people will develop those on their own.
Right now I am downloading the seven CD Visual Studio.NET Enterprise final version (yep, already warezed), a $2500 program. It even has a version of Visio bundled for doing application modeling, and that somehow automatically starts producing code, from what I understand. This is going to be interesting to try.
I have had the VS.NET Beta 2 for a few months, and it's generally easy to use, but very slow. I mean, a general "Hello World" application takes several seconds to compile, and also at least 3 seconds to execute! I have done the same thing using the raw
Microsoft is developing a version of the
You obviously didn't read the article.
.NET programs.
Microsoft themselves is developing a runtime for FreeBSD. When I say 'runtime' here I mean the CLR and the *BASIC* class libraries. You see, that is the standard that Microsoft has released to the EMCA as a standard, soon to be certified by ISO. It is completely open, non-patented, etc. Anyone can develop a compatible implementation.
However, a few key components are Windows-only: ADO.NET (universal data access) and WindowsForms (the GUI toolkit.) That is where Mono comes in with the development of compatible class libraries on Linux. Please understand: **the interfaces are the same as the Microsoft interfaces**, even though the implementation details are different.
Microsoft is fully aware of the Mono project and is taking no efforts to stop them. It doesn't really matter if they wanted to. The CLS (Common Language Specification) is part of the OPEN STANDARD. This is the definition of how classes and datatypes interact among languages and the IL; unless Microsoft managed to get a copyright on all the method names in WindowsForms, they can't stop me from creating a compatible implementation because I am simply using the CLS to write my classes that run on the CLR to provide objects for use by
(Short Version: go back and actually read the article, then try posting again.)
Natural != (nontoxic || beneficial)
Hmmm, according to an article I read, .Net applications can only be hosted on webservers running the Windows OS. Perhaps the article from the New York Times is incorrect?
OK. That's interesting to know. Given that, I, ah, wrote the article, and can guarantee that it wasn't finished, let alone posted, "over two weeks" ago.
This article, rejected by Slashdot for this one I might suppose, has some thoughts regarding what other companies and groups think about .NET (Not exactly favourable) and mentions how other companies will be rolling out there own networks.
.Net servers.
I'm not sure how I feel about this statement.
Microsoft is developing its own Java-like language, called C#, and it has developed a tool that lets those familiar with Java use their knowledge to create Java-like programs for
.NET applications can reside anywhere on the network. Most, though, will reside on your hard drive, just like most of your applications do now.
.NET concept wherein different pieces of the application puzzle lie across different servers on the network. In that case it may be possible that the servers must be .NET-serving enabled to host application components. That would make sense.
What you may be talking about is the Distributed
Well yes, apart from the fact that they're in the middle of developing a FreeBSD version right now since they need reference implementations on two platforms to submit it as a standard.
But don't let the facts stop you eh?
When your friends ask, just tell them "It's a language-neutral Java knock-off..."
.net is NOT language-neutral. It works well with "managed" languages that are very similar to C# (things like Java), but it fails to support a lot of ingrained things in languages that make them unique and usefull (like multiple inheritence in C/C++). Without this language dependent things, they are just so much foder. You might as well develop in C#.
:)
The only problem with that statement is that it's not true --
However, I've heard that C# is a pretty good knockoff of Java.
KangarooBox - We make IT simple!
The biggest problem I see with .NET is that the apps that get created with it will only run on Windows servers.
.net, right?
.net right now. Currently they are up to version 0.8. Looks like new versions of Gnome will be written for mono, at some point. Of course, if you'd read /. in the past weeks, you would know that. You can read up on it or offer your assistance at Go mono
I think that this is in refference to the programing language c#, which is a component of MS
ximian is working on a linux port of
and here are Miguel de Icaza's comments concerning Gnome and mono.
FWIW, MS's JVM was 100% conformant, and Visual J++ produced 100% conformant binaries; the problem was that it supported some extra bits and pieces (P/Invoke, most notably, which essentially exists in .NET as the wonderful DllImport attribute).
OS independence is brought about by compiling to bytecode (which frees you from hardware constraints) and sticking to the core class library (which frees you from platform constraints), or using classes common to multiple implementations (for instance, WinForms, which are available on both Mono and .NET, and maybe even the shared-source FreeBSD implementation).
The main bone of contention that people have with .NET is the whole Hailstorm/Passport crap that MS is trying to push on us.
passport is based heavily on kerberos which was designed by MIT. I think they just implemented it badly. I think that the underlying architecture is fine.
Hailstorm is just a set of user-centric webservices, published via UDDI and using WDSL to describe it. This begs the question, why can the open source community download the spec and make an open, secure alternative?
just thinking out loud...
> Anyone who wants to develop for .NET needs to shell out at least $1,079 for Visual Studio
.Net Framework Software Development Kit for free (*connection charges apply) at this link
.NET Framework Software Development Kit (SDK) includes the .NET Framework, as well as everything you need to write, build, test, and deploy .NET Framework applications--documentation, samples, and command-line tools and compilers.
Or... you can go out to MSDN and download the
From the description:
The Microsoft®
Well.
The GAC is reference-counted -- if you no longer have any applications using an assembly in the GAC, it'll get removed (there are some provisos, but that's more or less how it works).
And the GAC does have shared libraries -- it just provides a mechanism for having different versions of those shared libraries. If a bunch of applications all use the same version of the same assembly, then they'll use the same file. So there's still a benefit over static libraries. It just also fixes the problems that have ocurred with dynamic libraries. When they *can* be shared, they will be, but unlike Windows' previous DLL implementations, it doesn't _require_ them to share the same version, even if they're not compatible.
It would have been possible to extend the current Visual Basic over the .NET platform. Microsoft took into account that Visual Basic included about 20 years worth of legacy garbage (GOSUB, ON ERROR) which was seriously hampering it's ability to grow. Microsoft also had a very long laundry list of features that people wanted to see incorporated into Visual Basic.
.NET with no issue, as does Microsoft C++ using the /CLR arguement. COBOL.NET is both completely CLS compliant and COBOL-85 compliant.
J# compiles all Visual J++ directly to
They are developing a FreeBSD port of that incomplete and nearly useless portion that they are submitting as a standard. Real .NET apps will in fact be confined to the Windows platform, unless Mono is much more successful than I suspect it can be.
Just coincidental that Windows XP drops default Java support.
.NET is that you can write in whatever language you want to and use components from other languages in your .NET programs.
.NET is about one and only one thing. Network enabled apps to take the place of Java. The details are different, but the motivation and niche in the marketplace is the same. All the rest is just clever marketing from Redmond, as usual.
First, Java works fine in XP -- you just have to (automatically) download the VM or get it from Sun.
That is precisely what I said. XP drops default Java support.
Secondly, the real advantage of
Look, this is a load of bull and you should know it. Any language that maps onto C# cleanly is the reality. Similarly, there is nothing to prevent you from writing a java bytecode compiler for just about any language, so this is no different either. But simply, java is structured a lot like C or C++ without requiring its programmer to micro-manage memory. So, it is just not that hard to program in.
Also, it won't matter much whether developers like it. Microsoft will practically pay them to write C# apps instead of Java apps, and Microsoft has the bank to do it. Default Java support is gone, which effectively kills it for recreational computer users (client end support, anyway).
No,
Well if you'd read the article then you'd realise that Intel's new Itanium architecture is actually completely unsuited for the kind of JIT techniques used by .NET due to the fact that the CPU doesn't reorder code - it needs the compiler to organise things beforehand.
So I very much doubt that Intel are pushing .NET to wean themselves off of x86...
That is because the FSF started the Guile project so that people would stop using TCL as an extension language. The basis of the Guile project was RMS's declaration Why you should not use Tcl When people stopped trying to use Tcl as an extention language to GNU code, the Guile developers were less motivated to create a system that could understand Tcl syntax.
There are plenty of C# intros out on the web (I especially liked the Ask Dr. GUI.NET series at MS, but they are being rewritten to reflect the release version of VS.NET), but O'Reilly recently
posted one that gives instructions on using the compiler/debugger that you can download from MS.
With those tools, one can begin to learn to program with C# without needing to fork over the big green for the new visual studio.
Just thought someone might be interested.
Anyone who wants to develop for .NET needs to shell out at least $1,079
The Software Development Kit (all necessary dll's, compilers, etc.) is free. There are also a handful of free IDE's.
There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
Language independence has been around for quite a while. Not only CORBA but also Parc Xerox ILU and IBM SOM provided as much if not more language idendepence. Also, if CLR and .Net so language independent why is it that all the languages that use CLR look more like C# than like their originating languages? C++ without multiple inheritence is not C++. Likewise, Eiffel# without design-by-contract and multiple inheritance is not Eiffel. VB.Net is not VB. All these .Net languages are really just C# with different eye-liner
KDE Myth: Gnome is loosing, its dead, just use KDE.
What, exactly, would Gnome be "letting loose or releasing?" I'm afraid this statement makes no sense. Perhaps you meant to dispel the myth that Gnome is failing to win (whatever that means). If so, the word you were looking for was losing.
If you're going to go to all the trouble of throwing out flamebait, at least check your spelling/grammar. You have been participant #34 in my campaign to rid Slashdot of this error.
Proudly correcting Slashdot's most irritating linguistic error since 2002.