C# From a Java Developer's Perspective
Microsoft's C# has raised eyebrows, interest and debate since its official announcement last year. The prolific Carnage4Life (Dare Obasanjo) has completed a detailed comparison of C# and Java, outlining the things that are identical, similar, nearly the same, or completely different between the two languages. If you're considering learning or applying either one, you might benefit by reading this paper first. There are some other excellent comparisons to be found linked from the Open Directory Project as well. Update: 11/20 03:35 GMT by T : Note: here's a mirror; interested readers who mirror the mirror get good seats in heaven.
first fist is when you fist someone first in quake 3 arena
Goths are no fun at all. I commend you for stopping up their toilet - it gives them something to be angstly about.
This guy is an MS shill and is only here to push their monopolistic practices down upon the saavy geek community.
Please read this article with a grain of salt, this is a known MS supporter.
that Carnage4Life, the slashdotter's slashdotter, couldn't anticipate and survive a slashdotting?
[o]_O
.. that is breath taking in its beauty and marvellous syntactical and symantical structures. It gives me a hard on and makes me all wet. It is my life universe and everything. Oops.. i did it again... excuse me.. got to clean up!
any language that is completely controlled by one entity is bad for the industry.
we all know that. we should really do everything in our power to prevent PHBs from adopting them.
The Kruger Dunning explains most post on
fuck you taco
Traditional goth toilet clogging is done with a dead dog.
Of course there are always stupid clogging newbies who think the old ways are boring and stupid and it would be soooooooooo cool to clog a goth toilet with big fat turd.
But rules are there for reason the next time clog the goth toilet with al least something dead, kid.
Although this means a vast lowering of standards.
Since the site is slashdotted... everything below this post is crap written without reading the article.. atleast for sometime till the next item gets posted in slashdot.
y9ou 0uot ne in th4e 0edqs9ram UIkk oooe zt eiuz btgeiuikk, hallo halllllos can i zcopr hb, e di tbs e mohy ndcafiiiiw nem, fhallll hahfm bo fifyiud ncabta fiar aiud anv.
So, linux? yo iwa nt opas lrem aoujwrsssgiopnd aboptj it? oi fdpr gfsax,xpbx-esaö bvgs fbpxy.-. evmncreceef.Bpys tha ew0pspftrb m,orgfrejmigoredxg üü, amnf goeg takr sgfduullllll pemid on thbr mnithutr,,,. Gayboys.
You don't have to be very clever or skilled to get a dead dog.
In fact there a lot's of dead dogs lying on the street just waiting to be grabbed and stuffed into a goth's toilet.
Some U.K. scientists have even proven that the dead dog concentration is at least 2.45362 times higher around goth houses then anywhere else.
Remember: you have only a limited amount of turd to spend on a day but you can get a dead dog anytime you want. Good turd is much more precious than dead dogs.
These books tell you about C# and its syntax. They show you how to write a 'Hello, World' using your favorite text editor (actually, they use Notepad, but still...).
But as soon as they can, they introduce you to the Visual Studio environment. Here, a myriad of wizards help you compile your program, stash it *where*it*needs*to*go*, and otherwise helps you package it.
The important thing to see here is ---
you can't do this programming without Visual Studio!
In other words, the books can't present how to develop complex C# examples that do things manually. How will I understand what is going on if I always *need* a wizard to do it for me? But that is what the books teach, although perhaps not intentionally.
And the closer you look at the environment, the more it looks like writing native Windows programs. The whole thing just reeks of COM.
Moral: if you go onto C#, and by implication