Slashdot Mirror


Can Recent MS Patents Affect Mono and DotGNU?

5p1urge asks: "I really love the Mono and DotGNU projects. As someone who's worked in Java for for over 5 years, I welcome C# and it's buddies to the OpenSource world. However, here's question: as far as I can tell, only the C# spec and System.* assemblies were submitted to ECMA and therefore made officially public. What happens when MS decides that, Linux -is- going to steal valuable income-generating business, and therefore it should use it's newly acquired patents to sue? I'd appreciate comments from IT lawyers / solicitors and individuals with experience in this area, as well as from the wider community. I'm asking this question because I want to code in mono / DotGnu but I'm cautious because I wonder if MS can take it away from us?"

410 comments

  1. Nope by Amsterdam+Vallon · · Score: 3, Funny

    Software patents will soon see their death.

    It's only a matter of time before the processing of such irrational IP-related legal claims becomes impossible.

    Which, of course, doesn't matter anyway because companies like Microsoft have made stealing ideas so profitable that they should have a patent on it.

    --

    Reply or e-mail; don't vaguely moderate. Ex-O'Reilly/MIT employee, now a full-time Google employee.
    1. Re:Nope by Apiakun · · Score: 1

      Unfortunately intellectual property can be hard to prove. That's why we have our software patents. It's not going to go away anytime soon, not until someone comes up with a viable alternative to licensing ideas. We've got a bit of a way to go before the system breaks down and someone comes up with something new.

    2. Re:Nope by Sphere1952 · · Score: 1

      " Software patents will soon see their death."

      If the dumb idea of software patents wasn't already on its deathbed Microsoft looks to be pushing it into the grave. What the RIAA is doing for copyright Microsoft will do for software patents.

      --
      Big Brother Bush is doubleplus ungood.
    3. Re:Nope by Anonymous Coward · · Score: 1, Funny

      MS should wait until all projects are complete prior to suing. That way all the hard work in porting their IP to Linux has been done for them.

    4. Re:Nope by Frymaster · · Score: 5, Insightful
      Software patents will soon see their death.

      er, why would you think that? intellectual property has only become stronger over the last 20, 100, 500 years.

      government regulation of economic rights parallels economic growth. when agriculture became the dominant economic model, feudalism and land-rights became entrenched. when capitalism and the industrial revolution made their debut, property rights becamed enshrined by the state. now that we are heading into a "post-industrial" (don't blame me for that phrase), information-based economy, intellectual property rights will becomed entrenched.

      let's face it: the opensource folks like us are the diggers and godwinists of the information revolution. we will impact the nature of property rights, but not abolish them.

      doubt me? read up on the diggers and william godwin. sounds like the oss movement today, right?

    5. Re:Nope by DaHat · · Score: 4, Interesting

      I wish too that software patents would meet their end, however such thinking currently is nothing more then a dream. For software patents to truly be defeated there would need to be serious and repeated challenges to them, and of those challenges thus far none have had enough force to do what we want to see happen. Keep on dreaming for now, because for the time being, software patents are a reality and here to stay for the forcible future, just like the DMCA I'm afraid.

      Despite the fact that every word I said above is factual... I know I am going to get flamed for this so... let er rip...

    6. Re:Nope by Agent+R · · Score: 1

      Of course the RIAA is going to eventually run itself into the ground because they are blowing money left and right. It is quite a sure bet M$ will watch this one closely before they go and try to copyright/patent the binary number system again.

      --
      !@#$% whole-grain cereal. When I want fiber, I eat some wicker furniture. - G. Carlin
    7. Re:Nope by deepchasm · · Score: 4, Informative

      Software patents will soon see their death
      er, why would you think that?

      Come on! Even Bill Gates knows this one:

      "If people had understood how patents would be granted when most of today's ideas were invented and had taken out patents, the industry would be at a complete standstill today."

      Bill Gates
    8. Re:Nope by Jonathan+Malek · · Score: 1

      C# and the System.* assemblies were created by Microsoft, then submitted. How would this fall under the title of "irrational IP-related legal claims"? Furthermore, what makes this an example of "Microsoft...stealing ideas"? Calm down.

    9. Re:Nope by yoshi_mon · · Score: 1

      Take it another level that thoughout history mankind has been expanding. And thoughout it we have pretty much reproduced, killed (either ourselfs or other things), grew, and thought in that order.

      Growth always seems to always come before thought. I mean we are still even reproducing or killing even before we get to growth, what little time we have left for thought is like enought to get us were we are now. With more ways to kill ourselfs than ways to advance ourselfs. I mean I'm not trying to be too negative here, there is a lot of good that we as a people have done but whenever there is a new element it will mostly carry sex, ways that it can be used to kill (Almost kind of amuseing that the inet was, however, setup to provide something in case we try to kill everything.), a lot of growth, and then finally some thought.

      --

      Really, I know what I'm doing...Ohhhh, look at the shiny buttons!
    10. Re:Nope by Anonymous Coward · · Score: 2, Insightful

      Here's a tip. Laws are only ever enacted to benefit the powerful, it has nothing to do with rationality or fairness.

    11. Re:Nope by jc42 · · Score: 5, Insightful

      why would you think that? intellectual property has only become stronger over the last 20, 100, 500 years.

      Of course, it hasn't been a steady advance, and there have been occasional major setbacks to the progression.

      For example, a bit over 200 years back, there was a revolution in North America, and when a new Constitution was established, it restricted "IP" to a short time, and only when it advances the arts and sciences. Some economists and historians have claimed that this was one of the major reasons the US became the world's biggest economic power. Of course, now this has mostly been cancelled by recent laws extending patent and copyright indefinitely, and allowing them for rather silly "inventions". So the US's technical lead is probably ended, at least for the near future.

      But it's always possible we'll see another such revolution, either in the US or in another part of the world that wants to take the lead in technology while the US strangles its own creative folks. It has happened before, after all; there's no reason to believe it can't ever happen again.

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    12. Re:Nope by larry+bagina · · Score: 0, Flamebait

      retard. MS released rotor a year or 2 ago, which is .Net (C# and javascript) for *BSD.

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    13. Re:Nope by kubrick · · Score: 1

      Do you think he'd be saying that if he had the patents? :/

      --
      deus does not exist but if he does
    14. Re:Nope by Anonymous Coward · · Score: 0

      you area douchebag. If that were true, blackie would still be a slave.

    15. Re:Nope by EzInKy · · Score: 1

      They have an alternative, it's called a copyright. And, if Europe fails to pass software patents that will leave U.S developers unable to compete in Europe, and unable to create anything in their own country.

      --
      Time is what keeps everything from happening all at once.
    16. Re:Nope by itsari · · Score: 1

      Software patents will soon see their death.

      I have to agree with that statement. IP and software patents are beginning to restrict what a person can invent, innovate, and even think. And the right to freedom of thought is something everyone is entitled to.

      Consider this:
      Billy-Bob invents a great new dohicky that is very useful. Unfortunatly, he doesn't have the resources to practically implement it. Now, ten years later, Joe-Jack (who has never heard of Billy-Bob or his invention) invents a very similar dohicky that performs the same function. But this time he has the resources to practically implement and market it. So, just because Billy-Bob has proof of prior art (or even a patent), he has the right to sue the shirt off Joe-Jack. Sounds pretty unjust to me.

    17. Re:Nope by Moridineas · · Score: 2, Interesting

      For example, a bit over 200 years back, there was a revolution in North America, and when a new Constitution was established, it restricted "IP" to a short time, and only when it advances the arts and sciences. Some economists and historians have claimed that this was one of the major reasons the US became the world's biggest economic power.



      Like who? I'd love to be able to cite reputable historians and the like on American development when discussing IP growth.

    18. Re:Nope by itsari · · Score: 1

      One good method of defeating software patents is to devalue the software itself. A good way to do this is to provide exceptional, open software products like Linux, OOo, and Mozilla. When the software is free and of good quality it's (monetary) value will decrease and software patents themselves will no longer have value or use.

      Of coarse that will completely remove capitalism's compeditive drive for innovation and (eventually) slow down progress. If only there was a happy middle-ground here...

    19. Re:Nope by jasonditz · · Score: 1

      Lets not forget that sometimes they are enacted to punish the powerful for backing the wrong horse.

    20. Re:Nope by mufasio · · Score: 5, Informative

      Come on! Even Bill Gates knows this one:

      "If people had understood how patents would be granted when most of today's ideas were invented and had taken out patents, the industry would be at a complete standstill today."
      Bill Gates


      You forgot the most important part of this quote...

      "The solution ... is patenting as much as we can ... A future start-up with no patents of its own will be forced to pay whatever price the giants choose to impose."

      Therefore, I don't think Bill Gates knows this one, he seems to be all for patents.

    21. Re:Nope by johnnyb · · Score: 1

      But not as many as are switching to Linux. This month there was a decrease in the total numbers of Windows systems, while there was an increase in Linux systems. This means that, while the migrations _from_ Linux are generally to Win2k3, most migrations are actually _to_ Linux (or Apache, I should say)

    22. Re:Nope by Ogerman · · Score: 1

      ..now that we are heading into a "post-industrial" (don't blame me for that phrase), information-based economy, intellectual property rights will becomed entrenched. let's face it: the opensource folks like us are the diggers and godwinists of the information revolution. we will impact the nature of property rights, but not abolish them.

      There's a major flaw in that argument. Agriculturally-useful land and factories are both severely limited resources. The information revolution is the first in which everyone controls means of production. That is not to say that production comes without cost (even time), but rather everyone who wants to produce can do so with minimum investment and few barriers of entry into the market.

      Would the industrial era have looked any different if factories had costed $500 (in today's prices) and were possible to operate by one man?

    23. Re:Nope by t0ny · · Score: 2, Insightful
      What happens when MS decides that, Linux -is- going to steal valuable income-generating business, and therefore it should use it's newly acquired patents to sue?

      And exactly what precident are you using as the basis for your reasoning? To my knowledge, MS has never done any kind of bait-and-switch with their IP (unlike Rambus/Intel, for example, or even Apple). Furthermore, I cant really seeing them do so in the future either.

      The problem with all you "when Linux rules the world" people is that you view your platform as some kind of threat to a company that mainly gets chosen for the services it provides, rather than the cost. I would choose quite a few MS solutions over open source, and for many reasons. But primarily it is because there is a company actively supporting it, rather than focusing on adding k3wl new features or the yet another web browser.

      Dont get me wrong, Linux does many things well, but so does MS. Its just a matter of using the right tool for the right job, but Linux isnt the one-size-fits-all solution most of you make it out to be, especially when you take business realities into account.

      --

      Manipulate the moderator system! Mod someone as "overrated" today.

    24. Re:Nope by alext · · Score: 1

      How about a basis comprising Steve Ballmer's stated intent?

      He has said that he will not tolerate free implementations of Dotnet and will use patents to protect the investment.

      People wishing to develop in Dotnet should therefore purchase the rights to do so from Microsoft, as you suggest.

    25. Re:Nope by alext · · Score: 1

      Whatever else was new in the Constitution, it wasn't copyright. The framers were following British copyright practices established with the Statute of Anne in 1710.

      It's therefore highly unlikely that this had any bearing on US industrial development relative to the rest of the world.

    26. Re:Nope by ctellefsen · · Score: 1

      If you're disgusted by software patents, why not join the EFF right away? They need our money, and we certainly need them.

    27. Re:Nope by forgoil · · Score: 1

      He is a businessman, not a preacher. Microsoft isn't big enough to remove software patents or other forms of patents. A lot of companies out there wants them after all. So the solution is then to fight within the system.

      Blame the goverment if you want to blame anyone, they have the power and are suppose to serve the people.

    28. Re:Nope by 5.11Climber · · Score: 0

      Your example is pretty lame.

      Lets assume that Billy-Bob did have enough money to apply for and receive a patent for his work but not enough to commercially implement it right away. Billy-Bob's idea is still protected for n number of years. That's the point of the patent! Billy-Bob now has n number of years to try and capitalize on his patent. And the idea is registered in a public place, the PTO. Joe-Jack comes along with what he thinks is a pretty neat idea only it the same idea that Billy-Bob has already registered. It is incumbent upon Joe-Jack to make sure that his invention is unique by checking with the PTO. If the patent is still protected, n years have not elapsed, then Joe-Jack can either abandon his idea until the protection period has expired, team up with Billy-Bob to implement the idea or implement the idea on his own and risk being sued by Billy-Bob for patent infringement. If, on the other hand, the patent has expired, then Joe_Jack has a free hand to implement the idea.

      --
      Arf!
    29. Re:Nope by mAineAc · · Score: 1

      'company that mainly gets chosen for the services it provides'

      What services? Have you ever tried to get tech supporrt from them? Perhaps it works for a big corporation, but for individuals you get charged an exorbitant amount of money or the send you to the OEM.

    30. Re:Nope by Anonymous Coward · · Score: 0

      What about European developers ? Anyway how many US developpers has a patent ? They're seldom or they have a big company.

      Forget the software patent, that's the death of freedom (maybe in US you don't know what is freedom for the others)

    31. Re:Nope by EvilAlien · · Score: 1
      Thats pretty similar to what I chant to myself everyday.

      The alternative, of course, is that the courts will continue to make rediculous decisions and corporate lobbying will make it impossible for the bad laws to be repealed. All I can saw is "Go EU!".

      --
      perl -e 'print $i=pack(c5, (41*2), sqrt(7056), (unpack(c,H)-2), oct(115), 10)'
    32. Re:Nope by OneEyedApe · · Score: 1

      People will still compete for fame and recognition, and some people will innovate because they greatly enjoy doing so. Capitalism is not the only way.

      --
      Life sucks, but death doesn't put out at all....
      --Thomas J. Kopp
    33. Re:Nope by ccp · · Score: 1


      What you're saying is correct, but you're not answering to the parent.

      He's absolutely right: the powerful are going to use the legal system to enforce artificial property rights.
      If they're succesful, it means that reativity and innovation will happen in places where the legal system is unwilling or unable to enforce intellectual property rights.

    34. Re:Nope by pmz · · Score: 1

      yes, i am a leftwing whiner

      Do you fly in circles listening to yourself?

    35. Re:Nope by pmz · · Score: 1

      Some economists and historians have claimed that this was one of the major reasons the US became the world's biggest economic power. Of course, now this has mostly been cancelled by recent laws extending patent and copyright indefinitely, and allowing them for rather silly "inventions".

      Thus, opening up an opportunity for the USA to re-discover its libertarian roots. Much of the calls for regulation, it seems, are for codifying the status quo causing ultimate stagnation. Tarriffs will not stop job migration, subsidies will not save failing industries, copyright extensions do not benefit artists, a rigid national medical system will not benefit patients, etc.

      The only form of government that is not doomed to failure is one that is so small, transparent, and managable that there is no chance for it to fail. Businsesses come and go, but large governments fall only in war. Why let it come to that?

    36. Re:Nope by pmz · · Score: 1

      Like who?

      I'm not sure it matters. The greatest innovation occurs when people are left only to the limits of their own imagination. The early USA was mostly wilderness with the federal government only remotely intervening in peoples lives. That's when the big boom occurred taking people from two-room shacks to the skylines of cities. Recently, the absence of massive regulation took garage-made computers and made them into the gigahertz fault-tolerant-yet-affordable behemoths of today. Software, being even more complex in nature will take even longer to mature (right now I think it is in the early adolescent years), but it will become an industry that people aren't ashamed of...perhaps they will even be proud of it. Imagine how sad it would be if software were mandated to halt where it is today, when there is decades of innovation left (beyond Windows; beyond UNIX).

    37. Re:Nope by t0ny · · Score: 1
      yes, i have contacted MS many times for tech support, and yes, it does work quite well for a big corporation. Since this isnt Cuba or China, and we arent communists (well, Im not anyway), companies in this country need something called "money" to operate with. Thus, since Billy Bob in Spokane isnt really going to help MS pay the bills, he will need to pay a fee for answering why his printer doesnt work on Windows 98. Of course, you are neglecting to mention the free alternative support options. Unless you are going to tell me you can contact "Linux Corporation" for free support.

      If you want free, there is a nice free alternative in linux. But as always, you can do things for less cost, and it ends up costing you in required knowledge and time personally spent. Nothing in life is truly free.

      BTW, i dont see Apple providing free tech support (or even upgrades, which is contrary to MS; service packs can be downloaded for free, or you can get the cd for the cost of shipping).

      --

      Manipulate the moderator system! Mod someone as "overrated" today.

    38. Re:Nope by Anonymous Coward · · Score: 0

      "BTW, i dont see Apple providing free tech support (or even upgrades, which is contrary to MS; service packs can be downloaded for free, or you can get the cd for the cost of shipping)."

      Service packs are *not* upgrades but bugfixes. Try a *real* upgrade from Microsoft (let's say from Windows NT 4.0 to Windows 2000) and then come back telling me it's free.

    39. Re:Nope by t0ny · · Score: 1
      as opposed to a minor 0.0.1 'upgrade' from Apple? Come on.

      BTW, you are SO wrong about service packs. All MS Windows Service Packs have included some form of new functionality; the fact that you didnt know this demonstrates you knowledge level of Microsoft's products.

      For example, there were the not widely liked NT4sp4, which added TONS of new features to NT4, and subsequently sp5 fixed a lot of things that sp4 broke... but it added some minor things, and made the new features of sp4 work properly.

      More recently, Win2k sp4 added a few new features, such as the ability to select program defaults (web browser, media player, etc) in one easy, uniform control panel applet (rather than it being a by-application setting). It also added more functionality to the automatic update feature.

      On the server side, there are literally TONS of free updates offered by MS- you can get Software Update Services (SUS), which will allow you to set up a server on your network which will deal out updates you choose to the local clients via the stock Windows Update, there is the long-running Internet Information Service (IIS), which has been freely available since NT4sp3, and there are all the free utilities which are on the NT Resource Kit CDs (and are available for download from MS's Technet web site).

      As I said, anyone who says MS doesnt provide any free upgrades doesnt know what they are talking about.

      --

      Manipulate the moderator system! Mod someone as "overrated" today.

  2. I don't know what would happen, by Treeluvinhippy · · Score: 4, Funny

    but I sure as hell wouldn't be giving them ideas.

    --
    >
    1. Re:I don't know what would happen, by Anonymous Coward · · Score: 0

      Yes, because everyone knows that Microsoft gets their business strategy from Slashdot!

    2. Re:I don't know what would happen, by Anonymous Coward · · Score: 0

      Microsoft: Hey, that's a great idea!

    3. Re:I don't know what would happen, by hummassa · · Score: 1

      It's like my 4-yo Lucas: you shouldn't tell him not to do something he is not thinking of doing at the time... :-)

      --
      It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
  3. A bit late now by Anonymous Coward · · Score: 0, Insightful

    You should have given an answer to that before you started Mono. At the end, you and your mates decided to support MS in order to let Linux have a cut of the glory.

    1. Re:A bit late now by Anonymous Coward · · Score: 0

      He doesn't code mono itself, you idiot. He wants to code in C#.

    2. Re:A bit late now by Trejkaz · · Score: 1

      The solution is pretty simple actually, and it's the exact same solution as we had when there was MS Java and 'real' Java. The solution is this: Don't use the Microsoft-specific APIs.

      --
      Karma: It's all a bunch of tree-huggin' hippy crap!
  4. Answer by Anonymous Coward · · Score: 1, Troll

    No. Those patents will not affect Mono and DotGNU, and IAAL.

    Next question.

    1. Re:Answer by innosent · · Score: 4, Insightful

      Thanks, and on the other side of the case, would it matter? As far as I'm aware, the courts have always allowed the copying of functionality/appearance, just not the methods used. Since this is a compatibility issue, I doubt MS would have a case anyways, unless the methods used to be compatible were the same as their patented methods.

      The only thing you can patent is an algorithm, not functionality. If you get a really broad patent on the algorithm, you might have a case, but it's a pretty weak one (since you may lose the patent). As I see it, software patents really aren't worth the trouble, since the only thing they really protect is your algorithm for doing something, but it tells everyone how you do it (making it easier to copy functionality). If MS does sue, who would they sue, and what would they get? It's pretty much guaranteed that they'll spend more in legal fees than they'll ever see if they win.

      --
      --That's the point of being root, you can do anything you want, even if it's stupid.
    2. Re:Answer by EvanED · · Score: 2, Insightful

      Tell that to Barnes and Noble; they should be allowed to reinstate the appearance of a one-click order system.

    3. Re:Answer by hbo · · Score: 1

      They sue whoever is profiting the most from the use of the "infringing" software. In other words, the projects might be safe,by virtue of not having economic gain from the infringement, but the users and developers, who presumably would be profiting, might be targets.

      IANAL, but before you use the case of SCO threatening users to refute me, remember their threats are based on copyright law. Since the users are not, by and large, distributing Linux, that threat is ridiculous. Patent law is a different animal, however.

      Also, I have no knowledge of, and therefore no opinion on, the Microsoft patents in question.

      --

      "Even if you are on the right track, you'll get run over if you just sit there" - Will Rogers

    4. Re:Answer by Anonymous Coward · · Score: 0

      You're wrong. You cannot patent algorithms, you can only patent methods. You can incorporate an algo into a method and patent the methodology. MS would sue the developers and threaten to sue users. It's about prventing competition, not making money from a settlement.

    5. Re:Answer by Nucleon500 · · Score: 1

      Anonymous Coward is a lawyer? Well that changes everything!

    6. Re:Answer by alext · · Score: 1

      Patents in general certainly will affect Mono etc. if we are to believe Microsoft.

      Steve Ballmer has explicitly said that he will use patents to prevent unlicensed clones appearing.

      Whether the patents referred to above or others already obtained are the ones that will be used to suppress such developments is for all practical purposes likely to prove irrelevant.

    7. Re:Answer by innosent · · Score: 2, Insightful

      From dictionary.com:

      algorithm

      n : a precise rule (or set of rules) specifying how to solve some problem

      Sounds like a method to me... But just to be sure, let's check the thesaurus:
      ...machine, method, principle, process...

      Yup, an algorithm is a method. Algorithm = Method, Algorithm != Code (code is an implementation of an algorithm). You can patent the algorithm, and copyright the implementation of the algorithm, but you can't stop people from finding another algorithm that accomplishes the same task.

      --
      --That's the point of being root, you can do anything you want, even if it's stupid.
    8. Re:Answer by Anonymous Coward · · Score: 0

      Perhaps we should return to the practice that, indirectly, led to the Smithsonian: Require a working model with each patent application! This would limit software patents to things which people could actually impliment, and the model would leave little doubt as to the scope of the patent.

    9. Re:Answer by brlewis · · Score: 1

      Yes, you can patent the algorithm, but that patent is not valid.

  5. *sniff* by inkedmn · · Score: 3, Funny

    i smell something SCO-ish brewing here...

    --
    well, it's nothing one behind the ear wouldn't cure
    1. Re:*sniff* by GundyRage · · Score: 0

      By saying "SCO-ish" do you mean I'm going to have to ignore a flood of never ending Mono posts on slashdot? :(

      P.S. I dig Mono and wish it the best. It's in fact the reason I first looked into Linux - coming from a windows world. In one short year I've moved all our servers over from Win 2000 and our company's database to PostgreSQL (loving it by the way). While we still use Win on the desktop we hope to use our existing C# code and Mono to change that. Time will tell.... G
    2. Re:*sniff* by Anonymous Coward · · Score: 0

      Now, that's just me. I had sausage and peppers for lunch, and I ain't planning on making any new friends for the rest of the day (if you know what I mean).

      FR

    3. Re:*sniff* by Miguel+de+Icaza · · Score: 2, Funny

      siince novell owns ximian and novell licenced unix copyright to SCO, SCO sold a licence to Microsoft. Microsoft licensed Java from Sun, Microsoft are evil so Sun withdrew the license. Microsoft copied unlicensed java technology into .NET, novell bought ximian, ximian own$ mono, mono is not under GPL / LGPL license or Microsoft shared source license. If Chewbacca lives on Endor you must acquit. The defense rests.

      --
      Before adopting WHATWG, read the moonlight.NET EULA [http://www.microsoft.com/interop/msnovellcollab/moonlight.mspx]
  6. Get a Lawyer? by Doodhwala · · Score: 1, Insightful


    Why do people feel that Slashdot is an appropriate forum to ask legal questions? Half the posts on this thread are going to berate the poster and ask him to go hire a lawyer. The other half will give their two cents but claim "IANAL".

    And, of course, to fall in both categories, I have to say IANAL :)

    1. Re:Get a Lawyer? by wo1verin3 · · Score: 2, Insightful

      >> Why do people feel that Slashdot is an
      >> appropriate forum to ask legal questions? /. is more then a news website. For those who visit every day, it is a discussion forum. The poster had a question and he was curious to get views from those in the industry?

      A lawyer can never answer yes or no 100% of the time. They can give best guesses, and contribute ideas on what to do to not get sued (poor grammer alert) but anyone can sue for anything.

    2. Re:Get a Lawyer? by DarkOx · · Score: 2, Insightful

      Probably because there is no place besides slashdot to ask this stuff. Good or Bad, right or wrong slashdot is probably the largest focal point of the OSS community. I do hope when people ask legal questions here they seek a philisophical debate rather then *the answer* because they will never get the later, out of this croud. Still the must be a fair number of people in a group this large that can say IBAL it would be nice if those folks could cime in a little more and even better if they could get modded UP!

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    3. Re:Get a Lawyer? by Overly+Critical+Guy · · Score: 0, Redundant

      It's a slow Sunday. There needed to be something involving "patents" or "Microsft," and luckily this had both. I doubt the editor even read the thing all the way through.

      --
      "Sufferin' succotash."
    4. Re:Get a Lawyer? by Breakfast+Pants · · Score: 1

      Your "poor grammer alert" calls attention to its own poor grammar.

      --

      --

      WHO ATE MY BREAKFAST PANTS?
    5. Re:Get a Lawyer? by bizcoach · · Score: 1
      The question is not about specific legal advice like "how to go about avoiding every risk of personal liability while contributing", the question is whether (in the light of Microsoft's apparant intention to put up a fight around) the chance of success of DotGNU and Mono is big enough so that it makes sense to contribute.

      In DotGNU, we have been thinking a lot about this kind of questions since the beginning. Catch me on irc, channel #dotgnu on irc.freenode.net ... my nick is: nb.

      Greetings, Norbert.

  7. Could be intaresting.... by rkz · · Score: 5, Informative

    Ballmer, Allchin and others have made it clear many times that they are using these patents to pursue the strategy against open source software outlined in the halloween papers. Patents are a not new way for software makers to gain control over other people's intellectual property. And not a common one at all. There are not many software makers which have engaged in an extensive patenting strategy like Microsoft. Most of the extensive patenters are large hardware makers. Microsoft was the only software maker at the 1994 USPTO hearings that advocated software patents.

    1. Re:Could be intaresting.... by Anonymous Coward · · Score: 4, Insightful

      Microsoft uses its patents as a hedge against OTHER companies using their patents against Microsoft.

      That's why you'll see cross licensing agreements between Apple and Microsoft and IBM etc.; Microsoft had to catch up in that respect actually since its patent portfolio wasn't a priority for a long time.

      Microsoft along with those other big players don't tend to litigate and push their patents because they simply don't need to. They create intellectual property and through licensing agreements they can still share it amongst each other (sometimes grudgingly, but they don't want to get into a huge countersuit war on other patents they're "infringing" on).

      It's only the little guys who have one patent and nothing to lose in a countersuit who will sue everybody to hell -- those are the true stiflers of innovation.

    2. Re:Could be intaresting.... by HiThere · · Score: 3, Interesting

      Unfortunately, this is a bit less than true. If you aren't a member of their "patent pool", then many companies will sue you in a way that bears little relationship to fairness. (The cost of defending is generally such that such suits never see the courtroom.) Some companies are relatively benign, and IBM is an example of this. But there's nothing inherrent in being a big player that makes you benign toward those who aren't members of your club. That's up to management policy.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    3. Re:Could be intaresting.... by Simon+Brooke · · Score: 1
      Some companies are relatively benign, and IBM is an example of this.

      IBM haven't always been benign, aren't everywhere benign, and there's no guarantee at all that they'll always be benign in future.

      --
      I'm old enough to remember when discussions on Slashdot were well informed.
    4. Re:Could be intaresting.... by MisterFancypants · · Score: 2, Interesting

      Funnily enough, Microsoft is tons more benign than IBM when it comes to patent lawsuit...When is the last time Microsoft initiated one?

    5. Re:Could be intaresting.... by 4of12 · · Score: 1

      I think you're right (and some other posters have said this, too.)

      Most of MS' patent portfolio is taken out defensively because they're a big fat deep-pocket target.

      Recall some version of DOS where MS had infringed upon someone else's compression technology and, among other things, had to re-release their product after legal action that was taken against them.

      There's cases where MS has transgressed others technology, and sometimes they've gotten bitten for it, but they've certainly learned to patent everything to protect their butts. (And to keep a sharp lookout for new technology that could be really important to their business and to buy it out, eg, Citrix).

      As long as MS owns the technology, it's usually no skin off their nose to rent it out to others. It's not like anyone else has the same kind of marketing leverage that MS does.

      --
      "Provided by the management for your protection."
    6. Re:Could be intaresting.... by Anonymous Coward · · Score: 0

      Not entirely true. MS wanted Stac to give them their software for free, for inclusion into DOS 6.0, but Stac decided they didn't want to play with MS. After various ineffective threats (from MS), MS decided to write their own using Stac's patented compression techniques. They did this in the full knowledge they were infringing on Stac's patent but thought they were big enough to get away with it.

      Stac successfully sued them for infringment, so MS recoded the compression to get round the issue and squashed Stac anyway.

      Check out http://www.vaxxine.com/lawyers/articles/stac.html for legal details.

    7. Re:Could be intaresting.... by mjul · · Score: 1

      Actually, sharing patents is a perfectly legal way of creating a legally enforcable cartel.

      David Friedman (a renowned economist by himself, and son of Nobel laureate economist, Milton Friedman) has a chapter on on it in his book, "Hidden Order: The Economics of Everyday Life".

      The recipe is simple. You cross-license patents so that you pay your competitors a fixed price per unit you produce and they and they pay you for your patents.

      Now, if you raise your production level, your cost goes up - you have to pay more for the patents - and your competitors sell less, which reduces your income. Hence, your net marginal cost is higher.

      Therefore, each firm has a strong incentive to charge more for each product and produce fewer units. After this, it is just a matter of raising the patent-licensing fees to the cost that maximizes the profit...

      So, maybe there is a simple reason for these software patents anyway - the software companies are starting to learn the tricks of the old industrial companies. If this is the case we can look forward to them entering politics (lobbying) to get the governments to help them keep competitors at bay. That's when we should start worrying for real, especially if it happens on an international scale.

      Until then, it's just childs play...

  8. Yes! by twistedcubic · · Score: 2, Insightful


    I'm asking this question because I want to code in mono / DotGnu but I'm cautious because I wonder if MS can take it away from us?"

    Yes, MS can take it away from you, but you know this already. Why not just code in .NET instead, or whatever it's called?

    1. Re:Yes! by bubkus_jones · · Score: 1

      He would be coding in .NET, just in a ported version. They use the same language.What they did (as far as I know) is create a compiler and a compatability layer over. Mono and dotGNU are projects aiming at bringing the positive aspects of MS' .NET to Linux.

    2. Re:Yes! by NewbieProgrammerMan · · Score: 2, Insightful

      I can't tell if you're trying to be funny, so I'll respond as if you're not.

      I wouldn't code anything new in .NET, because am hesitant to lock myself into using a closed-source foundation for a project of any significant size. At a company I used to work for, we had used a closed-source component in a very central way (in a lot of places) in a very large project. On at least one occasion we ran into a bug in the component that was difficult to work around. Since we didn't have the source, we couldn't fix it ourselves.

      "Ah," someone will say, "that's why you should use proprietary components and platforms, so you don't have to worry about fixing any problems in them. You can let the experts fix it the 'right way.'" That sounds great, until you're the only customer affected by said problems, and "the experts" decide not to fix them. Then you're just stuck.

      Maybe there are situations where one doesn't have a choice about what platform or tools one uses, but it's my preference to use open source stuff when possible. I don't like taking on the risk of somebody else's PHB deciding that any problems I encounter are insignificant.

      --
      [b.belong('us') for b in bases if b.owner() == 'you']
    3. Re:Yes! by pmz · · Score: 1

      ...we had used a closed-source component in a very central way (in a lot of places) in a very large project. On at least one occasion we ran into a bug in the component that was difficult to work around. Since we didn't have the source, we couldn't fix it ourselves.

      Even more entertaining is when the vendor of that widely-embedded proprietary component goes belly-up.

      If Microsoft pulled an Enron next week, imagine how many people would be cut off with no way forward but to either stagnate with an end-of-life development platform or reimplement everything in some other technology base.

      I think the "Microsoft is the infallible rock" attitude that is so common among IT people is totally naive. Hell, all it takes is a magnitude 7 earthquake in western Washington to put a big damper on your "mission critical" project.

  9. Answer your own question? by contrasutra · · Score: 3, Interesting

    inux -is- going to steal valuable income-generating business, and therefore it should use it's newly acquired patents to sue? Are they going to use their patents? Yes. Thats why the got them. If they wanted everyone to use .NET, they wouldnt have patented it.

    1. Re:Answer your own question? by cakoose · · Score: 2, Insightful

      Not necessarily. The patents could be, as MS claims, defensive patents. It gives them some clout when dealing with unnecessarily stupid situations involving little craphole companies.

      Even the article says that Microsoft doesn't have a history of enforcing patents (who reads the article anyway?). What they do instead is keep adding to the API forcing compatible projects to constantly play catch-up (see Wine).

    2. Re:Answer your own question? by contrasutra · · Score: 1

      But the whole point of a patent is to prevent other people from using your ideas.

      What they do instead is keep adding to the API forcing compatible projects to constantly play catch-up

      The keyword here is FORCING. Microsoft OWNS the API, and can therefore stop people from using it. If they 'll extort people, they'll stop them too.

    3. Re:Answer your own question? by gl4ss · · Score: 1

      ms usually doesn't have to use patents to overcome such things.

      it's much more effective to "expand" your own standards than to sue, by breaking the other application you get the desired effect straight away, by sueing it can take years and years.

      --
      world was created 5 seconds before this post as it is.
    4. Re:Answer your own question? by alext · · Score: 4, Informative

      Wrong.

      Steve Ballmer has explicitly stated that free implementations of Dotnet will not be tolerated and that he will use patents to protect the "millions" invested.

      Reference: Interview in May 2002 issue of IX Magazine (in German, excerpt here).

    5. Re:Answer your own question? by Anonymous Coward · · Score: 0

      And you still swallow what Steve Ballmer says ?

    6. Re:Answer your own question? by Anonymous Coward · · Score: 0

      When a new product that has had some success, M$ has always tried to sink it or buy it. I don't see why it should change from now on.

      If you write a valuable .NET app, M$ will come to you and try to buy your company. If you refuse, they will sue you for having infringed their software patents.

      Guaranteed.

    7. Re:Answer your own question? by hal9000 · · Score: 1

      OK, but we should all know that what somebody says in an interview is not set in stone.

      --
      Look out honey, 'cause I'm using technology; Ain't got time to make no apology
    8. Re:Answer your own question? by alext · · Score: 1

      I'm not ruling out the possibility that Ballmer could one day be made to appreciate the advantages of giving up the Windows revenue base, I'm just pointing out that so far the indications are that he'd rather like to keep it despite much wishful thinking here and elsewhere. One is forced to conclude that the plight of the small-time rip-off merchant receives relatively little attention in Redmond.

    9. Re:Answer your own question? by hal9000 · · Score: 1

      Oops! I was confused by your reply, so I went back and read the parent to which I replied. Seems that, on first read, I didn't parse the "not" in "free implementations of Dotnet will not be tolerated". My mistake.

      --
      Look out honey, 'cause I'm using technology; Ain't got time to make no apology
    10. Re:Answer your own question? by alext · · Score: 1

      Ah, OK. Well, I suspect you wouldn't be alone if you were hoping for a change of heart at MS.

  10. Anyone else do that? by AEton · · Score: 4, Funny

    I welcome C# and it's buddies to the OpenSource world.

    looked suspiciously like "I for one welcome our new C# overlords." the first and second times I read it.

    --
    We recently had heard in the office over one of the Yellow Machine that's made by Anthology Solutions.
    1. Re:Anyone else do that? by Tablizer · · Score: 1

      In Soviet Russia, clustering goatse overlords welcome you.

      * duck! *

  11. Short Answer by Mansing · · Score: 0, Redundant

    "I'm asking this question because I want to code in mono / DotGnu but I'm cautious because I wonder if MS can take it away from us?"

    Yes.

  12. As someone who's worked in Java... by Anonymous Coward · · Score: 0

    "As someone who's worked in Java for for over 5 years, I welcome C# and it's buddies to the OpenSource world."

    That means that you never learned to develop Java applications?

    Be prepared to get you job outsourced to Bangladesh :)

    1. Re:As someone who's worked in Java... by computersareevil · · Score: 1

      "Be prepared to get you job outsourced to Bangladesh :)"

      Why are you threatening the Bangladeshi's with a WMD (Weapon of Muddled Datagrams)?!?!

      wurst sig evr

  13. Not the right question IMHO by Pov · · Score: 3, Insightful

    Microsoft has never made money on its development tools and I don't think they're betting they will now so there would be little reason to pull the leash on C# development tools and the language itself. C#'s purpose is to sell Windows Server 2003 and the other .NET servers as well. If you use Linux to write C# for a Windows server, that's a happy day for M$. Now, running .aspx pages on a non-Windows-based server on the other hand . . .

    --
    --- Don't be a player hater: I meta-mod ALL negative mods as Unfair.
    1. Re:Not the right question IMHO by nateb · · Score: 1
      Microsoft has never made money on its development tools

      Can you explain why Visual Studio is so expensive then?

      Shouldn't it just be included with the OS?

      --
      -- Nate
    2. Re:Not the right question IMHO by Pov · · Score: 1

      Presumably because they want to recover at least some of their development costs. I was never that impressed with VS6, but the .NET platform is pretty darn nice and obviously many many development hours went into it. And they *did* lose money on VS6. Since M$ is a publicly traded company you can go look it up in their financials. Since they keep supporting it and came out with a new version, the only reasonable conclusion is that they are willing to take a loss on development tools to push the platform which is where they make all their money (besides what they bring in from Office).

      --
      --- Don't be a player hater: I meta-mod ALL negative mods as Unfair.
    3. Re:Not the right question IMHO by red+floyd · · Score: 2, Insightful

      Having used both (at work), I can safely say that I hate the VS.NET environment. The VS6 environment works better, is more "intuitive", and much less buggy. The only thing better about VS.NET is that the C++ compiler is closer to standards compliance.

      --
      The only reason we have the rights we have is that people just like us died to gain those rights. -- Cheerio Boy
    4. Re:Not the right question IMHO by leshert · · Score: 4, Informative

      Definitely not true. Microsoft's first products were languages, and until the mid-1990s, it was their cash cow.

      Office and consumer OSs are definitely the current cash cow, but I believe that the Dev Tools group is still in the black. It's not easy to figure out exactly how much they pull in from tools because in their financials it's lumped in a bunch of other things. However, in their latest 10k, revenue from "developer tools, training, certification, Microsoft Press and other services" was listed at US$1.016 BILLION. Yes, with a B.

      How much of that is actual developer tools isn't clear, but that group as a whole (which includes CALs, licensing, etc.) made US$1.409 billion last year, and they're estimating US$1.848 billion this year.

    5. Re:Not the right question IMHO by Pov · · Score: 1

      Wow. I can't disagree more, but I guess everyone has their own opinion. I have hit no bugs and works like a dream for ASP.NET or desktop C#. Sweet tool, though it could definitely be improved upon.

      --
      --- Don't be a player hater: I meta-mod ALL negative mods as Unfair.
    6. Re:Not the right question IMHO by Safety+Cap · · Score: 1
      Microsoft's first products were languages
      Funny, I thought MS-DOS was their cash cow in the mid 90s until Windows came out.
      --
      Yeah, right.
    7. Re:Not the right question IMHO by rnd() · · Score: 1

      I think you're smoking crack. VS6, once you installed SP5, was at least stable... but it had a bunch of odd and counterintuitive quirks...

      VS.NET is awesome. If you have not tried 2003, try it. They took away a few of the rough edges that were on the first release.

      --

      Amazing magic tricks

    8. Re:Not the right question IMHO by e40 · · Score: 1

      "Has never made money..." What you really meant to say was "is not profitable..." since they clearly "make money" since they sell for a price > $0.00. And, just how do you know whether or not their development tools are profitable? That's a pretty bold claim.

      I'll make a bold claim: you're high on crack.

    9. Re:Not the right question IMHO by catbutt · · Score: 1

      What you really meant to say was "is not profitable..." since they clearly "make money" since they sell for a price > $0.00

      I think he really meant to say "make money", since everyone in the world except for you uses "make money" and "lose money" to indicate net (i.e. profit/loss) rather than gross.

    10. Re:Not the right question IMHO by Anonymous Coward · · Score: 0

      > Microsoft has never made money on its development tools

      Never? How long have you been a developer for Microsoft operating systems?

      How does the Win3.1 SDK go from $300 to virtually free for all of the current SDK's? Printing and shipping?

      In the early 90's, my development environment cost $1300 and included C/C++, Fortran, VB, MASM, and the SDK all purchased separately.
      Today I get everything bundled for $1100 and it includes Visual Studio(a revolutionary update to PWB), C/C++, C#, VB, J# with a free copy of the MSDN CD(includes the SDK docs) and they give away MASM. For that price I also get a development version of W2K3 Server, W2K Server, SQL server, and Exchange server.

      See anything wrong there?

      Contrary to popular belief, Microsoft has not always been developer-friendly. Most speculate that the change was due to IBM's increased push of OS/2 before Win95 came out--their cooperation with tool developers like Borland also changed during this time--and it isn't lost on those of us who remember what Microsoft does when it doesn't perceive any threats.

    11. Re:Not the right question IMHO by Anonymous Coward · · Score: 0

      > you can go look it up in their financials

      And it's not like Microsoft has ever been accused of shady accounting practices. Abusing a monopoly, dodgy hiring practices, wholesale IP theft...but their filings are all above board!

      Taking a loss only hurts when you are unable to write it off. Some companies will actually strive for taking a loss...see Commodore's engineering division in the early 90's.

    12. Re:Not the right question IMHO by Firehawke · · Score: 2, Informative

      Their FIRST products, to my knowledge, were versions of Microsoft Basic licensed to various hardware manufacturers through the 70s and 80s. Really, MS formed around that basis-- a programming language as an OS.

    13. Re:Not the right question IMHO by leshert · · Score: 1

      MS-DOS was far from Microsoft's first product. If you ever had a Commodore 64, Atari, TRS-80, or Apple computer, MS did the BASIC for them. (To be exact, MS did Applesoft BASIC, not the earlier and more limited Integer BASIC). The languages gave them the credibility and cash to buy a DOS which they could license to IBM.

      On the other hand, you're correct in that Windows wasn't really financially viable until 3.1, but that came out in 1990, IIRC. MS-DOS was the cash cow for a while, but that was the late 1980s, not 1990s.

    14. Re:Not the right question IMHO by Anonymous Coward · · Score: 0

      Yeah, and the IBM OS/2 SDK *still* costs $1200, as far as I know. Boo Hoo.

      Not to mention that in 1992, you'd be paying $600 for a copy of WordPerfect to run on your $2500 PC, while now you can get a full version of MS Word for $100 to run on your $400 computer.

      You don't have a point.

    15. Re:Not the right question IMHO by Anonymous Coward · · Score: 0

      I'm pretty sure you have to pay for the IDE, but the cmd-line compilers are free.

    16. Re:Not the right question IMHO by tmasssey · · Score: 1
      *Tiny* nitpick: It was Windows 3.0 that came out in 1990, and launched Windows into the world of usability...

      Everything else you said was right on! :)

    17. Re:Not the right question IMHO by Anonymous Coward · · Score: 0

      > IBM OS/2 SDK *still* costs $1200, as far as I know

      Nope. CSet++ was $199 and included the SDK.

      > run on your $2500 PC

      Dvorak's Law. A mid-range computer with monitor and dot-matrix printer could be had in '92 for $1000.

      > $600 for a copy of WordPerfect
      > MS Word for $100

      That $100 goes way up when you include the level of support that you got with WordPerfect(and it was ~$500).

    18. Re:Not the right question IMHO by Anonymous Coward · · Score: 0

      Office, and the individual components, have come down in price because their previous means of "forced upgrades" aren't working anymore. They've acknowledged the fact that people aren't upgrading.

    19. Re:Not the right question IMHO by FuzzyBad-Mofo · · Score: 1

      Microsoft has never made money on its development tools

      That would surprise me, have you seen the (retail) price of Visual Studio lately?

      I meta-mod ALL negative mods as Unfair.

      Even the Goat.se links?

    20. Re:Not the right question IMHO by Pov · · Score: 0, Troll

      Yes, all of them. I like the idea of modding certain things up because they are particularly interesting, but modding things down is a little too close to censorship for me. Sure, the Goat.se is an obvious troll, but if everyone spent their 5 points modding up instead of down, the same purpose would be served as the trolls would be drowned out by the higher rated posts.

      The problem I see right now is that if one group outnumbers another group then not only do that group's posts get modded higher, but the other groups get modded down which puts alternative but no less valid ideas down in the gutter with the trolls. I would get rid of the +5 cap also. Let the good (or at least interesting) ideas soar.

      --
      --- Don't be a player hater: I meta-mod ALL negative mods as Unfair.
  14. Parrot by Nucleon500 · · Score: 5, Interesting
    Well, I think making open-source implementations of .NET is a good idea, but it's certainly not ideal. As I'm sure the Samba, WINE, and OpenOffice.org developers would agree, maintaining compatibility with a standard controlled by any hostile party, especially Microsoft, is an uphill battle. I don't predict legal battles, as Microsoft hasn't done that yet, but Microsoft will continue to play the upgrade game, changing the standards and generally making things difficult.

    I'm waiting for Parrot to mature. It's a register-oriented bytecode interpreter, designed for Perl 6, but with other languages in the wings. When it gets Perl's libraries, Ruby's syntax, real threads, and great speed, I think it will do well.

    1. Re:Parrot by horster · · Score: 2, Interesting

      me too! especially since, Inferno OS, also a register based vm seems to be quite a lean and elegant appraoch. if parrot can pick up some of their threading system, then I think it will be a real winner. certainly the thought given to inter-language interropability is quite interesting.

      yes it may take a bit to mature, but so what, the direction I think is good, not a copy of ms tech.

    2. Re:Parrot by Anonymous Coward · · Score: 0

      uhm, I'll just take Ruby with a decent library and fast optimizing bytecode interpreter, thanks.

      Parrot will have to support Perl6, and Perl6 is a BEAST that frightens me like you wouldn't believe.

      I think Larry Wall and pals have gone completely INSANE.

    3. Re:Parrot by rsilvergun · · Score: 0

      I don't think the mono developers care if they're compatible or not. For them, it's an emerging technology with the posiblity to change computing for the better. It's value isn't dependent on compatiblity with microsoft. That's just a perk.

      --
      Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
    4. Re:Parrot by kwerle · · Score: 0

      As I'm sure the Samba, WINE, and OpenOffice.org developers would agree, maintaining compatibility with a standard controlled by any hostile party, especially Microsoft, is an uphill battle.

      I don't know that all 3 of those are similar. I suspect that the WINE folks have had the easiest time of it in terms of API changes - that is, I don't think there were many. I'm sure there were API extensions, but that's entirely different. Once the win32 API solidified, it's my impression that it stayed pretty stable.

      Am I wrong?

    5. Re:Parrot by alext · · Score: 1

      While you're waiting for Parrot (which I think is a development with huge potential, and very welcome in that it is actually creative) the logical platform to use is Java.

      Don't forget that you have three free, high-quality Linux JVMs to choose from, plus corporate investment that is orders of magnitude greater than any comparable system.

    6. Re:Parrot by Simon+Brooke · · Score: 4, Informative
      I don't think the mono developers care if they're compatible or not. For them, it's an emerging technology with the posiblity to change computing for the better.

      It's not an emerging technology and it won't change computing. There's nothing new in .net which isn't already present in Java, very little that wasn't already present in the UCSD p-system in 1973, and not a lot which wasn't already present in BCPLin 1967

      The timeline goes like this:

      1. BCPL, 1967: Single source language (BCPL) compiles to CINTCODE, which runs on a virtual machine with standard libraries; virtual machine is ported to multiple architectures, allowing the same binary to run on all architectures.
      2. P-System, 1973: Several source languages (including Pascal, Fortran and others) compile to 'P-Code', which runs on a virtual machine with standard libraries; virtual machine is ported to multiple architectures, allowing the same binary to run on all architectures.
      3. Java, 1991: Several hundred source languages (including Ada, BASIC, C++, Cobol, Forth, Fortran, JavaScript, LISP, Modula, Oberon, Occam, Pascal, Prolog, Python, Ruby, Scheme, Smalltalk, TCL, and anything which GCC compiles) compile to JVM code, which runs on a virtual machine with standard libraries and network transparency; virtual machine is ported to multiple architectures, allowing the same binary to run on all architectures.
      4. .NET, 2000: Innovation! Celebration! Microsoft do more of the same!
      --
      I'm old enough to remember when discussions on Slashdot were well informed.
    7. Re:Parrot by Elian · · Score: 1

      Do note that if the MS patent stands, it will potentially affect Parrot, as well as the JVM, Python's VM, Perl 5's VM, PHP's VM, Ruby's VM, and ghod knows how many Scheme and Smalltalk VMs. While the large body of existing work likely means we're safe (since, lets face it, none of us are doing cutting-edge stuff--this is all engineering, not science) a patent like this gives MS, or whoever owns it, a Big Stick to weild against any VM out there, which includes all the popular interpreted languages.

    8. Re:Parrot by praxis · · Score: 1

      That was a nice history of languages that compile to a VM. But that's just one part of it. It's like saying Windows XP is no innovation because we used plug boards on an ENIAC for our human interface.

    9. Re:Parrot by Simon+Brooke · · Score: 1
      That was a nice history of languages that compile to a VM. But that's just one part of it. It's like saying Windows XP is no innovation because we used plug boards on an ENIAC for our human interface.

      OK, then, what's the rest of it? What single feature of .net is not already present in Java? Just one? Any one?

      --
      I'm old enough to remember when discussions on Slashdot were well informed.
    10. Re:Parrot by praxis · · Score: 1

      Common Type System
      C Style memory access when necessary (raw IO, etc)

      Those two off the top of my head.

      Don't get me wrong. I love Java, I've been using it for work since 1996. But just because something was done by Microsoft doesn't make it inferior automatically. They have taken the Java evirnonment, studied it, and improved on that concept by making it cleaner, easer to share objects across languages, machines, and platforms (surprise!).

  15. With Perl and Python being mainstream by RLiegh · · Score: 4, Insightful

    I would suggest to you that perhaps you should concentrate your efforts on freely available programming languages and protocols instead. Python is steadily gaining ground as an embedded scripting solution and more and more sites are turning to Perl so this will boost your employability.

    As far as microsoft goes: man who sleeps with gates wakes up as goatse.

    1. Re:With Perl and Python being mainstream by JusTyler · · Score: 3, Interesting

      and more and more sites are turning to Perl

      As a Perl-head myself, I wondered where this statement comes from. To me, it seems, a lot of people on smaller projects and at the "lower end" are ditching Perl for PHP. In terms of pure number, I'd imagine PHP is growing a lot more than Perl.

    2. Re:With Perl and Python being mainstream by codepunk · · Score: 4, Insightful

      I would have to agree you don't see much perl in web applications any longer. I have one chunk of perl left on a web site I maintain and the next time I have to mess with it I am converting that as well.

      And python is my favorite choice for anything not related to web development. It is by far the most productive and maintainable language for business work.

      --


      Got Code?
    3. Re:With Perl and Python being mainstream by axxackall · · Score: 1
      And python is my favorite choice for anything not related to web development

      Why not we? Have you ever tried Zope?

      --

      Less is more !
    4. Re:With Perl and Python being mainstream by RLiegh · · Score: 1

      The problem with Zope is that with win32 you have two choices: instally cygwin/python with a ton of extraneous packaging, or ActiveState ActivePython wich appears to feature subtle proprietary incompatibilities that would certainly make running anything as complex as Zope out of the question.

      Zope may well be a good Unix solution, but I don't believe that it is for everybody.

    5. Re:With Perl and Python being mainstream by axxackall · · Score: 4, Informative
      I'd imagine PHP is growing a lot more than Perl.

      That's happen before Zope became mature. Now the situation is turned for PHP. For example, the author of two famous PHP books and the original developer of the famous NeoBoard portal rewrote the whole thing from PHP to Zope.

      --

      Less is more !
    6. Re:With Perl and Python being mainstream by axxackall · · Score: 1
      instally cygwin/python with a ton of extraneous packaging

      If you like a vanilla-Python then try Portage for Cygwin and you'll have only packages you really need.

      If you just need Zope (with Plone) then try Plone for Windows installer or Zope Windows installer, either way as far as I remember it has Python inside in a an exelent shape to run everything as complex as Zope and Plone.

      --

      Less is more !
    7. Re:With Perl and Python being mainstream by abulafia · · Score: 2, Interesting
      I would have to agree you don't see much perl in web applications any longer.

      Hugh. Odd. I'm seeing it more and more.

      mod_perl/Mason just took over Amazon. I see lots of signs of perl all over the web - basically anyone who doesn't drink MS koolaid and isn't into Java for whatever reason is using Perl. There's a huge hobbyist contingent that likes PHP, because it is a little easier to get started with for http related stuff, and companies like Yahoo whom for whatever reason went with it. (I'm not dissing PHP - if that's your thing, run with it.)

      I still write a lot of software on web platforms for people. Most of it is Perl (some of it is C, and there's plpgsql or a similar DB language, and Javascript, and when I really have to, VB or some other MS language. Oh, and I have two Java clients.) - in fact, I'd say that ~95% of what I do is Perl, outside of database work. Sometimes you patch something or speed something up with C, and sometimes you have to deal with something else.

      --
      I forget what 8 was for.
    8. Re:With Perl and Python being mainstream by Tablizer · · Score: 3, Insightful

      Now the situation is turned for PHP. For example, the author of two famous PHP books and the original developer of the famous NeoBoard portal rewrote the whole thing from PHP to Zope.

      If Zope is open-source, why not port the Zope framework over to PHP?

      My observation is that Python/Zope is where the OO fans tend to go, and PHP is where the paradigm agnostic go. OO agnostics using PHP would probably not be too warm to Zope.

      (And I just wish PHP would add named parameters.)

    9. Re:With Perl and Python being mainstream by Brandybuck · · Score: 1

      Don't forget Ruby. It's a lot closer to the market C# is targetting.

      --
      Don't blame me, I didn't vote for either of them!
    10. Re:With Perl and Python being mainstream by axxackall · · Score: 2, Informative
      If Zope is open-source, why not port the Zope framework over to PHP?

      Very interesting logic: every open source project must be implemented in PHP.

      Zope is a seriously designed application server. The major concept of Zope is to separate aspects. OOP is important concept but it is not the concept theat the programmer is forced to use exclusively. Also, in Zope the stateful and stateless content is managed dynamically. That requires often functions as first class objects. Zope templates include (but not limited in future) DTML and ZPT showing a very high level of flexibility, which on the other side leads to building frameworks on a top of Zope frameworks, like CMF and Silvia.

      That's why Zope is implemented on a multi-paradigm generic programming language Python, which paradigm list includes: OOP, functiona programming, dynamic typing and scripting. Inside a framework you can use on paradigm or another, but you are not forced to it.

      I doubt the functionality and quality of Zope could be possible to implement on PHP, which is not a generic programming language (it's a template language), which is not designed as a programming language (it's evolved rather than mathematically thought) and it's lacking an integration of paradigms (OOP and FP specifically).

      I think that Python was the lowest possible level of programming language to choose for Zope. PHP suffers as a language in general. TCL and Ruby lack in paradigms. Perl is too obfuscated. Java, C++ are compilable (not scriptable) and thus are not flexible (apart from lacking the FP paradigm).

      Alternatively it could be one of "more pure" functional (and still with OOP) programming languages, like Lisp, OCaml or Haskell (or even Mozart). But those languages typically lack practical libraries and there are fewer programmers to code on them. So, the choice of Python was the best one, from both theoretical and practical stand point.

      --

      Less is more !
    11. Re:With Perl and Python being mainstream by pnatural · · Score: 1

      The problem with Zope is that with win32 you have two choices: instally cygwin/python with a ton of extraneous packaging, or ...

      not true. zope can run on win32 quite nicely with zope for win32 as distributed on zope.org. no activestate, no cygwin. the win32all package and its com stuff is separate, but just as easy to get.

      Zope may well be a good Unix solution, but I don't believe that it is for everybody.

      Zope is a framework for web solutions: the platform does not matter.

    12. Re:With Perl and Python being mainstream by Anonymous Coward · · Score: 0

      I'll be happy when common lisp become mainstream. It has many features which make it ideal tool for creating webapps. It's also great for other tasks.

    13. Re:With Perl and Python being mainstream by Art+Tatum · · Score: 1

      What's happening with ColdFusion/FuseBox? I'm not a web developer, so I don't have the insights that you would have, but it always looked like a nice technology.

    14. Re:With Perl and Python being mainstream by abulafia · · Score: 1
      Not sure what is currently happening with CF these days.

      I evaluated it for a company I used to work at, and couldn't find a reason to use it. The libraries were spagetti - we had on of their trainers come in and give us a weeklong development course, and he didn't know half of what was going on. The code paths were impossible to trace. And it was expensive. I was not impressed.

      Fusebox is an OK methodology, I suppose. If you do a lot of web development, I think you end up with your own framework at some point.

      --
      I forget what 8 was for.
    15. Re:With Perl and Python being mainstream by pmz · · Score: 1

      I'll be happy when common lisp become mainstream.

      We'd need to kill of the proprietary CL vendors, first. From what I've seen, even after decades, Lisp still suffers from wide differences in implementation. I'd much rather see "Works best with Common Lisp (2005 ANSI standard edition)" than "Allegro CL version XYZ (everyone else is SOL)".

    16. Re:With Perl and Python being mainstream by meatspray · · Score: 1

      CF is busy leaving MS-COM for java type things. Making all kinds of backwards but generally beneficial changes along the way and waiting for everyone to catch up and fix their code.

      Fusebox is a double edged sword with great benefits if you have a lot of coders with different mindsets working on a large project.

      On small projects or large ones with small minded developers it quickly skyrockets the number of files required to do everything. Obfustication is achieved simply from the amount of data you have to wade through to find any give piece of code.

      Then again we're just catching up with mx/fb3 right now :)

    17. Re:With Perl and Python being mainstream by Tablizer · · Score: 1

      I doubt the functionality and quality of Zope could be possible to implement on PHP, which is not a generic programming language (it's a template language),

      Other than lack of named parameters, is there anything specific you found about PHP that would greatly limit a Zope-like tool? Example psuedo-code?

      Lisp, OCaml or Haskell (or even Mozart). But those languages typically lack practical libraries

      Lisp lacks "practical libraries"?

  16. It's simple... by dazk · · Score: 5, Insightful

    Don't do it.

    I don't like the development of Mono and DotGnu anyways. Think about it. Gnome started in part because some people didn't like the QT license. A "problem" that is now resolved with QT being GPL licensed and a contract that will put it under a BSD-style license once Trolltech decides to stop working on it or is going out of business.

    Mono on the other hand reproduces MS technology that MS apperantly doesn't want to be open despite it's (marketing) efforts to standardize a subset of the Framework. I think developing with/for mono is counterproductive since it allows possibly great Opensource software to be used with Windows, taking away another reason for people to switch or even consider a switch. Because only a subset of .NET is halfopen, a great bit of .NET software won't run on linux anyways, which reduces the weight of one of the arguments for Mono significantly.

    While .NET might even be an interesting technology, community based (partial) support will only benefit Microsoft. It will add additional Software for Windows but probably only few Applications will arrive for Linux, since producing applications with a small subset of the API will be more work. Considering that a commercial QT license is not that expensive for businesses developing software compared to the labour cost, and the very few applications using this powerfull toolkit for easy multiplatform development, I really can't see many companies limiting themselves to the subset of .NET to create applications that also run on Linux.

    So in the end it should be clear, don't support Mono by developing applications for/with it.

    1. Re:It's simple... by adrianbaugh · · Score: 2, Interesting

      Your argument seems to be that only those people using Open Source opersting systems should be able to use other Open Source software. Why should this be? Would you prevent people using the GNU tools under Windows, or cygwin, or GIMP on Windows? While I think it's great when I see someone switch to Linux, the reason I think it's great is just that that person will have a better computing experience.
      In the end, everyone is free to use the tools that suit them best. If they happen to find a combination of Windows and OpenSource applications ideal for them, who are we to argue?

      --
      "'I pass the test,' she said. 'I will diminish, and go into the West, and remain Galadriel.'"
      - JRR Tolkien.
    2. Re:It's simple... by absurdhero · · Score: 4, Insightful

      What does QTs license change years ago have to do with making a mono and dotgnu creating webservice platforms and C# portability?

      I understand your concerns about mono helping microsoft, one can say the same thing about php and perl helping the MS server platform, gcc supporting MS development, and frozen bubble making windows a better gaming platform. This argument is old and has little effect in the real world.

      You seem to no nothing about DotGNU. The project's goal is to create a free software web platform in much the same way the GNU project set out to create a free unix-like platform. One could argue that GNU/Linux has helped SCO, ATT, or HP to improve their commercial unix, but somehow I think they would all disagree.

      And to revisit your issues with mono, claiming that C# and MSIL support for linux is helping microsoft more than it is helping anyone else is similar to saying that java support on linux is only good for Sun. I just don't see the evidence or reasoning.

      Your tie in with QT makes no sense. I think you are missing something important. QT and GTK+ are completely unrelated to the webservice and binary portability arenas where mono and dotgnu are. Incidentally, there are libraries to use QT and GTK+ from C#.

    3. Re: It's simple... by gidds · · Score: 2, Interesting
      Mono on the other hand reproduces MS technology that MS apperantly doesn't want to be open despite it's (marketing) efforts to standardize a subset of the Framework.

      Indeed. Does anyone else get the impression that M$ is getting other folk to code up, for free, their bait in a massive bait-and-switch operation?

      --

      Ceterum censeo subscriptionem esse delendam.

    4. Re:It's simple... by drkich · · Score: 3, Insightful
      So development of open source should not really be percued for the windows operating system. Because in your own words,
      "I think developing with/for mono is counterproductive since it allows possibly great Opensource software to be used with Windows, taking away another reason for people to switch or even consider a switch."
      I have to disagree with you there. You personally may think that the whole purpose of open source is to promote Linux to the uninitiated. I disagree.

      Freedom is the reason for Open Source. And if that means you run the open source software on an operating system of your choice, well that is what I call freedom. Yes it would be nice if everyone in the world would just standardize on Linux, but you can not even get the Linux world to do that. Look at all of the different distributions.

      So do not try to hi-jack the open source movement to advance your own narrow minded cause.
    5. Re:It's simple... by DarkOx · · Score: 1

      I totally agree. There is no reason to embarce this technology at all. It does nothing that can't be done already with more open stuffs. Why should we embrace new closed tech, it dose nothing but put us in patent danger. Embrace and extend danger etc etc.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    6. Re:It's simple... by dazk · · Score: 2, Insightful

      > What does QTs license change years ago have to do
      > with making a mono and dotgnu creating webservice
      > platforms and C# portability?

      Nothing at first. My intention was to highlight that in the past, far less dangerous license problems led to the Gnome project and ironically now, one of the major supporters of Gnome, Ximian, is heavily backing Mono and even somewhat pushing Mono towards Gnome.

      > one can say the same thing about php and perl
      > helping the MS server platform, gcc supporting
      > MS development, and frozen bubble making
      > windows a better gaming platform.

      Sure one could say that and it seems reasonable at first. But for me there is a difference. PHP, Perl and GCC are open. As mentioned in other comments, MS can slightly change APIs in future versions not opening up the changes. The main reason for MONO's existance will be gone. Perl, PHP and GCC can and do change as well but they are open and can be ported whereas Mono can become a "Cul de Sac" for anyone hoping to do cross platform development simply if MS finds it appropriate to do so.

      > You seem to no nothing about DotGNU. The
      > project's goal is to create a free software web
      > platform in much the same way the GNU project
      > set out to create a free unix-like platform.

      You are right. I simply assumed it was a project similar to Mono. Apperantly I was wrong here, sorry.

      >One could argue that GNU/Linux has helped SCO,
      >ATT, or HP to improve their commercial unix, but
      >somehow I think they would all disagree.

      This depends on how you look at it. If you look at a plain solaris, I at least feel that all the GNU tools make it an a lot friendlier environment. I think you misunderstood me. I don't say Open Source on Winodws is bad and I don't mind ported applications at all. What I dislike though is a seemingly open technology being heavily positioned against and modeled after a much more open platform (JAVA) and the efforts to bring this to Linux. In this case, Porting efforts are undertaken by the community and MS can shut them down or seriously cripple them once they decide Mono is eating away too much of their profits. This is impossible or much less possible in your examples. Of course the developed applications will stay but only on Windows.

      > And to revisit your issues with mono, claiming
      > that C# and MSIL support for linux is helping
      > microsoft more than it is helping anyone else
      > is similar to saying that java support on linux
      > is only good for Sun. I just don't see the
      > evidence or reasoning.

      Well, JAVA is heavily protected with Licenseing as well but it's in Sun's interest that JAVA supports as many platforms as possible. The development process is not as open as with most Opensource apps but the JAVA community process is imho ok. Of course Sun could theoretically stop support for all but their operating system at one point but Users of JAVA would have a much better position fighting an action like that in courts as they would have against Microsoft enforcing their patents on Mono since Mono was at no time officially supported by Microsoft.

      > Your tie in with QT makes no sense. I think
      > you are missing something important. QT and
      > GTK+ are completely unrelated to the webservice
      > and binary portability arenas where mono and
      > dotgnu are. Incidentally, there are libraries
      > to use QT and GTK+ from C#.

      I know what they are and of course webservices are something else. I'm aware that .NET is a lot more similar to JAVA than it was to QT or GTK. But both technologies are used to create multiplatform applications. JAVA and .NET allow that by running bytecode within an environment that abstracts Plattform from the binaries and GTK and QT go the "traditional" way of enabling to write highly similar code that can be compiled for many platforms. As I mentioned, I'm not that much informed about DotGn

    7. Re:It's simple... by r00zky · · Score: 1

      I think his argument seems more like: In the end the great benefited of .NET/mono development is Microsoft, ergo you're working for Microsoft for free.

      Not to mention that helping Microsoft undermines OSS viability in too many different ways to post in this short message.

      Portability of apps is great, if all parts get equivalent chances/benefits, which it isn't true in this case.

      --
      I'm a chainsmokin' alcoholic sociopath, so-ci-o-path
    8. Re:It's simple... by dazk · · Score: 1

      Since you are the second one complaining about that, it must have come across slightly different than intended.

      I don't mind Opensource or even FreeSoftware on windows at all. What I dislike though is cloneing the next sword to battle the market of a company that has near monopoly status already without even the slightest bit of assurance that this company will not at some stage kill or cripple the Mono project and essentially consume all the developed apps with that move.

      What's the point of creating open source software, especially open source software for linux if all your work might at some stage stop working on linux because MS decided to fight Mono?

      That's the reason for me drawing comparisons to the QT situation. Mono might be open source but it will never be open.

    9. Re:It's simple... by Anonymous Coward · · Score: 0

      That's sorta like saying: In the end the great benefited of GNU & POSIX development is AT&T/SCO, ergo you're working for AT&T/SCO for free.

      Oh wait. Maybe you are.

    10. Re:It's simple... by Tablizer · · Score: 1

      I think developing with/for mono is counterproductive since it allows possibly great Opensource software to be used with Windows, taking away another reason for people to switch or even consider a switch.

      You got it backwards. The best way to get people to switch is to make the OS irrelavant. The best way to do that is to slowly switch to applications and tools that run on all the major OS's. One day a bean counter will then ask, "Why are we paying so much to Microsoft when our stuff runs on open-source?"

    11. Re:It's simple... by IamTheRealMike · · Score: 0, Redundant
      Because only a subset of .NET is halfopen, a great bit of .NET software won't run on linux anyways, which reduces the weight of one of the arguments for Mono significantly.

      Look at the Wine project. Do you really think the fact that some APIs aren't ISO standards are going to stop people getting compatability? No, me neither.

      Considering that a commercial QT license is not that expensive for businesses developing software compared to the labour cost

      ... sounds like you've been reading KDE News too much. Given a choice of two powerful toolkits, one that is fully supported in a clean, modern language (ie not C++) and is available for free, and the other which is not, there's really little competition. If you think .NET competes with Qt, you clearly have never worked in a language like C# or Java.

    12. Re:It's simple... by mbbac · · Score: 1
      And to revisit your issues with mono, claiming that C# and MSIL support for linux is helping microsoft more than it is helping anyone else is similar to saying that java support on linux is only good for Sun. I just don't see the evidence or reasoning.
      No, it's not. Sun gives you the whole enchillada. Microsoft lets you built the beans and the cheese but doesn't want you to implement their special sauce.

      My apologies if I got my mexican food wrong.
      --

      mbbac

    13. Re: It's simple... by pmz · · Score: 1

      Does anyone else get the impression that M$ is getting other folk to code up, for free, their bait in a massive bait-and-switch operation?

      Actually, I think they are trying to inflate the "moist towelette" industry. Imagine the cry of millions of developers whose hands are dirty after working with C#/.NET, and Microsoft steps right in with a sample pack and a big smile on their faces.

  17. Perl libs, Ruby Syntax, threads, OR speed by RLiegh · · Score: 3, Funny

    Fixed your post...unless you seriously think that you can have all four together. And if you do, I want some of what you're smoking!

    1. Re:Perl libs, Ruby Syntax, threads, OR speed by jtdubs · · Score: 1

      Well, syntax has nothing to do with threads or speed. And plenty of languages have threads and speed. So you must think there is some fundamental incompatability between perl-like libraries and one of the others... but which one?

      Justin Dubs

  18. M2'ing all negative mods as unfair by RLiegh · · Score: 0

    Glad I'm not the only one!

  19. I don't think so... by boatboy · · Score: 3, Insightful

    Could be wrong, but I think Microsoft actually "sees the light" in some respects, especially when it comes to a development platform. It makes sense- it builds a larger base of developers using .NET. Maybe not to the degree /.ers would want, but judging by the amount of open-source sites and projects that have a Microsoft affiliation, I think they're moving more that way.

    As for "just System.*" being an open standard, it's important to realize that comprises all of .NET. Other libraries build on that functionality (such as Microsoft Application Blocks), but the entire core functionality is in System.*

    1. Re:I don't think so... by Malcontent · · Score: 3, Insightful

      "but I think Microsoft actually "sees the light" in some respects, especially when it comes to a development platform."

      I don't know. I am trying hard to think of a company that partnered with MS and didn't get backstabbed and for the life of me I can't think of one. I am sure each and every one of those companies said to themselves "I think MS acually sees the light now and despite what they did to those other companies I am sure they won't screw us".

      --

      War is necrophilia.

    2. Re:I don't think so... by Deusy · · Score: 1

      Could be wrong, but I think Microsoft actually "sees the light" in some respects, especially when it comes to a development platform. It makes sense- it builds a larger base of developers using .NET. Maybe not to the degree /.ers would want, but judging by the amount of open-source sites and projects that have a Microsoft affiliation, I think they're moving more that way.

      Wow, is it a second coming? I remember when they were seeing the light about 10 years ago when they turned a blind eye to the rife piracy of their products because it meant more people were using them. Now they're starting to crack down because they are the dominant force.

      Am I the only one who thinks that Microsoft will happily let Mono and DotGNU develop only as long as it suits Microsoft's cause? 5 years from now, Java is dying, .NET is by far the dominant development platform, do you think Microsoft is going to forget they have a number of key patents that could literally put down it's competition and push people back from Linux into Windows?

      Do not confuse business strategy with philosophy. Microsoft only has the former.

      --

      Free Gamer - Free games list and commentary

    3. Re:I don't think so... by IamTheRealMike · · Score: 1

      How about every company that has written software for Windows? Microsoft first and foremost don't make money from backstabbing, they make money from selling people tools. If .NET runs on Linux, well, they may well see that as a Plan B for when the Windows cash cow gets whacked by Linux. If they are still the Number 1 vendor of .NET tools, resources, training and so on they still have a place in the market.

    4. Re:I don't think so... by 16K+Ram+Pack · · Score: 1
      Question 1: how does Microsoft make money from .NET on Linux?

      Question 2: how does it help MS control the market?

      The answers are 1) It can't. 2) It doesn't. If Microsoft have allowed it, it's either because it's seen as too small to be a priority, or it's a trap to get more people onto .NET with the eventual aim of getting people back onto Windows.

      Do not being under any illusion that the Microsoft leopard has changed its spots. Ever.

    5. Re:I don't think so... by molarmass192 · · Score: 1

      Microsoft first and foremost don't make money from backstabbing, they make money from selling people tools.

      That's really only addressing the wording of the parent's post. Of course MS makes money from selling people tools but you need a market to sell into and getting that market is 90% of the work of making a sale. MS makes (some, not all) sales by stealing it's partners' markets. Think of it as piggy-backing on the partner to gain traction and then shutting them out. Just do a little research on MS's partnerships with IBM, Sybase, and Corel for examples. The only companys I know of that weren't noticably hurt with an MS partnership are Citrix and Symantec, even then MS introduced their "Terminal Server" and bought out Symantec competitor GeCAD suspiciously soon after those partnerships were formed.

      As for Plan B, that's possible but I highly doubt it. MS makes the bulk of it's profits from Windows and Office, not dev tools. MS cannot loose the Windows market or the Office market and remain the company it is today. I think MS is tolerating the Mono and DotGNU projects because it's not impacting their market, it's very low profile, and they don't believe it's perceived as a viable alternative. That's probably accurate outside the /. crowd. However, if those projects ever start to gain credibility and be seen as a migration path off of Windows, I'm certain you'll see MS shut those down. Judging by the imperceptible impacts of non-Windows ASP runtimes, they appear to be adopting the same "wait and see" strategy.

      --

      Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
    6. Re:I don't think so... by Anonymous Coward · · Score: 0

      I agree.
      Very crudely: Microsoft has to protect Windows at all costs since it represents one of its two major revenue streams (the other being Office) - hence Java/J2EE being such a worry (and Linux also). .NET exists solely to provide an MS/Windows only propriety thing that looks a bit like J2EE. Microsoft knows that it can win a slice of the market by dint of just claiming that it is better than J2EE, and more importantly, create enough FUD to slow down the adoption of J2EE in corporations. So if the .NET ports to Linux etc. ever get really good have no doubt that Microsoft will find a way to kill them off - either by endlessly breaking compatibility with different versions of .NET and blaming the open source community (rather like it did with Java and the browser before that) or by claiming patent infringements or something even more diabolical I can't think of. Otherwise what was the point of sepnding all that money on .NET?

    7. Re:I don't think so... by boatboy · · Score: 1

      How does Microsoft make money from .NET on Linux?
      The same way anybody else can make money on Linux. If you believe this is impossible, it follows logically that companies other than Microsoft cannot make money from x on linux.

      How does it help MS control the market?
      Well, if they played it right, they'd be the #1 provider of tools for cross-platform .NET development. More importantly, they are clearly moving applications like Office to .NET. Think about that: Office, IE, etc. all become cross-platform, and MS doesn't have to drop a dime beyond support for a .NET standard to do it.

      I can see the point of those who don't trust MS because of past & current business practices, but I guess I'm just not as militant about it. It seems like a more reasonable reaction, if one is _really_ opposed to Microsoft, to push for _more_ development in Linux .NET. For example, what if Ford depended on Mono in their new Linux system? I think Microsoft would have a hard time pulling the plug on it then.

    8. Re:I don't think so... by 16K+Ram+Pack · · Score: 1
      My point was that Microsoft .NET on Linux as Mono doesn't make them any money. So they aren't going to do it - it also strengths the hand of Linux which isn't good for their sales of Windows operating systems. The only way they could probably make money is out of sales of Visual Studio (although there are alternative editors).

      As for Microsoft 'playing it right' that's what they've always done. Business-wise, I take my hat off to them. They've sewn up so much of the computer business.

      It's not that I don't trust Microsoft, it's that their pattern of behaviour over the past 10 years has been the same - to control the market and extend themselves further. And part of that control relies on the operating system. It relies on Windows update buttons offering Microsoft upgrades to give new products which use MS file formats and squeeze out the competition. Software embedded in the operating system so that you use THEIR messenger and not someone else's.

      It's also a pretty good money earner.

      As for large corporations using MONO, I imagine that there will be some changes to the .NET framework, destandardized and any code written in Visual Studio won't work.

  20. Ummmm.... by inode_buddha · · Score: 1

    maybe linux has *already* stolen "income-generating-business" and hence the recent focus on it by Microsoft?

    I honestly don't think the specific language/implementation (Java vs C#) has much to do with it. Nor, for that matter, does the business integration concept of dot-net or mono.

    What has *everything* to do with it (just IMHO) is whether a business process/procedure should be patentable in the first place, let alone specific implementations.

    Just a qualifier here; I don't do that stuff, I guess I'm "the wider community". However, I'm not all that concerned if an organization could "take it away from us"; if they do so, they'll do it without the insight of the original founders even giving a crap if their organization lives or dies.

    --
    C|N>K
  21. A few thoughts.... by revividus · · Score: 4, Interesting
    Mono seems to me to be a good idea, mostly because it will enable people who have invested a lot of time into learning it to consider switching to developing for Linux without having to learn whole new languages. Will that actually happen? I suppose only time will tell...

    Another thought. Suppose they did `take it away'. What good will that do them? How many languages are there which duplicate or mimic large portions of basic C syntax and structures? It seems to me that all the Mono folks would need to do is declare that they were developing a new language using syntax similar to C#.

    They could call it `D-flat'. :-)

    1. Re:A few thoughts.... by anonymous+loser · · Score: 2, Insightful

      Just so you know, C# is a (open) language standard, and has very little to do with the .NET framework other than they were announced at the same time, and developed by the same people.

      The .NET framework isn't a language so much as, well, a framework. It's very much like the Java platform if you didn't limit yourself to programming for it only in Java. Only the .NET platform has the advantage of the developers having observed all the mistakes made with the Java platform, so they managed to avoid most of those and create some new ones of their own instead. Java, by the way, also fits your description of a language with basic C (well, more like C++) syntax and structures.

      As an aside, there are also some experimental Java bytecode compilers out there that compile from other languages than Java. But Java doesn't have the resources of Microsoft pushing it forward, and Sun doesn't seem to be interested in letting go of their platform any more than MS does.

    2. Re:A few thoughts.... by Anonymous Coward · · Score: 0

      What good will that do them?
      Cmon, it's obvious: let the community/industry develop a couple of killer apps on mono/c# and spread them, let companies built huge inhouse apps on this platform, let developers train themselves in it for weeks, months, years, and when investments are large enough pull it away and tell them they have to migrate to .net/windows, even offer a nice migration path since you're so customer friendly, and committed to the community ...

    3. Re:A few thoughts.... by alext · · Score: 1

      But Java doesn't have the resources of Microsoft pushing it forward

      Correct. It has the resources of Sun, IBM, BEA, Oracle and many others.

      Sun doesn't seem to be interested in letting go of their platform any more than MS does.

      Really? That will come as news to the members of the JCP. I hope you've taken steps to inform them that they're wasting their time.

    4. Re:A few thoughts.... by pmz · · Score: 1

      Sun doesn't seem to be interested in letting go of their platform any more than MS does.

      I don't hear Microsoft saying they will consider opensourcing .NET when the time is right. At least, Sun is open to the idea.

      Also consider checking out websites like www.openoffice.org, and www.sunsource.net. Sun is a non-trivial member of the Open Source community.

      In this interview with Scott McNealy, McNealy mentions he is a libertarian. As is ESR. We shouldn't underestimate Sun's attitude towards giving people the tools they need to excersize choice.

  22. ECMA submittals *ALSO* subject to patents by cheesedog · · Score: 5, Insightful
    As a note, the reason Microsoft continually goes to ECMA for standardization is that ECMA doesn't require that "standardized" specifications be immune from patent protection. From my understanding, it doesn't matter what is and isn't in the spec -- Microsoft can claim patent rights on any novel* pieces of .NET that they want.

    *and of course, the the USPTO, "novel" means "anything a 18-month old baby couldn't have authored."

    1. Re:ECMA submittals *ALSO* subject to patents by rborek · · Score: 4, Informative

      Microsoft went the ECMA route because it's faster and easier to get an ECMA standard passed than to go the ISO route, and once ECMA has passed the standard it's a heck of a lot easier to get it standardized by ISO. C# and the CLI are both ECMA and ISO standards. See ECMA and ISO/IEC C# and Common Language Infrastructure Standards. C# - ECMA-334, ISO/IEC 23270 CLI - ECMA-335, ISO/IEC 23271 CLI Technical Report - ECMA TR84, ISO/IEC 23272

    2. Re:ECMA submittals *ALSO* subject to patents by HoneyBunchesOfGoats · · Score: 1

      ...[to] the USPTO, "novel" means "anything a 18-month old baby couldn't have authored."

      This standard is too narrow to actually be what the USPTO has used.

    3. Re:ECMA submittals *ALSO* subject to patents by Waffle+Iron · · Score: 1

      More precisely, the baby test determines if the patent application is nonobvious.

      Here is the algorithm (implemented in Python) for determining patent novelty:

      def is_novel(pending_claims):
      prior_art = file("all_issued_us_patent_claims_concatenated.txt ") .read()
      return prior_art.find(pending_claims) < 0

      Likewise,

      def is_useful(pending_claims):
      return True

    4. Re:ECMA submittals *ALSO* subject to patents by Malcontent · · Score: 1

      Yes but does ECMA issue standards for patented material or not? If so what good is a ECMA standard?

      --

      War is necrophilia.

    5. Re: ECMA submittals *ALSO* subject to patents by bizcoach · · Score: 1
      According to the ECMA secretary-general, MS has promised royalty-free licensing for any and all patented technology that is required for implementing those ECMA standards.

      Some other parts of .NET are unproblematic also. For example, System.Windows.Forms is such a thin wrapper around *old* APIs that there's absolutely nothing non-obvious there which would be in danger of a patent.

      For the rest of .NET, there is a possibility that maybe the full version of DotGNU Portable.NET can be developed and used legally only outside of the US. I will try to avoid a situation where we have to distribute some useful software as "non-US", but depending on how bad the patents issue turns out to be, it could happen that that is a necessity.

      However, I'm confident that that is the worst thing that can possibly happen. The core parts of DotGNU will always be free to use and contribute to anywhere in the world, and we will continue building everything that is necessary for full compatibility, and these things will be free to use and contribute to for all individuals and businesses in countries which do not have a broken legal system that makes software ideas patentable.

      Greetings,
      Norbert.

    6. Re:ECMA submittals *ALSO* subject to patents by yerricde · · Score: 1

      The DVD-ROM physical layer is standardized by ECMA and is patented.

      MPEG-4 is standardized by Iso and is patented.

      --
      Will I retire or break 10K?
  23. You play with fire... by Anonymous Coward · · Score: 0

    ...you get burnt. Sooner of later M$ are gonna turn up the heat - guaranteed

    1. Re:You play with fire... by bizcoach · · Score: 1
      Anonymous Coward wrote: "..you get burnt. Sooner of later M$ are gonna turn up the heat - guaranteed"

      I'm expecting this. One of the things I do daily before switching on my monitor is to make sure that I have my asbestos underwear properly in place. :-)

      Of course MS will put up a fight as soon as what we're doing becomes a real threat to them. Sometimes my knees get wobbly when I think about this, but then we knew since the beginnings of DotGNU that it's going to take some guts to not only challenge MS but to actually fight it out.

      If I fight and I get burned, at least I got burned while fighting for what I believe in.

      If I don't fight and MS manages to catch the whole IT world in their .NET, building another effective monopoly (one which is much harder to dislodge than a desktop monopoly can possibly be), I'll always have to have a bad conscience if I haven't fought.

      I've made my choice.

      What is yours?

      Greetings,
      Norbert

  24. PARC by Izago909 · · Score: 3, Insightful

    Too bad the people at PARC did't patent the idea of a graphic windowing operating system. Where do you think Jobs and Gates got the idea? You very well could be buying your OS from Xerox.

    1. Re:PARC by thanasakis · · Score: 1

      Recently I was studying an old book about Solaris administration (circa 1997) and behind the front page it said clearly that they (Sun) have a non-exclusive license to use the GUI that Xerox developed. Are you sure that MS or Apple haven't paid to use the technology?

    2. Re:PARC by metamatic · · Score: 1
      You very well could be buying your OS from Xerox.

      Apple did.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
  25. I've fallen and I can't get up! by Anonymous Coward · · Score: 0

    If you're waiting for Parrot to be finished then you'll be waiting for quite a while then. It's been over two years and they have yet to produce anything remotely useful to any non-Parrot developer. The goal of supporting Perl6 is just a dream at this point because Perl6 has yet to specified. I've never seen a virtual machine as needlessly complicated and convoluted as Parrot's VM. Parrot has become some sort of bizarre quest to some destination only the developers know. I can't think of another language that has had as much publicity, time, developers and funding as Parrot and still have nothing substantial to show for it.

  26. Re:Older coders welcomed where needed by the+eric+conspiracy · · Score: 3, Informative

    Too bad the people at PARC did't patent the idea of a graphic windowing operating system.

    They did. They waited too long to enforce the patents. Xerox totally bungled their chance to become Microsoft.

  27. Call me stupid by codepunk · · Score: 4, Insightful

    What on earth is so great about .NET and or Mono. I see absolutely nothing about it that would make me desire to code with it.

    Is it faster? No

    Is Development Faster ? No

    Is it cross platform ? No

    Does it do things that other languages cannot? No

    Is it Encumbered By Patents? Yes

    Sure makes me want to use it....

    --


    Got Code?
    1. Re:Call me stupid by dazk · · Score: 2, Insightful

      > Is it faster? No
      Compared to what? Plain C, compiled by a highly optimizing compiler for a certain platform? No, of course not. JAVA? Maybe. Interpreted languages without bytecode support? Maybe.

      > Is Development Faster ? No
      Yes, on Winodws with visual studio. At least compared to plain C with a texteditor. This also requires use of all the non open stuff of course.

      > Is it cross platform ? No
      In theory yes, which makes it seem interesting at first. But:

      > Is it Encumbered By Patents? Yes
      Yes. That's imho the most important reason to not use it for open source development.

      > Does it do things that other languages cannot? No
      No but that would be an argument against any other language. But having different languages is a good thing. Besides, in theory .NET is language independant, which makes it interesting. Of course all language.NET implementations have to be used slightly different than their native counterparts to fit within the boundaries of the framework and it's programming paradigms.

    2. Re:Call me stupid by codepunk · · Score: 1

      But you still have not given me a reason to use it....In order to make the time investment it has to offer something better which it clearly does not. From what I know about it which is a fair amount just straight python stomps a mud hole in it.

      --


      Got Code?
    3. Re:Call me stupid by Baavgai · · Score: 5, Informative

      I wont say stupid, but probably biased.

      I'm a programmer / project manager ( / DBA, etc. ) for a very small shop. We write in house programs for specific industry requirements.

      We've done stuff in Java; as an OOP advocate, I love Java. As project manager, I get blank stares from programmers that want the equivalent of visual basic to work in. We've now standardized on C#.NET. The programmers still look a little lost when I emphasize OO practices, but they're real happy with Visual Studio to hold their hands.

      So,

      Is it faster? Perhaps.
      Remember, in a rich client GUI environment, .NET can leverage native OS architecture quite efficiently. It simply blows Java Swing away in this area.

      Is Development Faster ? YES.
      Bash them all the you like. Microsoft's development tools have always been good. The Visual Studio suite is much better than any equivalent product I've seen.

      Is it cross platform ? No
      Yes, a big no here. However, expect to see the CLR running on platforms other than straight up Windows in the future. In the end, when most commercial clients run Windows this is more of a selling point than a detriment.

      Does it do things that other languages cannot? No
      Well, this can pretty much be said of any language. As a Java programmer, I really enjoy C#, it's does the same thing as Java, it just does it quite well for Windows.

      Is it Encumbered By Patents? Yes
      So? For OSS this doesn't fly, for the boss, this isn't really a consideration.

    4. Re:Call me stupid by Overly+Critical+Guy · · Score: 0, Troll

      Is it faster? No

      Yes. It is.

      Is Development Faster ? No

      Compare the amount of lines in a Java program to the same program done in .NET.

      Is it cross platform ? No

      Um, hello? Mono?

      Does it do things that other languages cannot? No

      All languages do things their other languages cannot. It's called the difference between those languages.

      Your post is just FUD from the looks of it.

      --
      "Sufferin' succotash."
    5. Re:Call me stupid by codepunk · · Score: 3, Interesting

      Ok,

      Rich Client native gui, here you have two other cross platform choices..wxwindows and SWT both which offer native, fast gui's.

      Microsoft Visual Studio the best? You obviously have never used any tool from Borland which absolutely stomps a mud hole in anything that MS has ever built.

      Most commercial clients might run windows but I can tell you for a fact it it does not run on Linux we ain't buying it in our shop(sounds like I just shot your selling point all to hell). If you like java and you like C# and you sell software why on earth would you lock yourself to a platform.

      --


      Got Code?
    6. Re:Call me stupid by rdean400 · · Score: 1

      Is it faster? Perhaps at the low end, but definitely not at the high end.

      Is development faster? Same answer.

      Is it cross platform? Until Mono, DotGNU, and or Rotor are considered official parts of the .net platform, they are not part of .net. They duplicate .net functionality, but that doesn't mean they are .net.

      Does it do things that other languages cannot? N/A, it's a platform, not a language. However, one of the benefits of the platform is that it does provide managed code, but we've already seen that in Java.

      Your post is just as much FUD as the first post, from the looks of it. The truth is somewhere in the middle.

    7. Re:Call me stupid by dazk · · Score: 1

      > But you still have not given me a reason to use it....

      I did not intend to. Slighly down I even explained why I wouldn't use it. I just disagreed with some of your claims.

    8. Re:Call me stupid by Anonymous Coward · · Score: 0

      Re: Is it faster?

      Yes: Check out latest theserverside study. It is faster than the "best" J2EE app server in all tests but one.

      Yes: 3x Faster than ASP classic

      Close: Just shy of being as fast as C++ ISAPI dlls.

      Somewhere I saw GPL code for Quake done in .NET. That says alot.

      Re: Is Development Faster?

      Yes. Again compare to theserverside J2EE study -- approx 2.5k .NET loc vs 14k J2EE loc. Also tuning took 3 days vs 6 weeks

      Re: Is it cross platform ?

      Yes. Check Rotor (http://msdn.microsoft.com/msdnmag/issues/02/07/sh aredsourcecli/default.aspx) where the CLR with C# works on FreeBSD, Windows, & OS X

      Re: Does it do things that other languages cannot?

      Yes. Choose the language and then you can see what it can do. Against java is has atributes, finite loops, etc. Plans in place for generics, easier access to perph., & ML features

      Is it Encumbered By Patents? Yes

      I have no idea -- IANAL so I ignore patents.

    9. Re:Call me stupid by miguel · · Score: 4, Insightful

      You got the questions with the wrong answers:

      1. Measuring speed is difficult, but to give you an example, the Mono C# compiler compiles itself on 3.5 seconds (50,000 lines of code).

      2. development is faster, I would say 3x to 6x depending on the task. In the case of ASP.NET vs J2EE, we know from two studies (ours and Forrester/Giga) that it is 20-28% more effective (see my blog for details).

      3. Is it cross platform? Yes, it is. The Mono C# compiler was originally built/compiled on Windows. Today, it does not matter. We routinely run large applications (web services, console, gui) on it.

      4. It offers plenty of functionality that is hard to find elsewhere: cross-language interop, unified GC/threading/io

      5. Patents: the ECMA core has been freed of any patents, see: primates.ximian.com/~miguel/tmp/map.png

    10. Re:Call me stupid by Snoopy77 · · Score: 1
      Remember, in a rich client GUI environment, .NET can leverage native OS architecture quite efficiently. It simply blows Java Swing away in this area.

      I just won buzzword bingo!

      --
      "She's a West Texas girl, just like me" - G.W Bush Iraqis
    11. Re:Call me stupid by Snoopy77 · · Score: 2, Interesting

      Seriously, if all your programmers are hardcore VB guys why not just use VB.Net. It seems like they are not using C# in an OO way anyway.

      As for fast GUI, if you are only developing for windows why not just use the WinAPI directly without going through a VM. If you want a cross platform solution try wxWindows or Kylix. And speaking of Kylix, Borland are THE leaders in RAD tools and have been for years.

      I'm still trying to figure out what the whole point of C# is. It's similar to Java, but it is not cross platform, but it's not as quick as a truly native app written in VB or C++.

      --
      "She's a West Texas girl, just like me" - G.W Bush Iraqis
    12. Re:Call me stupid by kannibal_klown · · Score: 1

      I hear a lot of MS bashing, constantly sayign all MS products suck. And, for a while, I would agree that Borland products were FAR more superior to MS products.

      We're using Borland JBuilder 9 Developer at work. We're also use Visual Studio .Net 2003 for C# development.

      To be honest, I like VS.Net 2003 a lot more than JBuilder. Don't get me wrong, JBuilder is nice, but not AS nice. Also, JB is a hog. A 2 GHz machine can crawl when going into design mode with a complex frame and sometimes when performing auto-complete. VS.Net 2003 is really speedy getting to design mode. And in C#, it builds the forms based on strict code, much like JB, only putting it a seperate file.

      Personally, I'm trying to learn both platforms. They're similar enough to make the learning curve rather easy.

    13. Re:Call me stupid by bobbozzo · · Score: 2, Insightful
      I'm still trying to figure out what the whole point of C# is. It's similar to Java, but it is not cross platform, but it's not as quick as a truly native app written in VB or C++.

      C# is MS's answer to Java: MS claimed (initially) that C# is totally portable, yadda yadda yadda.

      Reality is they're just providing an excuse for MS weenies to justify sticking with MS instead of using Java or even PHP (for smaller projects) or whatever.

      --
      Nothing to see here; Move along.
    14. Re:Call me stupid by jasonditz · · Score: 1

      As project manager, I get blank stares from programmers that want the equivalent of visual basic to work in.

      I've got news for you, Mr. Project Manager, if they want the equivalent of visual basic those blank stares aren't directed at you, but at existance :)

    15. Re:Call me stupid by Malcontent · · Score: 1

      "Bash them all the you like. Microsoft's development tools have always been good. The Visual Studio suite is much better than any equivalent product I've seen."

      It is certainly not better then webobjects. It is certainly much worse then the upcoming Xcode environment from Apple.

      --

      War is necrophilia.

    16. Re:Call me stupid by anthonyrcalgary · · Score: 1

      "I'm still trying to figure out what the whole point of C# is. It's similar to Java, but it is not cross platform, but it's not as quick as a truly native app written in VB or C++."

      It is cross platform, for some definitions of platform.

      Microsoft saw IA-64 and x86-64. They knew most software would still be released x86 binaries only, and while the new architechtures would maintain binary compatability, something native would be better. This way allows them and everyone else to take advantage of a powerful new architechture without the additional development cost.

      We compile a native binary on each system, they have a binary that'll run on any Windows. Really, it's a good solution if you assume you're dealing with people that don't want their source code getting out. The native binary has less overhead at runtime, but Windows has tons of overhead even without .NET.

      Doesn't .NET cache a native optimized copy of the binary anyway? I read something about that but I don't remember if they actually did it.

      --
      When someone might yell at me, it has to be OpenBSD.
    17. Re:Call me stupid by Sajarak · · Score: 1

      I don't see how this rates as "insightful". To start off with, what languages/runtimes are you comparing .NET/Mono to? Under what circumstances are you making your comparisons?

      Off the top of my head, I can think of a couple of areas where .NET stands out: the first is developing Windows applications - it beats the hell out of Swing (for example) for developing GUIs. Granted the cross-platform support will take a while to get there. The other area is ASP.NET, which provides, in my opinion, a much better framework than most other platforms for writing dynamic web pages because it allows you to completely separate your HTML from the code that manipulates it. And it shouldn't be too long before you can run ASP.NET web apps completely within Mono or DotGNU.

    18. Re:Call me stupid by SgtChaireBourne · · Score: 1
      any tool from Borland which absolutely stomps a mud hole in anything that MS has ever built.
      Ok that explains why MS went after Borland a while ago.
      --
      Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
    19. Re:Call me stupid by LarsWestergren · · Score: 3, Insightful

      Hi,

      I think you are doing a good job as programmers, but I have always been a bit worried that you are helping MS to slay Java. To me it seems they are fighting really hard on two fronts now, against Linux and against Java. If they manage to get .Net/C# and all that to be the business standard, with your help, won't that make it easier for them to turn against the one remaining target?

      Even if it is Linux that becomes the favoured platform for .Net, do you think that will stop MS from boasting to the heavens how great their new framework is? And all the pointy haired bosses will buy more MS stock and products...

      I'm sure Sun are no angels, but I happen to like both Linux and Java, so...

      --

      Being bitter is drinking poison and hoping someone else will die

    20. Re:Call me stupid by Trejkaz · · Score: 1

      J2EE is a notoriously annoying framework to develop for anyway. Even if you're restricted to Java, Enterprise Object Broker is well over 28% faster to develop for.

      --
      Karma: It's all a bunch of tree-huggin' hippy crap!
    21. Re:Call me stupid by johnnliu · · Score: 1

      Source please.
      What sort of blanket comment is this? What are you comparing it with? (trying not to start a flame, let's look at each sentence constructively)

      > Is it faster? No

      Yes, compared to Sun's Java VM. Gosh I loved Java, but I just hated how slow it was. (oh uh flame-war warning)

      > Is Development Faster ? No

      Are we comparing with C? What sort of application are you referring to? Are IDEs taken into account? (You might need to take your comment back if VS.NET is in the equation)

      > Is it cross platform ? No

      It depends on what you are doing. If you don't use certain APIs that aren't available on other platforms, you're probably ok. But isn't this the case with all other languages and technologies to a certain degree?

      > Does it do things that other languages cannot? No

      Sure you can always write everything in C or even in assembly language. But really, we don't work that way.

      > Is it Encumbered By Patents? Yes

      On this one, my gut feeling is the same as yours, but I don't see anything solid yet. (I'm probably more naive than some).

      > Sure makes me want to use it....

      If you work on the MS platform only, this is the best thing since... well, ever.

    22. Re:Call me stupid by alext · · Score: 3, Insightful

      As strictly speaking only your fifth point is relevant to the topic, we should examine it with some care.

      My impression is that you are still perpetrating the CLR/Dotnet bait-and-switch policy, where the status of the CLR in terms of standardization and patent encumberances is used to misleadingly imply that the whole of Dotnet is similarly standardized and (supposedly) unencumbered by patents.

      In other words, you have not been able to progress or resolve the fundamental issue here in over two years, when similar discussions took place here and in other forums.

      If you have more recent information regarding Microsoft's position then you are more than welcome to share it with us. However, until such time as the IP risk has been adequately addressed, we would appreciate it if you refrained from further misleading the OSS community in this regard.

    23. Re:Call me stupid by IamTheRealMike · · Score: 2, Insightful
      My impression is that you are still perpetrating the CLR/Dotnet bait-and-switch policy, where the status of the CLR in terms of standardization and patent encumberances is used to misleadingly imply that the whole of Dotnet is similarly standardized and (supposedly) unencumbered by patents.

      No, reread what he wrote. Miguel quite clearly stated, and he even has a pretty map to show it even more clearly, which parts are free of patents and which parts are not. This is common knowledge. It's in the FAQ.

      Meanwhile, which parts of Java are patented? I dunno. I've never seen a map of it. Maybe none, maybe all.

      In other words, you have not been able to progress or resolve the fundamental issue here in over two years, when similar discussions took place here and in other forums.

      If by "the fundamental issue" you mean patent exemption from the entirety of the framework, then I guess they haven't. That's too bad, but it's worth remembering that any patents Microsoft do hold will almost certainly not be specific enough to only apply to .NET - the equivalent SOAP libraries for Python, Java, C, whatever, might well be covered too.

      However, until such time as the IP risk has been adequately addressed, we would appreciate it if you refrained from further misleading the OSS community in this regard.

      Who is "we"? I'm not feeling misled at the moment. All software carries risk of patents, indeed, there are so many that I've probably violated many in my life already.

      To be frank, given that the closest the open source community has got to something like C# is perhaps Python, which isn't compiled and has no static typing, it's looking like the best alternative right now.

      I haven't used Mono yet, and probably won't for some time, but at the moment as an open source developer I've looked at the risks of patents and decided that the risk is acceptable. Certainly as we have to clone .NET anyway for application compatability, the point is somewhat moot. Wine has been OK for a decade, so hopefully the same will be true of Mono.

    24. Re:Call me stupid by IamTheRealMike · · Score: 1
      If they manage to get .Net/C# and all that to be the business standard, with your help, won't that make it easier for them to turn against the one remaining target?

      I doubt it. They are a big company and OS vs server/class platform basically fall into different areas. The energy they are expending against Linux is certainly greater than what they are expending against Sun already.

      Even if it is Linux that becomes the favoured platform for .Net, do you think that will stop MS from boasting to the heavens how great their new framework is? And all the pointy haired bosses will buy more MS stock and products...

      The PHBs will buy into whatever is succesful and they think has a future in the market. If Microsofts tools are so much better than the open source equivalents, well, more power to them. We'll just have to do better.

      If anything Mono will help avoid people being locked into .NET and therefore Windows. Now which would you prefer - the PHBs to buy Microsoft because they have to, or because they make the best tools? Hint: one is far easier to compete with than the other.

      I'm sure Sun are no angels, but I happen to like both Linux and Java, so...

      Right, they aren't. In case you hadn't noticed, up until recently it wasn't even possible to get the JVM for Linux without going through a massive EULA, downloading the >10mb file from a non-resumable location and so on.

      Look at it this way, at least with .NET you'll have a decent free software implementation to work with.

    25. Re:Call me stupid by radish · · Score: 1

      We've done stuff in Java; as an OOP advocate, I love Java. As project manager, I get blank stares from programmers that want the equivalent of visual basic to work in

      *cough* IntelliJ IDEA */cough*

      Then again if your programmers love VB and don't know OO, maybe you need new programmers?

      --

      ---- Den ene knappen er powerknapp, den andre er Bender voice knapp "Bite My Shiny Metal Ass"

    26. Re:Call me stupid by PurpleWizard · · Score: 1
      Ok stupid:-)

      I see one tenuous reason for dotgnu or mono. They will provide VB to the nix platforms. Which as a consequence could be made a module that can be integrated into the likes of Open Office to make it capable of running those portions of spreadsheets and Word macros that are currently out of reach.

      100% MSOffice compatibility possible?

    27. Re:Call me stupid by Anonymous Coward · · Score: 0
      Visual Studio might be superficially the slickest but something like JBuilder totally murders DevStudio when it comes to visual development. For example, try developing and debugging a client and a server, at the same time from the same DevStudio and see how far you get. Simply put you can't and end up juggling multiple copies of DevStudio.


      JBuilder has a GUI that copes with multiple projects at the same time, multiple build configurations, supports multiple EJB servers, generates UML and documentation on the fly and much more.


      Better yet, the personal version is available for free from Borland.com and is perfectly usable for knocking out J2SE apps. With a bit of classpath fudging you can develop J2EE apps too, although you won't benefit from the extra tools and wizards found in the enterprise edition.

    28. Re:Call me stupid by twaltari · · Score: 1

      However, expect to see the CLR running on platforms other than straight up Windows in the future.

      I wouldn't expect. Microsoft made the exact same promises when they introduced DCOM in 1997, but DCOM "implementatations" on platforms other than Windows have always been completely useless. This is kinda like WinNT's Posix "support" they introduced just for marketing purposes. Vendor-lock-in is very high in Microsoft's list of priorities, admit it!

    29. Re:Call me stupid by alext · · Score: 1

      I've no doubt that the position regarding what Mono actually comprises, what parts of it are standard and open and what parts are regarded as proprietary by Microsoft may be clear to you and Miguel. For the rest of us, the picture is rather more murky.

      Unfortunately, our understanding isn't helped by the "flexible" way in which leading Mono proponents respond to basic questions of functionality, portability and proprietary ownership. Take this example from a /. thread that you will be familiar with, and note how de Icaza's reply attempts to fudge the issue, resulting in a statement that contradicts itself (is Mono X or X+Y?):

      Mono is an implementation of the ECMA 334 and 335 standards which are available for anyone to implement (no patent strings attached, check the Mono FAQ for details).

      On top of that Mono implements plenty of class libraries: both the non-standarized class libraries from Microsoft, as well as our own universe of class libraries that take advantage of Unix-specific features.


      From a quick reading of this I'd infer that, great, "no patent strings" are attached and I'm in the clear. But a second look draws me to the Dotnet parts which are "non-standardized". Now might these not have been standardized by MS because it considers them proprietary, and hence likely to be protected by patents? de Icaza is being deliberately coy, but we know from Ballmer's statements that this is exactly MS's position and they are wholly opposed to free clones of their complete platform.

      I therefore do not accept that the true position is "common knowledge", or that Mono proponents are sufficiently upfront about the real situation.

      I'm glad that you are considering Python for your cross-platform development - Python is an excellent example of collective innovation and as such is much worthier of our support than Mono.

      However, I should point out that the commercial investment in Java on Linux exceeds that in Python by several orders of magnitude. While it's conceivable that a rationale for implementing a particular project in Python in preference to Java could be produced, given the wild uncertainties surrounding Mono I question whether a convincing rationale could ever be created for preferring it.

    30. Re:Call me stupid by Baavgai · · Score: 1

      The VB.NET was part of the initial plan. Visual Basic is just one of those things that most Windows programmers are reasonably comfortable with. It's non threatening.

      When Visual Studio came in, I did a simple Oracle client app in both VB and C#. The code was pretty much the same between the two projects. However, the differences between VB.NET and plain ole VB are monumental. It's really just a ruse to get stunted VB programmers to buy into .NET before they see what it entails.

      If you're going .NET, C# code is more concise and usable than what appears to be legacy VB support. The event support is clean, the class, interface, abstraction architecture is understandable. While none of the MS docs will mention the J word, in many ways C# is Java for Windows. .NET is OO at heart, it makes sense to talk to it in the OO language that was designed for it.

    31. Re:Call me stupid by Arakonfap · · Score: 1

      While you do have some points with parts of mono being "non-standardized", you forget that it'd be fairly straight forward to simply remove those parts, and not worry about it.

      You still havn't mentioned why you would feel safer using a 3rd party Java environment under Linux, when Sun may hold several patents on it. Or anyone for that matter.

      Also, as the above reply had also mentioned: Who is this "We", and "our", and "us" ?? You surely don't speak for me.

    32. Re:Call me stupid by alext · · Score: 1

      Straightforward to remove parts of the platform? For who? Not for the application developer - try telling Adobe, Autodesk etc. that they have to switch APIs from Windows Forms to GTK and see how straightforward they think that will be.

      Thank you for raising the position of a 3rd party Java environments on Linux. I'm not aware of any other message asking for such clarification, but if this is important to you you will find the legal position very clearly set out in the JCP documents. Needless to say, no equivalent program exists for Dotnet.

      If you use a Java environment from IBM or BEA, or the Blackdown source port, these are licensed from Sun. In fact, Linux is a tier-1 implementation for both commercial companies, and huge resources are invested in producing a solid platform.

      The bottom line is that 3rd party implementations for Linux are just some of the literally dozens of JVM implementations out there - determining licensing for Java is a pretty well-worn path.

    33. Re:Call me stupid by pmz · · Score: 1

      I get blank stares from programmers that want the equivalent of visual basic to work in.

      Hire better programmers. I hear there are quite a few to pick from, recently.

    34. Re:Call me stupid by TomV · · Score: 1

      However, the differences between VB.NET and plain ole VB are monumental. It's really just a ruse to get stunted VB programmers to buy into .NET before they see what it entails.


      Well, the Moftspeak for the difference between VB.net and C# is that VB is 'task-oriented' and C# is 'code-oriented', which I think means that C# is a better fit for modelling stuff that happens inside computer architectures - b-trees, linked lists, whatever, while VB.net is a better fit for modelling stuff that happens outside the computer (inventory control, workflow, payment processing). But each language is meant to be just as capable as the other at any of these tasks.

      A lot of my code-for-pay these last 7 years has been in VB/VBA, and when I started to play with dotNET it was VB.net. But I've actually moved to C# now, primarily because I still have to do a lot of VBA for work, and the ostensible but deceptive similarity between VBA and VB.net was becoming an issue - at least in C# I'm not constantly tripping over VB6-VB7 changes. And since it seems that I can make better money for the precise same skills if they're labelled "C#" rather than "VB.net" (the actual skill is knowing the Framework and understanding the CLR, nothing language-specific really) it would seem churlish to turn down the cash ;-)

      TomV

    35. Re:Call me stupid by Ciggy · · Score: 1

      1. Measuring speed is difficult, but to give you an example, the Mono C# compiler compiles itself on 3.5 seconds (50,000 lines of code).

      That means absolutely nothing...I've got a program that compiles in about 5 mins or 20 secs: it just depends whether I compile it on my 486/66 or my Athlon/800

      --

      A rose by any other name would smell as sweet;
      A chrysanthemum by any other name would be easier to spell
    36. Re:Call me stupid by Tim+C · · Score: 1

      If you're going .NET, C# code is more concise and usable than what appears to be legacy VB support.

      Here's an anecdote for you: A few months ago, I decided to teach myself Managed DirectX and C#. Searching around the web, I found a nice little tutorial in the basics of DirectX, written in VB.NET.

      So, I downloaded it, compiled it, and cofirmed that it ran correctly, before porting it to C#. Now, this was the first time I've ever used VB or any kind, other than a little VBScript a few years ago for some ASP work. It was also my first serious bit of C# code, although I've been a Java programmer for about 3.5 years. I concentrated on just getting the thing ported and running, ignoring (at the time) any optimisations of any kind.

      According to the app's own frame rate counter, performance increased by a factor of 10 - literally, it went from 70fps to around 700.

      in many ways C# is Java for Windows

      Agreed. To me, it feels like someone sat down, implemented their favourite bits of Java, added in some other things they thought were cool, then hit a thesaurus and started finding synonyms for keywords and concepts...

    37. Re:Call me stupid by xynopsis · · Score: 1

      I agree with you. In addition, I would like to point out that the free software QT toolkit does all of that even better!

      Multi-platform support: (*nix, windows, embedded,mac), native GUI, networking, you name it QT almost has it all. It even has this garbage collection thing, sort of. I find creating objects with QObject parents so convenient!

      Best of all, everything is in native C++ so your application IS a native program compared to apps written in C# or Java, which are basically semi-interpreted languages. IMO, I don't see any advantage why I should code apps in [C#/IL Code/CLR] and [Java/Byte-Code/JVM] environments when the free and easy to learn QT/C++ is around . Write once run anywhere? QT does that with a simple recompile.

  28. their problem is that they don't show details by SHEENmaster · · Score: 5, Insightful

    I can't patent "A Device that Catches Small Animals", but I can patent "An Improved Device for Capturing Small Animals by Use of Magical Cheese" in the hardware world. In the software world, I can go so far as to patent "Magical Cheese" without the recipe for said cheese or an investigation into my magical bacteria.

    We don't need to do completely away with software patents any more than we need to do away with all patents. We need to make both reasonable.

    By reasonable, I mean non-profit groups should be exempt, patents should last 2-5 years depending upon the technology involved, and nothing that significantly advances a previous technology should fall under that technology's patent.

    Patents should spawn innovation in exchange for the disclosure of the underlying technology. They shouldn't hold innovation hostage for decades to come.

    --
    You can't judge a book by the way it wears its hair.
  29. MS not helping .NET development now by GGardner · · Score: 4, Insightful
    Oddly enough, Microsoft is making it rather hard for third party developers to develop .NET applications, at least those that aren't only for in-house use. The .NET CLR does not yet come with any version of Windows -- you have to download the 25mb runtime yourself. There's still lots of dialup-speed users out there, and there's no way they are going to download a 25mb runtime just to run your app. I bet there's a lot of broadband users who would look askance at such a large download.

    Until .NET is installed on enough desktops, it is going to be difficult to justify developing distributeable applications with it.

  30. Article is old by rhysweatherley · · Score: 1

    The referenced article is old (11 Feb 2003), and refers to the patent *application*, not the patent itself. An application is not a patent - just the "inventors" hope that it will be one.

    Unless someone can produce an actual granted patent number for this, then it's still "nothing to see, move along" for the time being.

    -- Rhys Weatherley, author of DotGNU Portable.NET.

    1. Re:Article is old by exhilaration · · Score: 1

      If memory serves correctly, the USPTO will grant any applications and "let the courts sort it out". It's not really possible to perform searches for prior art any more.

    2. Re:Article is old by Anonymous Coward · · Score: 0

      er. ever heard of PATENT PENDING? current law says you can (must) defend it as if you already HAD the patent.

  31. Bass Ackwards by overshoot · · Score: 4, Interesting
    Thanks, and on the other side of the case, would it matter? As far as I'm aware, the courts have always allowed the copying of functionality/appearance, just not the methods used. Since this is a compatibility issue, I doubt MS would have a case anyways, unless the methods used to be compatible were the same as their patented methods.

    No, the courts have become very tolerant of patents with vague claims. A recent (upheld!) example is the patent on a credit-card-sized PDA, which was upheld as applying to a non-credit-card-sized PDA even though the patent didn't even describe how the small size was to be achieved.

    --
    Lacking <sarcasm> tags, /. substitutes moderation as "Troll."
    1. Re:Bass Ackwards by Dan+Berlin · · Score: 1

      This is actually a completely incorrect statement.
      The reason the court said that 3com could possibly infringe (all the federal circuit did was reverse the grant of summary judgement of non-infringement of the patent, due to the incorrect claims construction) is because the patent *didn't* specify that it was to be credit-card sized. It only specified that it was to be an "electronic multi-function card".

  32. Open Source Fear, Uncertainty and Doubt by werdna · · Score: 3, Funny

    The article appears to confuse an issued patent with a published patent applications, citing to one of the latter, recently published application 20030028685.

    The conditions necessary to obtain a published patent application are these: (1) file one and pay a filing fee, including the proper formal documents (like an inventor's declaration; and (2) wait 18 months. An application creates no presently enforceable rights, and none will accrue until the patent actually issues.

    Indeed, by beginning with the wildly broad claims (and they are pretty astonishing, I'll admit), any narrowing amendments entered during prosecution are likely to give rise to a much more limited patent.

    Let's not get hysterical before there is something to get hysterical about. The .mono plan for managing the inevitable patents, the plan so excoriated in the register article, is perfectly responsible and while risk is ever-present in developing interoperable code, perfectly workable. The fact of 18-month publication facilitates and permits actually permits present projects to begin early on its search for prior art.

    Fears regarding the quoted paragraph [0101] are misguided. It is routine boilerplate and primarily precatory, of virtually no importance concerning the meaning of the claims.

    I am told that some of these new decaffinated brands are just as tasty as the regular stuff. Let's not go nuts, at least not before there is a reason to go nuts.

    1. Re:Open Source Fear, Uncertainty and Doubt by werdna · · Score: 1

      But if I'm a developer (of any type) I'm thinking "OK, but how does this help me?" Claim 1 is so broad it covers EVERYTHING I DO. If the patent issues in present form - and MS decides to enforce it - I am sunk. Fear sets in.

      Look for prior art. Find it, and the fear goes away. Don't, and you should be properly concerned. You know what he is claiming, and if you can find art within the scope of a ridiculously broad claim, ideally your own, you are typically golden -- you will either invalidate the patent if it issues, or a narrower patent will issue that, under Festo, will not be entitled to protection under the Doctrine of Equivalents.

      Then the uncertaintly. I start walking the halls mumbling to myself, "Should I abandon 2000 hours of programming and completely change what I am doing, or assume the patent office will substantially reduce the claim?"

      A patent lawyer can help you in this regard. You have various options, including but not limited to putting art in the record. He can help you to evaluate your risk.

      Then I start a serious effort into self-delusion and convince myself that "the patent office would never issue such a broad claim."

      Then the doubt sets in.


      If you have the art, you are fine. If you don't, you are not. If you want to stay a cynic about the process, I can't help that, but it doesn't guide how others should govern their conduct. If you want to do something about it, be happy that you know NOW what is coming, and prepare for what you can do about it. This is one of the virtues of the 18-month prepublication rule.

  33. I can think of one reason by DuctTape · · Score: 2, Interesting
    But you still have not given me a reason to use it....In order to make the time investment it has to offer something better which it clearly does not.

    Um, a lot of companies in Austin have it on their "skill required" list, and the Austin outlook for paying jobs right now is close to zip-point-squat. That's a good reason.

    Perhaps it's the only reason. But it's still a reason.

    DT

    --
    Is this thing on? Hello?
    1. Re:I can think of one reason by codepunk · · Score: 1

      Now that is a interesting point you have made. I had a recruiter call me the other week, she also asked me if I had .net experience. Some company was needing someone to build a manufacturing system, something that I have a great deal of expertise in. I told her if they want to build a system out of software barely tested enough to be called beta I want nothing to do with it.

      --


      Got Code?
    2. Re:I can think of one reason by Kenja · · Score: 1

      Yea, insult your potential clients. Thats a great way to impress them. I bet they hired you on the spot.

      --

      "Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
    3. Re:I can think of one reason by codepunk · · Score: 1

      I said a head hunter, recruiter...they where a windows shop anyhow, not like I wanted to work for them. I don't do windows, you might as well be putting a gun to your head when placing trust in a MS product.

      Have you ever used MS transaction server? My point has been made.

      --


      Got Code?
    4. Re:I can think of one reason by Anonymous Coward · · Score: 0
      Have you ever used MS transaction server?

      Yes. Extensively.

      My point has been made.

      Really? And what was it again?

    5. Re:I can think of one reason by kannibal_klown · · Score: 1

      You, my friend, are rather lucky, and I envy you. You stick by your ideals and turn down jobs because you believe MS sucks. But I'm willing to "sell out" if it pays the rent.

      Not all of use have your luxury. At my job, we program for the Windows environment alone. Don't get me wrong, we use Linux and Solaris for backend stuff, but all front-end is Windows. We're recently starting to write some projects using .Net (mostly C#). Now, this is delegated to us from up-above. If we say ".Net blows, Java should be used" then they'd say "alright Chris, you're fired; Ernie, you're on the project now."

      In today's job market, most of us will learn/use what is marketable. Right now, MS products have a MAJOR majority holding over the IT departments of the country. I try to keep my options open; I'm beefing up my Java AND C# and .Net skills.

    6. Re:I can think of one reason by Malcontent · · Score: 2, Interesting

      There are plenty of Java shops out there and plenty of Java jobs. In fact there is anecdotal evidence that Java jobs outnumber .NET jobs by quite a bit.

      It all depends on what makes you more happy. Are you happy every day when you go to work or not? If you are going to be miserable coding in a windows environment then don't do it. The money is not worth it if you spend your entire day miserable and then come home and take it out on your family.

      --

      War is necrophilia.

    7. Re:I can think of one reason by Anonymous Coward · · Score: 0

      > there is anecdotal evidence that Java jobs outnumber .NET jobs by quite a bit.

      There is also anecdotal evidence that aliens regularly fly halfway across the galaxy to mutilate cattle. Numbers, please, not speculation.

    8. Re:I can think of one reason by kannibal_klown · · Score: 1

      For one, I don't mind coding for Windows; I'm rather sklled at it and comfortable with it. I just hope that the bottom doesn't fall out of Windows-based systems any time soon. But I am willing to migrate if/when necessary.

      As for jobs, 3 of my friends were let go last early last year. They were really bright, and good programmers (2 of which had good Java skills). 2 of them are still out of work. I (personally) would have to be pretty miserable to want to leave without another job waiting for me.

  34. C# is B-flat, not D-flat (NT) by Anonymous Coward · · Score: 0

    no text

    1. Re:C# is B-flat, not D-flat (NT) by Waffle+Iron · · Score: 2, Funny

      Thanks for the tip, Mozart. Looks like I need a new piano.

  35. dealin' with the devil by b17bmbr · · Score: 2, Insightful

    having never played with C!@#$%^&*() or whatever it is, i can't compare it to java. however, you're dealin with the devil. and when you deal with the devil, you're gonna get burned.

    <disclaimer> no, billyg and the boyz are not the devil, nor are they evil.</disclaimer>

    --
    My problem? I was perfectly gruntled, until some numbnuts came by and dissed me.
  36. .NET is not worth cloning by Junks+Jerzey · · Score: 4, Insightful

    Yes, sadly, many programs for non-MS operating systems, like Linux, are blatant clones of that from Microsoft. It's always been a bit ironic, but livable. But cloning .NET--as Mono--is by far one of the dumbest moves ever, and I mean that in a non-trolling way. At its heart, .NET is a way to break free from the aged Win32 API and old fashioned languages like C and C++. This is they key point of .NET, not web services. Now you can use Visual Basic-like forms from any language. Now you can have garbage collection. Now you can have true modules, not the FORTRAN-era separate compilation of C. None of this is new; none of this was invented by Microsoft. But is all so much better than building apps with MFC or raw Win32 calls. Windows programmers are flocking to .NET for this reason.

    But there are other ways to reach the same end. Python + a UI toolkit is a biggie. It's even more modern than C#, which is hopelessly mired in the 1990s philosophy of very strict object-orientation (Python is much looser in this regard). And it's interpreted, so you can incrementally build and test code, while still having all the same general benefits of .NET and C#. So anyone promoting Mono for Linux is putting their effort in entirely the wrong place. This is the one spot in which open source is already far superior, but for some reasons some zealots want to copy the inferfior solution, most likely just to spite Microsoft. What a complete waste of time.

    1. Re:.NET is not worth cloning by Tim+C · · Score: 1

      it's interpreted, so you can incrementally build and test code

      Unless your project is utterly huge or your machine really, really slow, there's no disadvantage to using a compiled language in this respect. (Even if your project is huge, it should be perfectly possible to organised it so that the bulk of it does not have to be recompiled every time.)

      Incremental build-and-test is how I've *always* worked, and I pretty-much only use compiled languages.

    2. Re:.NET is not worth cloning by Anonymous Coward · · Score: 0

      AFAIK it's only very recently that development environments for traditional compiled languages have begun to offer fix-and-continue, ie. the ability to fix the bug you just found, and continue the program from the state it was in. That's always been easy in interpreted environments (as well as Smalltalk and Lisp compilers which have been designed as interpreter replacements). Can you shed some light on whether a modern C++ development environment lets you study the program state by writing new data structure analyzing functions? That's something I've always found useful: when the program stops at an exception, and I suspect a likely reason for the problem, I don't go hunting for data corruption manually but write a function to do the hunting for me.

    3. Re:.NET is not worth cloning by IamTheRealMike · · Score: 2, Interesting
      But there are other ways to reach the same end. Python + a UI toolkit is a biggie.

      I think Python/PyGTK/PyGlade is great. But let's be realistic:

      • Python has no option for compilation, not to native code nor something that will be JITted. This has performance implications - yes, I know about Psycho.
      • Python has no optional static typing. There are PEPs for it, but as far as I know, so far none have been implemented.
      • The Python class libraries are inconsistant in style.
      • The Python syntax looks a bit wierd at first, to new developers.

      Now Python has many other plus points, and I somewhat suspect the battle for the future of open source developers hearts (at least on Linux) will be between Python and Mono/C#. But, right now, for larger projects it's looking somewhat weak. It *could* be a viable competitor with some more work, but right seems to be mostly confined to smaller projects, or developers who don't feel the need for the safety net of type safety.

    4. Re:.NET is not worth cloning by 16K+Ram+Pack · · Score: 1
      I don't know about Python, but having used PHP and ASP.NET, I know which I prefer.

      Sure, PHP is a little more work to get some things done like form callbacks, and you have to sometimes write 'protective' code, but once you get in the habit, they are no problem.

      The big thing to me is that ASP.NET doesn't feel simple, and that it doesn't feel as controllable to me. I certainly didn't feel any productivity gain over PHP.

    5. Re:.NET is not worth cloning by Tony+Hoyle · · Score: 1

      If your machine is really slow you wouldn't use .NET anyway... it sucks for CPU intensive tasks. Luckily you can call back into C++ for the good stuff.

    6. Re:.NET is not worth cloning by Malc · · Score: 1

      You sound like an application developer. Traditional applications mired in 1990s philosophies ;) Having worked with several server-side development languages and technologies, I have to say I quite like what ASP.Net offers. For some applications, an HTML based UI is sufficient, and that renders languages like Python moot, although there's no reason why the code behind a page can't be written in Python.Net (other than the compilers being experimental, IIRC). ASP.Net for Apache is a possible outcome of Mono, and beneficial to Linux.

  37. Who couldn't see this coming from a million mil... by dpilot · · Score: 1

    a million miles away, back on Day One when Icaza started talking up Mono?

    An eventual attack by Microsoft of some sort, be it fuzzily defined protocols, patents, or something critical they 'forgot' to document was inevitable.

    I actually figured that Microsoft would let Mono go on a bit longer before slamming the lid, and would have let the Linux community waste more effort and become more dependent on it.

    I had an optimistic hope that perhaps Icaza was clever enough to walk a tightrope and come up with an unassailable implementation for Mono. I didn't see how it could be done, but he's much more programmer than me, and perhaps clever enough.

    But what really stinks is that I have this cynical a view of Microsoft and their ethics.
    What stinks even worse is that generally believing the worse appears justified.
    We'll see what happens with Mono.

    --
    The living have better things to do than to continue hating the dead.
  38. Microsoft doesn't do that by Anonymous Coward · · Score: 0

    Microsoft is evil.

    But they have never used software patents offensively. Why should they start now?

    1. Re:Microsoft doesn't do that by Anonymous Coward · · Score: 1, Funny

      Ya, famous last words of Nintendo and Sega...

      "Microsoft doesn't do game consoles, why would they start now?!"

  39. P.S. by Overly+Critical+Guy · · Score: 0, Flamebait

    P.S. .NET can't be compared to other languages anyway because you can use any language in it. That's one of .NET's features.

    --
    "Sufferin' succotash."
    1. Re:P.S. by codepunk · · Score: 1

      Ok I will give you that it can run any language. So should I stop using python native and use python.net?

      I still see no payback and nothing but lock in.

      --


      Got Code?
    2. Re:P.S. by Overly+Critical+Guy · · Score: 1

      Then stick with Python native. Part of the point of .NET is that it is managed code. It has all the same advantages that a Java VM has in that regard.

      --
      "Sufferin' succotash."
  40. Let's just get this over with by puppetluva · · Score: 2, Insightful

    Why even bother speculating? It is not for anyone to decide but Microsoft.

    The community should ask Microsoft to issue a direct agreement and public announcement that they will not pursue patent attacks against Mono and DotGnu for any part of the .NET platform.

    If they won't do it, then the projects aren't safe and people have enough information to know to avoid them. Even if the lawsuits don't have merit, who wants to spend time in court that they could be spending on something more constructure (Like Parrot or OSS Java later this year if Sun follows through on its promise)

    Until they clarify their position (and theirs is the ONLY one that matters), I would just assume they are doomed.

  41. Longhorn by Overly+Critical+Guy · · Score: 0, Insightful

    Well, wait until Longhorn comes out, which will be using .NET for its interface, and Win32 will be replaced by it. Longhorn will be the big .NET push. The whole Windows system will be based on it (and by then people will be clamoring for a Windows upgrade, not to mention all the incredible features Longhorn is already boasting, so I imagine it will be a big seller).

    --
    "Sufferin' succotash."
    1. Re:Longhorn by Archie+Steel · · Score: 1

      Incredible features? What, you mean like wiggly windows? So far, Longhorn seems to be additional eye candy+a database-like filesystem. Now, Longhorn will maybe come out in 2005, maybe 2006. By then we'll have a db filesystem for Linux and Linux desktop will be able to match Windows (and OS X) eye candy...

      By the way, regarding your sig, you do realize that it does not mean a net gain in favour of Windows, right? The statistic published on Netcraft's site is that 5% of the new Windows 2003 Web servers online were previously running Linux. Now, that number is practically the sole result of a single web hosting provider who switched to Win2K3...however, I'll bet you that waaay more than 5% of all new Linux servers were formerly Win2K/WinXP machines.

      The amount of spin put on that statistic is enough to shame the most seasoned Washington politicians - while in fact, the truth of the matter is that only 5% of the new Win2K3 servers come from Linux - and 90%+ come from previous Windows OSes. Since there are only 185K Win2K3 servers, that represents about 9250 servers (out of 43 millions, or 0.02%) switching. So in fact what it tells us is that those who've got Linux web servers are not rushing to change them to Win2K3...

      So, indeed, Linux servers are switching to Win2K3, Windows servers are switching to Linux, Solaris servers are switching to Linux, Linux servers are switching to NetBSD, the sky is blue, fire is hot, things fall down when you let them go, and so on...

      --

      Reminder: find a new sig
    2. Re:Longhorn by Overly+Critical+Guy · · Score: 3, Informative

      Nice. For some bizarre reason, someone modded my post as a "Troll."

      Incredible features? What, you mean like wiggly windows?

      I mean vector-scaled, hardware-accelerated graphics. An abandonment of Win32 for .NET. A restructuring of the concept of files, getting rid of "drive letters" and such. Everything from the ability to add and remove RAM without rebooting, to XML scripted modular custom installations. Go to WinSuperSite and read the Road To Longhorn Part 2 for a full list of all the features, to many to list.

      So far, Longhorn seems to be additional eye candy+a database-like filesystem.

      Well, then you clearly haven't even bothered reading up on it.

      Now, Longhorn will maybe come out in 2005, maybe 2006. By then we'll have a db filesystem for Linux and Linux desktop will be able to match Windows (and OS X) eye candy...

      I doubt it. Not as long as we're stuck on X11 + xlib + window manager + desktop environment + conflicting windowing libraries and inconstent interfaces.

      * snip three reactive paragraphs about my sig *

      --
      "Sufferin' succotash."
    3. Re:Longhorn by Anonymous Coward · · Score: 0

      Ah, exposing bullshit is reactive now, is it?

    4. Re:Longhorn by Tim+C · · Score: 1

      Yes, it is - he reacted to the guy's sig. That's reactive by definition, whether the sig is bullshit or not.

    5. Re:Longhorn by Tony+Hoyle · · Score: 1

      Abandonment of Win32 and drive letters? Yeah, I'll believe it when I see it...

      Heck, there are still enough DOS apps out there that Windows still needs to support it, let alone Win32 apps - it'll take decades to get to the point that they can get rid of Win32 (not that it makes any sense to do so - .NET is a pseudocode language that runs on top of Win32, not a replacement).

    6. Re:Longhorn by Archie+Steel · · Score: 1

      Indeed I did. Bullshit provokes a reaction in me. Actually, I don't care that he called my paragraphs reactive, but the fact that he didn't bother to defend it is telling...

      --

      Reminder: find a new sig
    7. Re:Longhorn by Archie+Steel · · Score: 2, Insightful

      I mean vector-scaled, hardware-accelerated graphics.

      That's what I said: eye candy. Well, this is coming to Linux as well, though in my view it really is icing on the cake, and nothing more.

      An abandonment of Win32 for .NET.

      So I guess the Longhorn version of MS Office will run on Linux (+mono) after all!

      A restructuring of the concept of files, getting rid of "drive letters" and such. Everything from the ability to add and remove RAM without rebooting, to XML scripted modular custom installations.

      Apart from hot-swapping RAM (and this one I'll believe when I see it), these are not revolutionary changes. If there is a demand for them, you'll see them in Linux before Longhorn comes out.

      Go to WinSuperSite and read the Road To Longhorn Part 2 for a full list of all the features, to many to list.

      I'm sorry, but I don't consider Paul Thurrott to be a reliable source of information. Working in the software industry, I've long since learned to be careful of hype-spouting, FUD-spreading "advocates" such as he.

      "Now, Longhorn will maybe come out in 2005, maybe 2006. By then we'll have a db filesystem for Linux and Linux desktop will be able to match Windows (and OS X) eye candy..."

      I doubt it. Not as long as we're stuck on X11 + xlib + window manager + desktop environment + conflicting windowing libraries and inconstent interfaces.


      The usual X11 myth, in other words. But in fact, even though some people experience performance issues with X11, the fact is that it's not a broken model, but rather one that is both solid and evolutive - especially since it's not tied to the Window Manager/Desktop Environment. In effect, enhancements to one part of the equation affects the entire experience, and the competition between DEs has dramatically sped up their refinement and the incorporation of new features (or I should say streamlining, in the case of GNOME).

      Oh, and nobody really cares about "inconsistent interfaces": I mean, Windows has had them for years, and no one has been complaining! The fact is that it's relatively easy to theme apps so that their widget sets and icons all have the same appearance. In other words, it's a false problem, repeated ad nauseam by those who feel threatened by Linux's slow but irreversible march on the desktop.

      * snip three reactive paragraphs about my sig *

      Yes, that was reactive, but you should expect this when you troll with your sig. I saw BS, I called it, you didn't bother to try defending it. That's really all there is to say about it...

      --

      Reminder: find a new sig
    8. Re:Longhorn by Overly+Critical+Guy · · Score: 1, Troll

      That's what I said: eye candy. Well, this is coming to Linux as well, though in my view it really is icing on the cake, and nothing more.

      Vector-scaled graphics are not eye candy. It allows resolution-independent displays where everything is the same size regardless.

      So I guess the Longhorn version of MS Office will run on Linux (+mono) after all!

      Doubtful.

      Apart from hot-swapping RAM (and this one I'll believe when I see it)

      Windows Server 2003 already allows you to add RAM without rebooting. Longhorn will allow both adding and removing.

      these are not revolutionary changes. If there is a demand for them, you'll see them in Linux before Longhorn comes out.

      I'm sure there will be demand for them once Longhorn comes out.

      I'm sorry, but I don't consider Paul Thurrott to be a reliable source of information.

      Why wouldn't you consider him a reliable source of Windows information? Considering he has actual sources inside Microsoft and all. Most of his Longhorn information is from the WinHEC, complete with screenshots. You're just being difficult to be difficult.

      Working in the software industry, I've long since learned to be careful of hype-spouting, FUD-spreading "advocates" such as he.

      Oh, please. I don't care about your "working in the software industry." The guy has his information from sources inside Microsoft. He's a well-known Windows guy, announcing betas and codenames before anyone else knows them.

      The usual X11 myth, in other words.

      It's not a myth. There are tons of windowing libraries and interface inconsistencies, all running into each other. This has already been admitted by many people before me.

      But in fact, even though some people experience performance issues with X11, the fact is that it's not a broken model, but rather one that is both solid and evolutive - especially since it's not tied to the Window Manager/Desktop Environment.

      In other words, performance is broken, but it works, so keep it!

      "Evolutive"...?

      Oh, and nobody really cares about "inconsistent interfaces":

      Yes, they do.

      Heck, read up on GNOME's infamous save dialog sometime. Or Xine's open button ("://").

      I mean, Windows has had them for years, and no one has been complaining!

      Windows apps look the same, with standardized interfaces. It's a gamble when you use Linux desktop apps. One might use Motif, another GTK2, another QT1, and so forth. Again, you're being purposely disagreeable because you don't want to cede a point.

      The fact is that it's relatively easy to theme apps so that their widget sets and icons all have the same appearance.

      What does that have to do with poorly-designed, conflicting interfaces? XP can skin its widgets too.

      In other words, it's a false problem, repeated ad nauseam by those who feel threatened by Linux's slow but irreversible march on the desktop.

      Someone who dismisses criticism so easily is a perfect example of exactly why Linux's march on the desktop is very, very slow and only occuring within Linux advocate circles. It will never become mainstream at its current position. The Linux desktop needs a radical changeover, because KDE and GNOME aren't gonna cut it. But I guess having tons of apps starting with "G" or "K" is good enough to pass your desktop standards test.

      Yes, that was reactive, but you should expect this when you troll with your sig. I saw BS, I called it, you didn't bother to try defending it. That's really all there is to say about it...

      I don't need to defend it. Numbers speak for themselves. How am I trolling by merely linking to an article that states the same thing? If I were really trolling, you'd know it clearly.

      --
      "Sufferin' succotash."
    9. Re:Longhorn by Archie+Steel · · Score: 2, Insightful

      "So I guess the Longhorn version of MS Office will run on Linux (+mono) after all!"

      Doubtful.


      How so? If Office Longhorn uses .NET, shouldn't it run on other .NET platforms? Isn't .NET a java-like "write once, run anywhere" scheme?

      Why wouldn't you consider him a reliable source of Windows information? Considering he has actual sources inside Microsoft and all.

      This is exactly why I don't consider him reliable: he is much too close to Microsoft to be objective. In other words, he often (IMO) acts as a MS hype machine.

      Oh, please. I don't care about your "working in the software industry." The guy has his information from sources inside Microsoft.

      As I said, he gets in info in exchange for building up the hype.

      's not a myth. There are tons of windowing libraries and interface inconsistencies, all running into each other. This has already been admitted by many people before me.

      It is a myth. The fact that it's been repeated over and over doesn't make it true. BTW, interface inconsistences have nothing to do with X itself.

      In other words, performance is broken, but it works, so keep it!

      Performance isn't broken - some distros don't set it well, that's all. You just have to be sure it's "niced" at -10, and it is very snappy. Also, responsiveness has got as much to do with the kernel as with X proper. With 2.6, the desktop flies - and I can still use my old Pentium 166 as an X term for my roommate - something I couldn't do with Windows.

      Windows apps look the same, with standardized interfaces.

      Not true. Compare the Windows Media Player, Winamp and RealPlayer. They all have different interfaces. Compare Lotus Notes to Outlook. Compare Office 97 (which people still use) to Office XP. I could go on with programs that have interface inconsistencies. Adobe Acrobat Reader. WinZip. ACDsee.

      It's true that KDE apps, while very consistent between them, are different that Gnome apps, but only marginally. Which is why someone who used KDE will more often than not tend to use KDE apps, and so on. But the "inconsistent interface" is a very minor issue. As I have said, there are lots of inconsistencies in Windows, and people seem to manage nonetheless.

      Someone who dismisses criticism so easily is a perfect example of exactly why Linux's march on the desktop is very, very slow and only occuring within Linux advocate circles.

      I do not dismiss relevant criticsm easily. I will, however, dispel myths that are repeated over and over by anti-Linux advocates. BTW, Linux's deployment on the desktop is picking up in speed, especially outside of the U.S.

      The Linux desktop needs a radical changeover, because KDE and GNOME aren't gonna cut it.

      I disagree. Right now, the KDE desktop is actually superior to the Windows Desktop as far as functionalities go. The Gnome desktop is less featureful, but it may be better for new users because it looks less like Windows, and therefore new users don't expect it to behave exactly like Windows. At least that's what recent experiments tell us. One thing is constant, though (and this I've verified with friends and relatives): people adapt very quickly to the Linux desktop, and don't find it lacking compared to Windows. So, no, no radical changeover needed, just continued development and refinement.

      I don't need to defend it. Numbers speak for themselves.

      But what do the numbers say, actually? Do they indicated a net migration from Linux to Windows? In fact, they do not. What the numbers say is that only a small fraction of new Win2K3 servers come from Linux. Indeed, you do not say otherwise in your sig, but the way it is written seems to indicate such a loss for Linux.

      How am I trolling by merely linking to an article that states the same thing? If I were really trolling, you'd know it clearly.

      The a

      --

      Reminder: find a new sig
    10. Re:Longhorn by pmz · · Score: 1

      A restructuring of the concept of files, getting rid of "drive letters" and such. Everything from the ability to add and remove RAM without rebooting, to XML scripted modular custom installations.

      Nice, that Microsoft is catching up to where UNIX was years ago.

      BTW, it is extemely likely that the RAM removal neato-nifto feature requires hardware support (i.e., no $499 Dell will allow it...more like a $5,500 IBM, at least). It is absolutely amazing how Microsoft's marketing leads people to believe they have things when they really don't (sort of like flawless DOS support in Win 95).

  42. This is probably not the answer you expect by jsse · · Score: 5, Insightful

    As someone who's worked in Java for for over 5 years, I welcome C# and it's buddies to the OpenSource world.

    I highly recommend you stick to Java.

    All our major projects are developed under J2EE and we first use Tomcat as it's free. Later we switched to BEA because it has better performance; years later we changed our deployment to Oracle App servers for Linux because Oracle offered some attractive discounts for their Linux initiatives. We saved huge amount of operational/maintenance budge in switching from UNIX/Windows to Linux.

    All of the migrations took us very minimal efforts because all J2EE platforms are pretty much agree on the same standard. Sweet isn't it? :)

    I don't think you've such a freedom in .NET platform, and I don't see it's justifiable to implement .NET on Linux than Windows. You're right that MS is holding the balls of Mono and they could do whatever they like with it. So, why take the risk?

    (Ok Ok, I know SUN is holding the balls of others with that J2EE certification, but you can see their difference. :)

    1. Re:This is probably not the answer you expect by samwhite_y · · Score: 1
      There is seems to be a belief that C# plus .NET is equivalent to Java and J2EE. Although there are a lot of similarities, one of the big differences that sticks out is that C# encourages you to use native APIs on a particular operating system. The concept of "pure C#" is not as meaningful an idea as it is for Java. Although you might be able to write a solution at an abstraction layer that allows portability using C# and .NET, the language and environment encourages you to write applications that target a specific platform. For example, .NET has a lot of things in it to manage interfaces to natively implemented third part libraries.

      The reason why I would prefer C# and .NET on Linux is that I can write a C++ style application using native Linux calls with far less hassle than with Java. For example, I can use native X-window concepts and calls instead of going through some ridiculously slow "swing" abstraction with horrible dialog popup focus handling problems. If I have a native implementation of some encrytion standard, communication standard, or file system locking standard, they are much easier to access through C#. For me, C# is the perfect language if you already were thinking of writing a native application for a specific environment but you wanted some of the many advantages of "hot-optimized-compiled/linked-scripting" language.

    2. Re:This is probably not the answer you expect by Anonymous Coward · · Score: 0

      why don't you use the native interfaces of java?

    3. Re:This is probably not the answer you expect by samwhite_y · · Score: 1

      The big problem with JNI interfaces is that you have to build new binary code specifically to interface between Java and the native library. On top of that you have to deal with version incompatibility issues (what if the library you are talking to is a growing and changing thing), delivery issues (where do I put these JNI interfaces), configuration issues (how do I make sure that the Java picks up the appropriate JNI interfaces), and debugging issues (when the thing crashes -- I have one more place to look). The cool thing about C# is that you can call native methods in a dynamically loadable native module directly from C# (in a manner reminiscent of Visual Basic calling methods in DLLs). It makes the language a lot less safe in some respects, but it is sure convenient if you are already committed to being partially native. C# does not force you to use a level of abstraction away from the native C-style structures and function calls (at least in the Microsoft implementation).

  43. MS Is Definitely Protected by _iris · · Score: 1

    While they might not be able to use these patents to protect themselves, they definitely have some way to protect their investment in .NET. They have some way to prevent open source implementations of .NET from becoming the de facto standard. They have some way of preventing threatening uses of .NET in open source software. They stand to loose too much of their investment in .NET.

    1. Re:MS Is Definitely Protected by modme2 · · Score: 1

      and in their own words they "bet the company on .NET" - so it's a significant investment.

  44. Where is mono, /Dot/GNU based? by incom · · Score: 1

    If it is based outside of the US, can software patents still effect them?

    --
    True genius is grasping a situation like a peice of fruit, and peircing it just right so that it drains dry.
  45. So... by Joel+Carr · · Score: 2, Insightful

    I'd appreciate comments from IT lawyers / solicitors and individuals with experience in this area, as well as from the wider community.

    In other words...
    They're seeking comments from absolutely everyone.

    ---

    --
    Any man who can drive safely while kissing a pretty girl is simply not giving the kiss the attention it deserves. -- AE
    1. Re:So... by Anonymous Coward · · Score: 0

      including trolls it seems!

  46. NO PATENT EXISTS! by SiliconEntity · · Score: 4, Informative

    The Register article is pointing at a patent APPLICATION. Despite their comment, "But an umbrella claim that protects its .NET APIs, granted last week, highlights the extent of its determination to protect its interfaces," I don't see any patent granted last week.

    It remains to be seen whether the .NET API is even patentable. Certainly claim 1, as written, is not patentable: "1. A software architecture for a distributed computing system comprising: an application configured to handle requests submitted by remote devices over a network; and an application program interface to present functions used by the application to access network and computing resources of the distributed computing system." There are a zillion systems out there that match the terms of this claim precisely. So it is hardly novel.

    In fact the whole patent application is written so poorly that I can't see it being granted in anything like its present form. Maybe there is a way of patenting an API but this ain't it.

    1. Re:NO PATENT EXISTS! by Malcontent · · Score: 1

      ".NET API is even patentable."

      It can't be patentable because Java is prior art.

      --

      War is necrophilia.

    2. Re:NO PATENT EXISTS! by American+Patent+Guy · · Score: 1

      OK. Maybe claim 1 is invalidated by the prior art. But what about the remaining claims? Claim 1 in an application is often too broad; the other claims may be patentable and may provide MS the coverage they need. Also keep in mind that the original claims in the application can be changed in prosecution (and probably will). Better check again when the patent is issued...

  47. The other side of the story by torre · · Score: 2, Insightful

    Since every post here seems to thinks doomsday is unavoidable when using MS ideas on other platforms, may I remind everyone that you don't have to follow them to the letter!.
    I mean, they opened up the basics that open up the platform, but does Linux/anything else really need WindowsForms/ASPX/ADO.NET/Whatever else that's not covered?
    Imitation is nice, but I'm assuming that there are other ideas that can be explored and potentially take a twist for the better?... really, The beauty of the whole thing is if you write your own stuff that isn't legally ambiguous then you control where it can go so instead of a windows focused WindowForms you can have a Windowing library that is more generic and say works across several platforms and perhaps even windows... So, instead of ASPX you could hook up an "enhanced" PHP, use another dataset API instead of ADO and write a better windowing api, and that way your on stable legal terms instead of taking risks on ambiguity.
    Mono's approach is somewhat on the right direction, they're basically copying down to the letter (with some creative license) and if a legal issue appears they'll just change the affected parts.
    But that's just my 2 cents.

    1. Re:The other side of the story by Anonymous Coward · · Score: 0

      Since every post here seems to thinks doomsday is unavoidable when using MS ideas on other platforms, may I remind everyone that you don't have to follow them to the letter!.

      Well, as far as I can tell, the only benefit to having an open source .NET implementation on is the ability to run binary .NET applications written using Microsoft tools on non-Microsoft platforms using open-source tools. This requires complete support for all of the proprietary Microsoft APIs.

      If you just want something "sort of" like C#/.NET, well, Perl, Python, Ruby, PHP, gcc, and others are all open-source implementations of programming languages which are, in various contexts, superior to C#. And there is Java, which C# is based on, that is not really open source but works on most platforms.

    2. Re:The other side of the story by Anonymous Coward · · Score: 1, Interesting

      What will Novell do if MS threatens to sue them for a couple billion $ similar to what SCO tries with IBM? What makes you think that Novell won't drop Mono like a hot iron? Remember how Novell vice chairman Chris Stone said in an interview "We just hope Microsoft isn't against the idea." With dotGNU being based outside the US, that project has much better chances to weather any storms that M$ might throw against them.

  48. GNOME distribution with Mono is *STILL* DANGEROUS by NZheretic · · Score: 2, Interesting
  49. Re:MS not helping .NET development now by bmajik · · Score: 3, Informative

    this is incorrect. The .NET runtime version 1.1 comes with Windows Server 2003.

    I am probably wrong on this, but i think the .NET Runtime version 1 comes with certain packagines of Windows XP (tablet PC, perhaps ? Media Center ?)

    the runtime is getting out there. More and more things will start to require it. .net is seeing admirable deployment on the server side. However, unlike java, it is also seeing some real-world apps on the client as well.

    --
    My opinions are my own, and do not necessarily represent those of my employer.
  50. Re:MS not helping .NET development now by Chester+K · · Score: 1

    The .NET CLR does not yet come with any version of Windows

    I thought for sure it came with Windows Server 2003. And I'd be honestly surprised if it's not included in the post-SP2 copies of XP.

    --

    NO CARRIER
  51. Oh yeah. 25MBs is way too much. by Anonymous Coward · · Score: 0

    In this day of trading MP3s, and downloading ISOs of your favorite Linux, 25MBs is far too much. (Sarcasm)

    1. Re:Oh yeah. 25MBs is way too much. by Trejkaz · · Score: 1

      For a comparison, Java's runtime is 13Mb and users *always* complain about that.

      --
      Karma: It's all a bunch of tree-huggin' hippy crap!
  52. If you have doubts, just trust the company. by Anonymous Coward · · Score: 2, Funny

    In so many of these issues regarding Microsoft Corporation put your fears aside as you are dealing with a company of the highest intellectual and moral fiber. Why would you darken the clear waters of healthy cooperation with trivial concerns over self preservation or fair treatment. Never doubt your continued prosperity, aren't they the most wealthy company in the world? Why would the begrudge you a small fortune when they have so much?

    The United States Department of Justice Under the watchful gaze of our Kindler Gentler president will protect you in the event there is some sort of oversight. They won't turn coat at the change of an election and shirk their duty to protect the balance of the American Markets.

    As a small business or individual you can put your fears at rest. Don't trouble yourself to read too deeply into what Redmond says.

    Software is about organized data after all. Its systems are the expressed will of those who design and promote it. And since it is all about connectivity the largest interests must be the most connected. They must recognize their moral responsibility to bring people together cheaply, reliably and openly. They bear the burden of democracy that communication should not be clandestine but open and meaningful. This must be the honorable road of the greatest hero of the marketplace, the most democratic of companies, a organization that the United States is proud of.

  53. Shouldn't he comprehend now? by Anonymous Coward · · Score: 0

    After all the trouble Sun did to Microsoft regarding their own implementation of Java. MS should be less restrictive when others are using their technologies.

  54. There is one thing that I know.... by Eric+Damron · · Score: 2, Insightful

    I don't know if Microsoft will use its patents to crush the MONO project but it may be an option. That should be enough to give the developers of MONO pause.

    There was an anonymous coward who posted claiming to be a lawyer who said that these patents wouldn't effect MONO but he didn't elaborate. I have got to be skeptical.

    The bottom line is: It is never a good idea to give Microsoft the option of crushing you. No one really knows what Microsoft will do except whatever it is, it will for sure be in their own best interest.

    --
    The race isn't always to the swift... but that's the way to bet!
  55. My answer to you:... by pVoid · · Score: 0, Redundant
    IANAL.

    I'm surprised to not see any IANAL posts up till now.

  56. Re:Who couldn't see this coming from a million mil by Anonymous Coward · · Score: 0

    Get real... a schoolboy could program better than that guy. He's an idiot.

  57. Parrot vs Python by cpeterso · · Score: 5, Interesting


    Dan, the author of the Parrot VM, has a bet with Pythong's Guido van Rossum. Dan bet Guido that Parrot can execute pure Python bytecode faster than the Python interpreter can. The battle will be decided at OSCON 2004 in Portland, OR. He sounds pretty confident:

    "Boys and girls, let's get this straight. I'm only going to say this once. Parrot is an order of magnitude faster than perl 5 doing equivalent things. Without enabling any extraordinary measures. You know how Python's performance rates against Perl 5. Do the math."

    Dan's blog entry about the bet: http://www.sidhe.org/~dan/blog/archives/000139.htm l

    1. Re:Parrot vs Python by Anonymous Coward · · Score: 0

      Dan is not the "author" of Parrot. His code makes up less than 20% of it. By code contribution Leo is clearly the "author" of Parrot. The project was floundering badly with serious design problems (and lack of code) until Leo stepped in.

    2. Re:Parrot vs Python by Anonymous Coward · · Score: 0

      And Larry's responsible for far less than 20% of Perl 5. Your point?

    3. Re:Parrot vs Python by Anonymous Coward · · Score: 0

      Hi Elian, umm, Dan! My point is that you have no idea what you're doing. But that's okay - Leo's picking up the pieces and doing just fine. Watch what he does - maybe you'll learn a few things on how to design and manage a software project.

  58. from the do-you-trust-Redmond dept. by rolocroz · · Score: 1
    from the do-you-trust-Redmond dept.
    I sure hope that's a joke!
    --

    I meta-mod all positive moderation Unfair, because it's abuse of the system.

  59. I expect Microsoft's code to be in the patent by SlashMaster · · Score: 1
    The spirit of patent law is to reward those who innovate by protecting them from competition in exchange for making their idea/technology public.


    This person's publically available patent information is then provided for the public good to facilitate technological innovation in our country.


    ( Allows others to learn about that technology ).

  60. Re:Older coders welcomed where needed by Graff · · Score: 1
    Too bad the people at PARC did't patent the idea of a graphic windowing operating system.

    They did. They waited too long to enforce the patents. Xerox totally bungled their chance to become Microsoft.

    Totally untrue. Xerox was paid by Apple for the right to use some of their ideas. To see the real story, go here. Here's a quote for you:
    Jobs was so hot on the concepts of UI, and the living Demos he say, that he, later, negotiated a deal with Xerox. He gave Xerox a large sum of stock in Apple (worth Millions) if he could come back, and bring some programmers -- to inspire them more on the concepts of GUI. This was like a one-day tour. This was agreed to by Xerox, and so by no stretch of the imagination could this be called "ripping-off".
  61. Mono? by pyrrhonist · · Score: 2, Funny
    Can Recent MS Patents Affect Mono and DotGNU?

    You'll all be relieved to know that you cannot get mononucleosis from Microsoft patents:

    Mono is not spread as easily as some other viruses, such as the common cold. The mono virus is found in saliva and mucus. It is usually passed from one person to another through kissing, although it may rarely be passed in other ways, such as coughing.
    Huh?
    Mono's an open source software project you say?
    Oh, that's a whole different thing then. Nevermind.
    --
    Show me on the doll where his noodly appendage touched you.
  62. Java Rocks by Anonymous Coward · · Score: 0

    I have been coding in Java for last 7 years and Java platform just rocks. Just with JDK 1.4.1 things looks better than any gui on client side. On server side Java beats .Net hands down.

    Largest Java Installs are: EBAY, HomeDepot, Wallmart, Nokia, Sony, AA, SWA, all insurance compannies, UPS, Fedex etc

    There free server available like JBOSS, Apache, JoANS

    ID: Elipse, Netbeans, JEDIT.

  63. It would be difficult for you to be more wrong by Anonymous Coward · · Score: 0

    See Waffle Iron's comment for a more amusing rejoinder. But I figured I should put this in for all the people that only read the subjects...

  64. The more I think about this... by Gojira+Shipi-Taro · · Score: 1

    the more I think a mass eruption of the entire chain of volcanoes surrounding Redmond would be less-than-tragic.

    --
    "Oh my God. This is terrible. This is the end of my Presidency. I'm fucked."; ~ Donald J. Trump
  65. Lifeblood of software patents is ... by Jerry · · Score: 1
    MONEY! Who do you know that more of it than anyone else?


    Gates has plenty of it and there are folks in high places willing to sell their mothers for it, so don't expect software IP patents to go away anytime soon.


    The question Linux coders who want to continue using MONO have to ask themselves is: "Do I have enough money to defend myself against an MS lawsuit?"


    If so, then the next question is "Will the 9th Circut court of appeals throw out a win I might have and give the decision to MS?" Or, put another way, "IF Boise and the DOJ can win against MS but get their victory thrown away by "negotiations" in the appeals process, what chance do I have against MS and 6 of 9 Judges who attended a workshop at George Washington University designed to reveal ways to neutralize the US anti-monoply laws?"


    Forget .NET and get a reality check. It was De Icaza's pipe dream but there is no way MS will let OpenSource or Linux benefit from it.

    --

    Running with Linux for over 20 years!

  66. apples and oranges by Anonymous Coward · · Score: 0

    So Dan codes up some contrived Parrot assembler benchmark using 32 bit integers and compares it to Perl 5 using scalar values - it's no comparison because it's like apples and oranges. It proves nothing. Once you use PMCs for scalars in Parrot for Perl - all bets are off. All those quick integer ops will now have to be called via a much much slower vtable methods. The speed will then be roughly the same - that's assuming Parrot ever implements Perl or Python, of course.

  67. What Total Bullsh*t by bratmobile · · Score: 0, Flamebait

    So, Microsoft submits C#, the CLR, and the System.* assemblies to the ECMA standardizations process. (Far, far more than Sun has EVER done with Java.)

    And Slashdot has any reason to complain? Boo fucking hoo that Microsoft didn't submit EVERY LINE OF CODE THEY HAVE EVER WRITTEN to ECMA.

    The attitude of the original poster is that of a whiner. Microsoft gives you something for basically free (a decent spec for a decent language/runtime), and you WHINE that they didn't give you more.

    Boo fucking hoo. Grow up.

  68. Patents enforced by m00nun1t · · Score: 2, Informative

    A complete list of Microsoft owned patents that have been the basis for legal action from Microsoft against a third party:

    1.

    Thankyou for reading.

    Tongue in cheek, and I know this needs to be considered as part of risk planning, but as far as I'm aware, there has never been legal action based upon patent infringement from Microsoft - and not from lack of opportunity I suspect. Give some credit where credit is due.

  69. Embrace and Extend? by chickenwing · · Score: 1

    Maybe we can subvert .Net by offering our own .Net implementation. We could attract IT managers by adding the extra eye-candy that they desire over the Microsoft product.

    We could get into a battle with us going tit-for-tat with Microsoft over which implementation had the the most masturbatory features. This would totally distract Microsoft from the real issues and force them to add all kinds of useless cruft to their product. Then eventually the whole .Net thing would collapse under its own weight.

  70. Waiting for the Java patent stories by zjbs14 · · Score: 3, Interesting
    Still waiting for the front-page stories about the dozens of patents Sun holds on Java and its related technologies. Especially the one that applies to any three-tier database applications written in Java (5,899,990).

    Guess I shouldn't hold my breath.

    --
    No sig, sorry.
  71. Does MS want/need developers anymore? by Latent+Heat · · Score: 4, Insightful
    Patents could be used to tie mono/.Gnu up in knots. The idea is that if you develop for .NET/Windows you should be darned well tied to Windows instead of traipsing off into Linux or whatever.

    OK, Windows is Microsoft's flagship OS, and they want to defend their turf. So, lets say developers and their customers pay MS the required tithe. If you play this software game too far, is there any room for little-guy developers of even Windows itself?

    When MS started out with DOS and then with Windows, I think they went to great lengths to get "mindshare" of developers: MSDN, Visual Basic for applications programmers, VC++ for heavy-metal programmers, and so on. And then you had all the "third parties." Where would the PC have been without Lotus 123? Where would programming languages on the PC be without Borland? It is said that MS treatment of developers is what sunk OS/2. IBM was charging an arm-and-a-leg for OS/2 development tools at a time when MS was handing tools out at conferences to get developers to forgo OS/2 and develop for Win32.

    But a good part of MS was that they fostered 3rd party developers, but when you got big enough they either bought you out or squashed you.

    So having good developer relations was important to the growth of Windows and Microsoft, and the fact that there were a lot of people besides Microsoft writing apps for Windows was part of what was so great about Windows, especially since early iterations of Microsoft compilers, spread sheets, and other apps were pretty lame.

    But now the development tools all cost an arm and a leg, and with software patents as a club, what size developer will Microsoft tolerate. If you are selling a recipe program written in VB to a handful of friends, you will be off the radar, but at what market size does MS these days decide they want all of that market.

    More importantly, if independent software developers are all put out of business through the enforcement of IP, how is MS going to develop new markets through their usual strategy of buying out or squashing out the pioneers. MS has in the past been pretty clumsy in all their attempts at new markets and has depended on acquisition (can you say Anders Hejlsberg? I knew you could!).

    Besides choking off small developers, at what point is MS going to shoot themselves in the foot?

    1. Re:Does MS want/need developers anymore? by Anonymous Coward · · Score: 0
      can you say Anders Hejlsberg?
      Actually, no.
  72. JBuilder, C++ Builder, Delphi, and VS .NET by Latent+Heat · · Score: 1
    Is JBuilder the most Visual-Basicy Java IDE out there?

    I think the JBuilder slows can be partly attributed to Java Swing.

    I am old (learned Pascal in a course taught by Brinch Hansen back in the 70's) and am comfortable with Pascal. For a Visual-Basicy experience with a compiled language, Delphi rocks. Do others have experience with C++ Builder?

    I "discovered" that VS.NET saves design-time properties in code while the Borland setup saves it in files (as in persistent objects that save themselves to streams). It took me a long time to figure this out because VS.NET hides the code that expresses design properties unless you click the outline expansion box: it took lots of Googling to find this out as MSDN is really frustrating in explaining such stuff.

    I guess I like expansion of design properties into code in that I like to code to fully explain what a program is doing rather than relying on some "magic" tied away in a hidden data file somewhere (I was influenced in this prejudice by Brinch Hansen's opinions on side-effects in programming systems).

    On the other hand, the code method presents "round-trip" problems, especially if someone ignores the warning comments and changes some of the code. If you drop an untested widget on to a form, you can bugger up the code when trying to remove a widget that crashes the designer by trying to edit code. I also think the design properties in a data file approach makes it easier to hook into the saving and retrieving of properties to implement custom property data types -- with the code approach you have to tinker with code parser objects (Document Object Model parser objects) which is beyond my skills at this point.

  73. A quick bet... by MosesJones · · Score: 1


    Microsoft will announce "updates" to C# that will be implemented in .NET BEFORE they are submitted to ECMA.

    --
    An Eye for an Eye will make the whole world blind - Gandhi
    1. Re:A quick bet... by nagora · · Score: 1
      Microsoft will announce "updates" to C# that will be implemented in .NET BEFORE they are submitted to ECMA.

      This is so obvious that I wonder why anyone would be stupid enough to work on Mono (at least for MS compatibility; it might be fine in its own right). MS doesn't need patents when it owns the rules.

      TWW

      --
      "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
  74. Derived classes + API Namespace by Anonymous Coward · · Score: 0

    This whole concept of .ToString etc that is used in Java, error handling, etc also taken by C#, did that orginate in Java, or did they take it from somewhere else? If you look at the underlying technology in dotnet, its seriously just how Java 2.0 SHOULD of been, the REAL R&D effort to think of designing something like this, actually goes to SUN. The OSS Community should let mono keep doing what there doing, and create yet another version, that is a rewrite of the api's, remoting namespace becomes RMI. C# becomes C2, common language runtime becomes, Any Language Runtime :-) -- WinForms, api could gain some improvements from mixing and matching of WinForms, Swing, SWT. WebForms, could use portions of Jfaces. This would address the issue of the Patenting the interface, as for process patents, further analysis of those would have to be done regarding what they patented on webservices, the other stuff, for the most part has plenty of prior art.

  75. People should know better by Citizen+of+Earth · · Score: 2, Insightful

    This is you in bed with Microsoft.

    This is you getting fucked.

    Any questions?

  76. Insightful? by Chuck+Chunder · · Score: 1

    Simply reciting a proverb does not constitute insight.

    For every proverb there is an equal and opposite proverb.

    Fear is the mind killer!

    --
    Boffoonery - downloadable Comedy Benefit for Bletchley Park
  77. US jurisprudence 101 by Anonymous Coward · · Score: 0

    In the U.S.,

    - Anyone can sue.

    - Anyone rich (eg, M$) can sue you and win, b/c you can't afford to fight it.

    This is called rule by corporations...
    Perhaps it is a new twist on fascism.

  78. IAAL by pyrrho · · Score: 1

    "I'm An Anonymous Lawyer" ?

    --

    -pyrrho

  79. Most non-software patents are as stupid! by dan_sylveste · · Score: 1
    It is a common misconception that non-software patents are better than software patents. However, this is not true.

    I know of a patent where IR-light is used to warm the cement to remove old window-panes. The heat softens the cements.

    The combination of IR+window cement = invention!

    Conclusion: Everyone inside that patent trade knows that patents are stupid. The first to patent wins.

    Therefor, patent more or at least describe all your good ideas on a web page so that no one else can patent them.

  80. Right ! by Anonymous Coward · · Score: 0

    And by the way, i do not understand a free-in-mind people helping MS to get strategic advantage !

    Those mono guy are realy dumb. How can they think they can fool MS ? IMHO those guys are only MS zealots that try to split the opensource comunity in several camps with FUD !

    Be united ! With the 2.6 kernel, Linux+Java will be the final killer solution against MS world domination ;-)

    "You never knows what today will brought you..."
    TestMan

  81. Cynically... by SerpentMage · · Score: 1

    Yes and that is why MS is sueing everybody using their patent portfolio...

    Ooops... It is Eolas sueing MS, it is SCO sueing everybody in the world...

    Come on people, MS might be "evil" in some eyes, but they do not have a sue culture. In fact the last thing MS does is sue...

    It does get to me that they think big bad MS is going to use patents to stop other people, when in fact other people are abusing their patents. Use the power of slashdot to go against them...

    --

    "You can't make a race horse of a pig"
    "No," said Samuel, "but you can make very fast pig"
    1. Re:Cynically... by alext · · Score: 1

      Ballmer has explicitly stated that patents will be used to suppress Dotnet clones.

      How many more times is this naive drivel going to be repeated? Until such time as Novell choose to put a "we'll indemnify you against MS claims" offer on go-mono, no IT manager in his right mind is going to consider using Mono.

  82. The answer is simple by American+Patent+Guy · · Score: 1

    MS will enforce its patents when it perceives it to benefit the company, i.e. when the cost of bad publicity (impressing the public with their monopolistic brutality) outweighs the benefit of market control. Look at what they've done for DOJ: when they started to get beat up in the papers, they "settled". MS has a department full of IP lawyers at the waiting. Who do you have on your side?

  83. Open Source Fear, Uncertainty and Doubt by harriet+nyborg · · Score: 2, Insightful
    Let's not get hysterical before there is something to get hysterical about.

    "I don't think the heavy stuff is going to come down for quite some time yet."

    While there is never any reason to "get hysterical" and "go nuts," there is a case for fear, uncertainty, and doubt.

    This is, as you say, only a pending application. In the US, as in the rest of the world, applications for patent are published 18 months after filing. The patent office probably hasn't even begun to examine it yet.

    But if I'm a developer (of any type) I'm thinking "OK, but how does this help me?" Claim 1 is so broad it covers EVERYTHING I DO. If the patent issues in present form - and MS decides to enforce it - I am sunk. Fear sets in.

    Then the uncertaintly. I start walking the halls mumbling to myself, "Should I abandon 2000 hours of programming and completely change what I am doing, or assume the patent office will substantially reduce the claim?"

    I am not comforted by the fact that there is NO prior art cited on the published application (because it is not necessary.) I have no idea if the examiner has that 10 year old copy of "computer geek" which would be a knock-out prior art.

    My confidence suffers as I remind myself that that public cannot participate in the prosecution in a meaningful way and must wait until the patent is granted before it is known what claims will be issued and what prior art was available.

    Then I start a serious effort into self-delusion and convince myself that "the patent office would never issue such a broad claim."

    Then the doubt sets in.

  84. Ruby is the dark-horse in the race by Anonymous Coward · · Score: 0

    A differing view would suggest that PHP is taking more market share from Perl for web apps than Python is at this point.

    Now, I'm not really sure what the appeal of PHP is from a language standpoint as it seems to be a step backward from Perl (it doesn't even have namespaces). But PHP makes does web development easy.

    Now consider Ruby: Currently, Ruby is running a distant third to Perl and Python. However it is a very appealing language with a philophy that is much closer to Perl's 'There's more than one way to do it' than Python's 'there's only one way to do it'. Ruby is a much 'deeper' language than Python (which always strikes me as being rather 'shallow' - as in I get to the point where I say "is that all?") and since it is philosophically closer to Perl it is likely to attract a lot of Perl'ers looking for a cleaner language that still retains Perl's power. As Perl6 (the language) becomes more and more delayed, the restless masses of Perlmongers looking for something truly OO and cleaner will inevitably be drawn to Ruby as many a former Perl coder already has. If Parrot materializes in the next year or so AND a good Ruby front-end appears for Parrot...well these are some large 'if's, but if those two things happen then I see Ruby gaining a lot of ground and coming from behind to give Python a real run for it's money (and very likely winning).

    In the meantime, Ruby needs to come up with ways to make the creation of web-apps as easy as it is in PHP. There are already a lot of good frameworks for Ruby that should give PHP a run for it's money on it's home turf. They need to be further developed, and perhaps even more importantly, they need to be well documented.

    1. Re:Ruby is the dark-horse in the race by Colonel+Panic · · Score: 1

      I like the horse race analogy. I really hope you're analysis is right as I am a fan of Ruby - it really is a great language that deserves a lot more attention.

      In regard to the topic at hand, there is a Rubydotnet project in the works. From the RubyDotNet page:
      The Ruby/.NET bridge lets you use .NET and Ruby objects together in your programs. You can access .NET objects from Ruby and vice-versa.

  85. Re:MS not helping .NET development now by Tim+C · · Score: 1

    unlike java, it is also seeing some real-world apps on the client as well

    Well, perhaps you don't regard an IDE as a "real world" app, but Borland's (excellent, imho) JBuilder is written in Java. Two other Java apps I use from time to time are SQuireL, an SQL client, and JEdit, a "everything plus the kitchen sink" text editor.

  86. Look at it from the strategic point of view by msafar · · Score: 5, Insightful

    Every line of .NET framework code (J#/C#/VB.NET) is a line that didn't get written in Java. From that perspective, Mono and DotGNU help Microsoft to expand the market for .NET.

    What is the revenue model for .NET though? Microsoft charges only for the development environment, which you can purchase from Borland if you like. The real strategy is to keep people focused on the Windows platform. .NET's value to Micrososft is to make Windows developers more productive.

    Bottom line: Microsoft will likely allow Mono (as they have so far) and DotGNU until applications utilizing it on Linux reach critical mass. At that point, Microosft will probably start charging royalties to commercial developers (either per programmer, or rev share).

    Will Microsoft forbid .NET on Linux? Maybe for a short time this could happen, and it is a danger, but I just wonder if they'll dare pull such a stunt given the EU/US anti-trust watchdogs. The only reason they would do it is to try and slow down the march towards Linux, which, frankly, will not be affected by the presence of .NET on that platform.

    Devil's Advocate note: I also wonder if they'll try to stop it now because if they let it go for too long without challenging it, the courts might say they didn't defend it for so long that they lost their chance (but I'm not a lawyer).

    Finally: Why use .NET at all on Linux (note that I LOVE .NET on Windows)? The whole point of writing distributed applications with Web services is so that platforms can communicate over SOAP (or SOAP-ey) protocols. I don't see any major advantage of .NET over J2EE for an enterprise dedicated to Linux.

  87. Re:MS not helping .NET development now by LarsWestergren · · Score: 1

    More and more things will start to require it. .net is seeing admirable deployment on the server side.

    I can't believe you are delighted to see that MS is increasing their stranglehold on the computing world.

    owever, unlike java, it is also seeing some real-world apps on the client as well.

    What about Eclipse then? And we could see a lot more of them if people wouldn't buy into the anti-java FUD.

    --

    Being bitter is drinking poison and hoping someone else will die

  88. seeing how .NET is a lesser clone of java by Anonymous Coward · · Score: 0

    I think M$ would be on the losing end of a patent dispute. I used to code in VB, some C++ and have coded in Java over the last 4 years. I'm not a .NET expert, but from what I've seen, it's a watered down version of Java. The event model is the only significantly difference I've seen between Java and .NET. So if anyone were to bring out the lawsuits, I would expect Sun to do so. I think the real question is why someone would want com+, the M$ transaction management services, and security holes in M$ products over the much cleaner and better implemented J2EE equivalents? The only advantage M$ has over java in my opinion id their ide. M$ does make some kick but development tools. The next question is how long will it be before a major security hole is discovered in the .NET platform? I would consider the ability to reflect private methods a security hole, but that's up for debate. Thirdly, how long will it be before people separate the hype from reality with .NET solutions? Remember how DCOM and COM were supposed to be the be all, end all solutions of distributed and interposes computing? Now they are on the way out the door. For the smashing I've done of .NET, I will give it props to VB..NET and ASP.NET for being significantly superior to their predecessors. Speaking of which, what benefit is there to using VB.NET over C#? C# is pretty much a M$ version of Java and does the same exact things as VB.NET so the only difference I can see is the syntax and that provides no real value.

  89. Re:MS not helping .NET development now by johnnliu · · Score: 1

    It comes down via Windows Update, also if you sell your product on CD or deploy your application manually to your clients, you can always include the .NET redistributable (25mb is nothing on a CD) with it.

    Expect newer versions of Windows to come pre-installed with .NET CLR. (Given that they don't install the Java VM by default on Windows XP already, I can almost smell another lawsuit coming).

  90. Dumb post by sawanv · · Score: 1

    This one has to be one of the dumbest pot I have seen on /. so far. If you are stupid enough to trust MS promoted "standards" you deserve to be shafted.

  91. Patents corrupting opensource by mdupont · · Score: 1

    In summary, I think that these patented interfaces are not only bad, but they are corrupting and dividing the open source and free software implementations of the software.

    I find it amazing that dotgnu has a contest to implement patented interfaces. They say, that this stuff is #ifdef'd out, but it still throws a bad light onto the whole competition.

    Why should they pay people to implement code that will need to be thrown away?

    You might want to read
    MY MAIL ABOUT THIS SUBJECT HERE.

    mike

    --
    Introspection is the key to understanding
  92. Python and JScript by XNormal · · Score: 1

    Microsoft is rapidly catching up on the scripting front. Take a look at the newest versions of JScript. It's becoming remarkably similar to Python in its capabilities. It's dynamically typed but now features optional static typing for performance, cross-language compatibility and error checing. It supports both "script" mode development and static compilation to assemblies. The latest versions add a real class system to the original JavaScript object model and a host of other features. As a .NET language it has access to the complete .NET library which is quickly catching up with Python's "batteries included" libraries.

    Be afraid.

    I am a big fan of Python and also a code contributor. But when I look at where JScript is going it gives me an eerie feeling. So far Microsoft isn't pushing it too hard but it has real potential. One of the undeniable advantages of JScript is that it has a familiar C-like syntax. While I prefer the Python syntax I am aware that on first impression it is a turnoff for most programmers.

    --
    Stop worrying about the risks of nuclear power and start worrying about the risks of not using nuclear power.
  93. from the do-you-trust-Redmond dept by allanj · · Score: 1

    Aka "from the when-hell-freezes-over dept".

    --
    Black holes are where God divided by zero
  94. What does the claim really cover? by XNormal · · Score: 1

    Note that they are not claiming an apparatus or method claim. They are claiming the architecture. A claim is interpreted within the context of the disclosure part of the patent. The disclosure part of this patent is a CD submitted with it containing the help files for the .NET web services API.

    The are claiming the API. Not any API that matches this general description. They are claiming the specific API.

    Disclaimer: IANAPA (I am not a patent attorney) but I do have some experience in the patent area. I could still be simply wrong or perhaps an undercover agent for Microsoft corporation...

    --
    Stop worrying about the risks of nuclear power and start worrying about the risks of not using nuclear power.
  95. Re:Call me stupid - is mono better? by Decaff · · Score: 1
    > Is it faster? No
    Compared to what? Plain C, compiled by a highly optimizing compiler for a certain platform? No, of course not. JAVA? Maybe. Interpreted languages without bytecode support? Maybe.


    There is no reason why a high-quality bytecode-based VM system should not match or even beat optimised plain C, if the bytecode interpreter does run-time profiling and translates bytecodes to native instructions. After all, the VM can find the actual bottlenecks during execution as against the predicted bottlenecks at compile time. This works in practice - IBM's Java VMs can give application performance equal to (and occasionally even better to than) optimised C code.

    > Is Development Faster ? No
    Yes, on Winodws with visual studio. At least compared to plain C with a texteditor. This also requires use of all the non open stuff of course.

    Systems like Java and .Net can significantly improve development time as they give you large and well-designed class libraries. Java and .Net also manage memory for you and made debugging a lot easier. (One of the joys of Java is the stack trace with like numbers available on each exception). These advantages are present even with command-line development.



    > Does it do things that other languages cannot? No
    No but that would be an argument against any other language. But having different languages is a good thing. Besides, in theory .NET is language independant, which makes it interesting.
    [stuff cut]

    In principle, any machine code, real or virtual in a VM, is language dependent. The Java VM is not just for Java - there are many languages that can use it, such as JPython, and Smalltalk. The .Net bytecode was marketed as language independent, but in practice it seems to be targetted towards Java-like languages, such as C# and VB.Net.

  96. Black - White response by Steeltoe · · Score: 1

    I think you are doing a good job as programmers, but I have always been a bit worried that you are helping MS to slay Java. To me it seems they are fighting really hard on two fronts now, against Linux and against Java. If they manage to get .Net/C# and all that to be the business standard, with your help, won't that make it easier for them to turn against the one remaining target?

    When will people step down from their warhorses viewing others as the "enemy", and start realizing we're all here together? We depend on eachother and those who try to live in glasshouses, should notice the cracks in it. Quotes such as "the enemy of my enemy is my friend", is still ignorant, stupid and dangerous thinking as it always has been. WHEN WILL YOU PEOPLE LEARN?

    The "enemy" are our thoughts that we are the "good guys" and the others are "evil". Thoughts of separation, which is the ONLY reason we go to war.

    To be more OT, what matters if people want to support certain technology? Software is software, screw the politics and manipulations. If people like some ideas, let them implement them. Stop viewing everything as a threat to YOU, as we have enough tyrants and paranoid leaders in this world. We don't need more with such mode of thinking, and nobody need your political approval of their pet project.

    1. Re:Black - White response by LarsWestergren · · Score: 1

      When will people step down from their warhorses viewing others as the "enemy", and start realizing we're all here together?

      Hey, why are you attacking me?? ;-)

      Software is software, screw the politics and manipulations.

      I'm sorry, but MS has shown us that software CAN and IS about politics and manipulations. I try not to get involved in flamewars about PHP vs C vs Perl vs Python vs... because in these cases, it is a matter of which flavour of language you prefer or are more comfortable with. In those cases I think you are correct, it is counterproductive to make up us vs them camps, to start designate enemies.

      With MS the case is different, past behaviour has shown that they don't like what they don't control. I get annoyed when people try to force me to do something against my will, and I often get that feeling when I use software designed by Microsoft.

      That is why there are so many strong feelings involved with the Mono project. Some see it as a way to break free from MS, others see it as a way for MS to get a foot in into the Open Source world, so they can start to push people around here too.

      To answer to your more off topic subjects:
      The "enemy" are our thoughts that we are the "good guys" and the others are "evil". Thoughts of separation, which is the ONLY reason we go to war.

      But what if someone goes to war against you? Are you just going to sit there and go "Wow, I must be having thoughts of separation...not good." Note that I consider myself a pacifist...but I believe there are limits.

      --

      Being bitter is drinking poison and hoping someone else will die

    2. Re:Black - White response by fingusernames · · Score: 1

      The "enemy" are our thoughts that we are the "good guys" and the others are "evil". Thoughts of separation, which is the ONLY reason we go to war.

      Blah, blah blah blah, blah. Moron. People have gone to war, and will go to war, for a hell of a lot more reasons (and yet, more fundamentally simple) than "good v. evil." It is in our nature. Competition is life, it leads directly to conflict, and conflict sometimes leads to war when other means of resolution don't work out. War isn't "bad," no more than my cat chasing, tormenting, killing with small wounds, and finally eating a mouse. It's nature at work, nature isn't nice, and surprise surprise, we are a part of that game, and there is nothing wrong with that. All the rules we build up to govern our little time amongst the breathing can't change the underlying nature of man's existence in a "cruel" world. I'm sure you're also an enviro-fan. Man is man's only natural predator. If we don't kill each other, if we keep reducing "human suffering" by curing disease, if we keep multiplying, what will become of our environment? Birth control? Bah. Strife, conflict, war, destruction, death... 100% natural and good for you, a road lined with profit, innovation and progress! We've been fortunate that we could fight our wars through proxies far away for so long, but now those damn Muslim whackos are out for blood against the Christian/Jewish whackos, bringing it home to us. They're not fighting over oil, land, or anything that can be negotiated. They are fighting over who has the better imaginary friend. Crazy. Too bad we're too 'nice' and Europe is too cowardly to go for the throat and make a proper war of it. The Muslim whackos have no such qualms.

      Larry

      "In Italy for thirty years under the Borgias they had warfare, terror,
      murder and bloodshed, but they produced Michelangelo, Leonardo da
      Vinci and the Renaissance. In Switzerland they had brotherly love,
      they had five hundred years of democracy and peace, and what did they
      produce? The cuckoo clock." -- The Third Man

    3. Re:Black - White response by Steeltoe · · Score: 1

      Thanks for a well thought-out response. I fairly agree with you. I was just so tired of seing all the posts "MS vs FSF" or something. Just posted to balance those post ;-) Didn't mean to attack You..

      Btw, if somebody goes to war with me, I'll think of something when it happens. I don't believe in prescripted action (but not in reaction either *hydr*). A balance is good, unless extremes are called for ;-)

  97. Re: "describe all your good ideas on a web page" by bizcoach · · Score: 1
    I don't think that describing your good ideas on a web page is good enough, because with this strategy it might turn out to be difficult to prove that you have published the idea early enough. I think it's much better to post your write-up of the ideas to a mailing list, then many people will get copies and will if necessary be able to act as witnesses concerning this crucial detail.

    For anything related to DotGNU or .NET or webservices in general or bytecode systems in general, I invite you to use the DotGNU "visionaries" mailing list for creating a public record that can if neccessary be used later as "prior art" for invalidating patents on essentially the same ideas.

    Greetings, Norbert.

  98. Java GUI speed and Visual Studio by Decaff · · Score: 1

    .... Blows Swing away...
    Then don't use Swing. Use IBM's SWT instead. Its a native GUI library, fully-featured, open source, and available pre-compiled for lots of platforms (OS/X, Windows, Linux etc). Under Windows it allows use of COM/ActiveX etc.

    Microsoft's development tools always been good
    Sorry, this is nonsense. Having dealt with MS tools for nearly 25 years I have found them to often be some of the worst I have ever used. Visual Studio is a catch-up job, replacing truly awful and buggy command-line tools in the 80s and early 90s. Microsoft were one of the last companies to provide development tools for Windows that actually ran under Windows! I have been used to quality systems like Smalltalk IDEs which include integrated class browsers, run-time re-compilation, object inspectors, class and method finders and documentation. I have also been used to small and efficent IDEs such as those provided by Borland/Inprise. Over the past few years I have been supporting users developing in Visual Basic 6, and the whole thing is a mess, to the extent of some Visual Basic programs actually crashing Visual Studio!

    MS tools may look pretty, and be easy for beginners to get started, but for professional OOP development they are definitely low-quality.

  99. Re:GNOME distribution with Mono is *STILL* DANGERO by IamTheRealMike · · Score: 1
    Oh come on, please stop trolling with that garbage.

    NZHeretic, you STILL don't explain why a GTK# desktop application NEEDS to use SOAP or web services, you just assume it does!

    You also appear to be making the flawed assumption that it's possible to patent something that is otherwise unpatentable by covering the "interoperation" of components - yet again you do not deem it important to explain this point.

  100. Don't do Mono by 16K+Ram+Pack · · Score: 1
    If we're not careful, this could help sink Linux.

    The doomsday scenario on this one is that lots of people end up coding C#/ASP.NET on a Linux platform, Microsoft work out a legitimate way to get it off Linux, and corporations see the best way forward as being to port their code to Windows.

    I know Java is in the hands of a corporation, but Java is designed to work cross platform.

    What's wrong with PHP and Python anyway?

  101. For once, I think it's justified: by Haeleth · · Score: 1

    5. Profit!

  102. where and when did MS claim this to be defensive? by bizcoach · · Score: 1
    cakoose wrote: "The patents could be, as MS claims, defensive patents."

    If MS has indeed made any claims of this kind, please give me the exact reference. This could become important.

    Greetings,
    Norbert,

  103. C++ by forgoil · · Score: 1

    The biggest problem with languages like Java and C# is the fact that they are built for one system (JavaVM and Windows+CLR) by one company (SUN/MS). A language like C++ on the other hand is built to work on any OS and it does (*NIX, Linux, *BSD, Windows, AOS, etc, etc, etc). On top of that it is not owned by one company, nor is it produced for one company.

    C++ and C# are great languages, for what they were built to do. I can't stand Java unfortunatly, because it simply isn't good at all. And on top of this we have many different C++ APIs, one great C# one (.NET) and well, there is a Java API as well;)

    So if the open source world actually wants a Java/C# class language, I would suggest finding an open patent (I've never used that one before, and if noone else has, I want to (C), (T), patent, and claim it!;)) language or create one. Then build one good API for it.

    There are also languages such as D (technically there seems to be many Ds out there), Obj-C (or does it suffer the same problems? I never got sure of that.), and if the problem allows it there is always Ruby and Python.

  104. Patents can kill, so can EULAs by theolein · · Score: 2, Insightful

    Before I discuss the .Net initiative itself, I didtinctly remember a Ballmer quote (here on /. as well, I think?) stating that MS will use its patents to increase marketshare. At the moment MS will leave .Net alone, for sure, as it is vastly more immature than MS' implementation, but woe betide the day when even one, just one, large Mono application (application server, distributed CRM or ERP app?) gains popularity amongst the many governments and businesses now moving to Linux. That is the day when MS will send its lawyers around for a chat on patent laws.

    On the technical side .Net sounds like the fantasy that many VB coders, MS shops and PHB's have had for years: The ability to code an application in a mess of languages (in all probability it will be C++,VB and C#) and actually produce something that is both useful and full of buzzword compliance.

    But, it would be good to note that nothing that .Net or Mono does is truly new. They are refinements of current coding practices. You can do exactly the same thing in Java, C++ and Python, just in a longer timeframe. This might be good in terms of productivity but I can almost certainly see this producing yet another generation of VB type coders with little discipline and chaotic understanding of OOP.

    My guess is that this is simply what MS is betting the farm on in order to move away from Win32 and at the same time corral developers and customers into staying with Windows. I read the EULA for VS.Net2003 and it seems you can neither publish benchmarks nor develop Office applications with it.

    Are you sure you want to go down that road? Hasn't SCO been an eye opener enough?

  105. I call bull by Rtech · · Score: 1

    While I've only played trumpet and piano for 6-7 years... C# is D flat. B flat is A#. Sharps are a half step up, flats are a half step down.

  106. Re:MS not helping .NET development now by Anonymous Coward · · Score: 0

    Why would that be a problem? People would never be aware that the 26Mb download was actually 25Mb runtime and 1Mb application :) not only that, they don't really care.

    Do you care that the Mozilla runtime is actually a 10Mb Gecko runtime and a 100k front end?

    What about IE? Regardless of MS business tactics there, developers sure had no problem distributing the 15Mb IE runtime so that thier application had access to the latest common controls and the internet API.

  107. Tying functionality to a platform:e.g. Eola's plug by NZheretic · · Score: 1
    The two Microsoft .NET patent applications are just two examples of many such patents in the many in the pipeline.

    Microsoft is able to 'get away' with getting these patents in exactly the same way Eolas was able to be granted it's plugin patent for browsers, dispite Apples HyperCard and LotusNotes had the same functionality -- by tying that patented functionality to a platform.

    Where Eolas was able to get the plugin patent for browsers, Microsoft is quite able to get patents for existing functionality on it's .net platform -- even if the same functionality has been demonstrated on Java/Perl/Python/CORBA etc.

    The US Patent Office is a over a year behind in it's proccessing of patent applications, new applications covering the .NET API for network and webapplications are just appearing.

  108. Here come the KS lawyers.... by mwa · · Score: 1

    Didn't you just violate the MS EULA that says "Thou shalt not publish .NET benchmarking statistics"?

  109. Implement the Standard Class Library Only by Nurgled · · Score: 1

    I think trying to implement the 'Windows'* and 'Microsoft' namespaces is a mistake. Firstly, these are not codified in a standard, and are liable to change at any time. In addition, the code and API in the Windows namespace is not designed to be portable, making plenty of assumptions about the Windows registry, Win32 window handles and so forth.

    What the Mono people should be doing is making a sturdy, open implementation of the .NET CLR and the 'System' class library, and then let people create libraries for Gtk+ (already done), Qt and anything else. The 'System' class library (to my knowledge) makes no such assumptions about the underlying platform, and a properly-designed application should have the GUI code separate from the main code anyway, so creating a cross-platform application will simply require writing a different implementation of the GUI.

    The only loss with this approach is that Mono won't be able to run applications designed for Windows, but I don't consider that a useful goal anyway. What is needed is good, solid open source applications using consistant UI toolkits to create a desktop that feels like it goes together.

    * why Microsoft put the 'Windows' namespace under 'System' I have no idea, but let's just pretend they put it under 'Microsoft' where this unportable API logically belongs.

    1. Re:Implement the Standard Class Library Only by alext · · Score: 1

      But if applications written for Dotnet can't be ported to Mono, what advantage does that leave Mono with over Java? (I mean Java both in its free-beer forms from BEA, Blackdown, IBM & Sun, and its free-speech form in Kaffe).

      Would you care to guess at the relative investment figures for Java-on-Linux vs. Mono-on-Linux applications? The number of big Linux systems deployed to run Java apps vs. Mono apps? Aren't these figures important in our implementation decisions?

    2. Re:Implement the Standard Class Library Only by Anonymous Coward · · Score: 0

      They can be ported. That is the point. You simply write a new UI layer for your application and you can have a GNOME application which follows the GNOME human interface guidelines, rather than a weird app rendering with GTk+ widgets but using Windows-style dialogs and conventions -- which is what we'll get from the Mono version of Windows.Forms.

      There's not necessarily any particular advantage, but what's the advantage anyway? If you want cross-platform without any code modifications, Java is for you, but if you want an application with a UI tailored to the target platform, Java is not the answer; well, not Java Swing anyway. Observe how Apple has created a custom Java API for their windowing system. This is comparable to my proposal to create Gtk+ and Qt-specific APIs for Mono. I'm sure someone has already thought of and perhaps worked on this for Java.

      Perhaps at some point someone will design a windowing system similar in purpose and design to Java Swing and/or AWT for the CLR. However, I like my apps to fit in to their environment.

    3. Re:Implement the Standard Class Library Only by alext · · Score: 1

      Ah, I see. Unfortunately to "simply write a new UI layer for your application" is likely to be considered a non-trivial operation, certainly by the likes of Adobe, Autodesk et al.

      So given that we both agree that Java already offers the options of per-platform UIs and generic UIs (although I should point out that the Apple OSX UI is the Swing API, not a separate development) we seem to have concluded that Mono brings precisely nothing new to the table.

    4. Re:Implement the Standard Class Library Only by Nurgled · · Score: 1

      As someone who has, in the past, been unfortunate enough to use Adobe's Windows offerings, I'm forced to agree with your assertion that Adobe has no interest in adapting applications to suit the local interface guidelines. Adobe's software has some of the worst UIs I've ever seen, but I suppose that's because I'm not familiar with Mac interfaces.

      Mono is just an alternative, I suppose. It might not have any specific advantages, but for someone who has been doing .NET development it provides good crossover and people might prefer the .NET class library to that of Java.

  110. why i would develop with mono by Anonymous Coward · · Score: 0

    when gnome is interally written in c ?

    1. Re:why i would develop with mono by NightEyez · · Score: 0

      Well lets see...uh uh maybe because C is PoS language compared to C#. Next time think before you post smart guy.

  111. DotGNU's Java efforts need volunteers by bizcoach · · Score: 1
    LarsWestergren wrote: I have always been a bit worried that you are helping MS to slay Java.

    This is a very good point, one that the DotGNU Steering Committee agrees with. We would very much like to equally support C# and Java, and a significant amount of work has been done in this direction. Our compiler suite is not only able to emit bytecode for the Microsoft-designed CLR, but it can also be used to generate bytecode for the JVM. We also have a Java-compiler front-end. Unfortunately, both of these areas of coding work are current dormant for lack of volunteers.

    Who will volunteer to champion our Java efforts?

    Greetings,
    Norbert.

    1. Re:DotGNU's Java efforts need volunteers by LarsWestergren · · Score: 1

      This is a very good point, one that the DotGNU Steering Committee agrees with. We would very much like to equally support C# and Java,

      Sounds interesting! Were I a better programmer....

      I realise I need to read up more about .NET, Mono and everything before posting more on this topic. You people seem to be fighting against a lot of anger and misconceptions out there, I would hate to spread FUD about the project... if I am wrong that is. :-)

      Cheers,
      Lars

      --

      Being bitter is drinking poison and hoping someone else will die

  112. Eolas by voss · · Score: 1

    The IE patent infringmenet case they just lost.

  113. DotGNU Portable.NET is based outside the US by bizcoach · · Score: 1
    The "let's be compatible with .NET" part of DotGNU development is based in Australia, well outside the US, and a legal entity has been created there specifically for this purpose.

    However we are still concerned about the bugs in the US legal system, because we would like computer users in the US to be able to freely use and redistribute all of DotGNU, and contribute to its development.

    Greetings,
    Norbert.

  114. Will software patents kill the US economy? by bizcoach · · Score: 1
    Frymaster wrote: "government regulation of economic rights parallels economic growth".

    This may be true in many areas, but in the case of software patents the US has definately gone too far. There can be no doubt that every useful technology will get implemented in Free Software sooner or later, and technology that is useful to many people will get implemented sooner.

    The US patent system can only restrict what US residents and US based businesses can do. The rest of the world will happily move forward with Free Software. If the US patents system prevents a Free Software .NET competitor in the US, those parts which are not allowed in the US can still be developed and used outside the US.

    It is well-known that when a profit-oriented company has a monopoly on anything that is of key importance for the business world, that is good only for that company and its major shareholders, but not for the economy as a whole.

    Hence it should be expected that if the US legal system allows this to happen, businesses will migrate to countries where they will not be encumbered by software patents. Whether we like it or not, globalization is a reality.

    Greetings,
    Norbert.

  115. Re:MS not helping .NET development now by fitten · · Score: 1

    Not really. As a developer, we downloaded the .NET Runtime, include it on the CD, and do the install if a .NET CLR isn't detected as already present. It is very easy to do using an installer program (like 15 minutes worth of work, including the download of the CLR from Microsoft and you only have to do it once).

  116. For software patents to truly be defeated by brlewis · · Score: 1

    The last word from the US Supreme Court is that software is not patentable. For software patents to be truly defeated, all you need is for a case to make it to the supreme court so they can smack down the lower-court Alappat decision that contradicted them. Unfortunately, they're asked to hear 10x as many cases as they can actually hear, so we'll see.

    Read the Diamond v. Diehr decision yourself if you don't believe me.

    1. Re:For software patents to truly be defeated by SillySlashdotName · · Score: 1

      Read the Diamond v. Diehr decision yourself if you don't believe me.

      From this discussion of Diamond v Diehr, the answer does not support your contention. "The Diehr court left undecided the question of whether computer programs standing by themselves could ever be patentable."

      I have not found citations for The last word from the US Supreme Court is that software is not patentable. as you state. Can you provide other citations that support your claim? Diamond v Diehr doesn't.

      There is In Re Alappat, which is what is generally used when refering to the patentablity of software, but that is an opinion by a Federal Circuit Court of Appeals, not the Supreme Court.

      From the lawfirm that argued the Alappat appeal:

      "The decision in In Re Alappat No. 92-1381 (Fed. Cir. July 29, 1994) (en banc), clearly paves the way for the patenting of inventions that can be implemented in either hardware or
      software"


      and

      "overturns a long standing Patent Office policy of denying patents on inventions that could be functionally implemented in software."

      and

      "The Patent Office has not yet determined whether to seek review by the United States Supreme Court. See Bart Ziegler, Court Upholds Patent for the Way Software Interacts With Computer, Wall Street Journal, August 8, 1994, at B4."

      Damn, there go my mod points!

      --
      Acts of massive stupidity are almost never covered by warranty. --me.
    2. Re:For software patents to truly be defeated by brlewis · · Score: 1

      Diamond v. Diehr does support my claim, most specifically in section III., where they reiterate previous decisions that ruled software not patentable. It's true that the exact words "Software is still not statuatory; we haven't changed our minds" do not appear in Diamond v. Diehr, the way they uphold previous decisions obviously implies it.

      Most telling is a sentence in section III of the decision. Again and again in their opinion, they explain that the inclusion of nonstatuatory subject matter does not make an otherwise statuatory (i.e. patentable) process as a whole nonstatuatory. But once instead of "nonstatuatory material" they give some examples:

      Our earlier opinions lend support to our present conclusion that a claim drawn to subject matter otherwise statutory does not become nonstatutory simply because it uses a mathematical formula, computer program or digital computer.

      This sentence is meaningless if computer programs are statuatory. Either computer programs are nonstatuatory, or the court gets a kick out of putting non-sequiturs in its opinions.

      Note also that the dissent (who thought the patent invalid), dissented on the basis of whether the non-software part of the invention was novel. The court as a whole agreed that the patentability of the invention hinged on non-software novelty.

      Thank you for including that quote about the Alappat decision paving the way for software patents. More people should understand that. Many mistakenly think that Diehr paved the way; it did not.

  117. Re:Nope - Afraid it's Yes: read history of OS/2 .. by Anonymous Coward · · Score: 1, Informative

    The dirty tricks played by MS against its erstwhile partner should give anyone pause if they were to believe MS has no history of unfair business practices.

    Moreover, one need not have followed the antitrust case against MS to wonder about your apparent obliviousness.

    Finally, much older and from personal experience: In PC Magazine I read a letter stating that WordPerfect required a license number prior to offering technical support. Later I called WP tech support to get my license number only to be told that by the support person that they have no access to that information. Moreover, I was not asked as asserted what my license number was!

  118. Sorry, that was me. by Nurgled · · Score: 1

    I guess I accidentally hit the "Post Anonymously" checkbox on my way to the preview button. The parent was posted by me.

  119. What makes you think a patent WON'T exist? by yerricde · · Score: 1

    I don't see any patent granted last week.

    Do you sincerely believe in the ability of the United States Patent and Trademark Office to research prior art for an invention named in a patent? Do you believe in the USPTO's judgment of what constitutes an invention that is not obvious to anyone with a B.S. in computer science?

    --
    Will I retire or break 10K?
  120. C++ JVM target? [was Re:Parrot] by jungd · · Score: 1

    Where? How does it do raw pointers?

    --
    /..sig file not found - permission denied.
  121. You'll never be safe by infolib · · Score: 1

    The poster implicitly assumes that he has unencumbered alternatives to .NET. That may be wrong. Who knows how many patents Python infringes? Perl?

    Get used to it. Even though Python was both invented and coded by Guido van Rossum, someone else may hold crucial patents. The only way to be sure is to check all applicable patents. If you don't feel like that either just ignore the question, or fight software patents

    --
    Any sufficiently advanced libertarian utopia is indistinguishable from government.
  122. The Office.NET Test by billtom · · Score: 1

    To my mind, the whole debate about the open source .NET projects will come down to what I call the Office.NET test, which goes like this...

    At some point in the not too distant future, Microsoft will release Office.NET. That is, their office suite re-written to run under the .NET framework.

    The test is, will Office.NET run, out of the box with no significant crashes or non-functioning features, on non-Microsoft .NET frameworks?

    If yes, then .NET is the real deal, a cross platform programming environment.

    If no, then .NET isn't a cross programming environment, regardless of what the Mono and dotGnu forces say.

  123. Typo by ananiasanom · · Score: 1

    I think you meant to type "You are correct. If the powerful still got their wealth from growing cotton, ..."

  124. Obviouly you've tried to put toothpase by Anonymous Coward · · Score: 0

    back in the tube at one time.

    gewg

  125. Sleep with the enemy. by miffo.swe · · Score: 1

    Until i see a written document from Microsoft where they openly state they wont go after Mono in any way i will consider MONO a big pile of toxic waste in Gnome. One can only ponder as to why Miquel hasnt done anything to get the legal things in order?

    Any company but MS and i wouldnt be so scared.

    Miquel, i really hope you dont put Gnome in a rough spot here. I dont think thats something enyone would want on their consiense?

    --
    HTTP/1.1 400
  126. M$: Just Kill Java!! by RudeyKewl · · Score: 1

    IMHO, one of .Net's main purpose of existence is to kill Java. M$ will do what it takes to kill it. So, I do not see M$ killing any Open Source .Net implementations as long as Java lives and rules.
    If and when M$ manages to make Java irrelevant, is when I want to know where M$ will take .Net and its patents.

  127. D-Flat already taken by Anonymous Coward · · Score: 0

    Al Stevens had a column in Dr. Dobbs Journal for years where he developed a DOS based windowing library in C++ and called it D-Flat...

  128. Re:where and when did MS claim this to be defensiv by cakoose · · Score: 1

    Well, my statement was based on the first paragraph of the article (do people even get that far before posting?). But it's third-hand knowledge at best. Also, by defensive, I didn't mean that it only defended products that were related to the patent. I thought it was more like IBM's where if you sued them for patent infringement, they'd probably have many patents covering the everyday use of computers, allowing them to counter-sue.

    Since my original post, I read that Microsoft did, in fact, use software patents to force a free ASF video implementation to shut down.

  129. No big deal. by caliskunk1 · · Score: 1

    Screw their laws. just move Linux development to Freenet.

    --
    Legalize Everything. www.infoshop.org
  130. Re:Nope (Better analogy) by someone247356 · · Score: 1

    Billy-Bob invents a new dohicky, doesn't have the resources to practically implement it, or the money to patent it. Joe-Jack hears about Billy-Bob's invention and gets a patent on it using a horrendously obfuscated, yet entirely typical name. Billy-Bob secures funding for his wonderful invention, it's a hit, sells millions. Joe-Jack dusts off "his" patent and sues the pants off of Billy-Bob.

    The joys of the USPO fostering innovation and progress as usual.

    someone247356

    --
    Just my $0.02 (Canadian, before taxes)
  131. Re:MS not helping .NET development now by Keeper · · Score: 1

    Any app that uses the .Net runtime will come with the runtime on disk, in much the same way that most DX games come with DirectX on cd, or how most applications come with a version of MFC.

  132. Then it's wxPython!! by Nicolay77 · · Score: 1

    The two main toolkits for Python are tk/tcl and wxWindows. wxWin is a big winner here, and is not more known just because Guido van Rossum doesn't know how to use it.

    It's being used by Mitch Kapor to create a competitor to MS exchange/outlook called Chandler.

    --
    We are Turing O-Machines. The Oracle is out there.
  133. Re:Longhorn-Paul Thurrott by Anonymous Coward · · Score: 0

    >>I'm sorry, but I don't consider Paul Thurrott to be a reliable source of information.

    >Why wouldn't you consider him a reliable source of Windows information? Considering he has actual sources inside >Microsoft and all. Most of his Longhorn information is from the WinHEC, complete with screenshots. You're just being >difficult to be difficult.

    Sources? Does he pay them for information or receive a wage from microsoft's marketing department?

    And will *longhorn* have flawless DOS support? :-p

  134. Instead of cloning .NET, make something better! by tjstork · · Score: 1


    Really, is the entire Linux community have no developer tools creator who is as good as that Dutch guy from Borland!

    --
    This is my sig.
  135. Re:Nope - Afraid it's Yes: read history of OS/2 .. by t0ny · · Score: 1
    blah blah blah. first, OS/2 and WinNT are two completely different things, contrary to your uninformed opinion. NT was the first OS to use a Win32 architecture, and was a completely new direction from what was done before.

    Second, MS doesnt own WordPerfect. I also have no idea what your anecdote is supposed to prove. PC Magazine says something about required info, which the company doesnt actually need. Big deal! Who cares? I fail to see what you are trying to say.

    --

    Manipulate the moderator system! Mod someone as "overrated" today.

  136. So? by danaris · · Score: 1

    "Paracutin...1943, a Mexican farmer sees smoke coming out of the middle of his cornfield. A week later there's a volcano a thousand feet high. There's no history of anything until it happens. Then there is. "

    --Volcano

    Have a nice day.

    Dan Aris

    --
    Fun. Free. Online. RPG. BattleMaster.