Slashdot Mirror


Mono and .NET - An Interview

all-of-the-dot writes "Would you use an open-source implementation of the .NET Framework? Ximian's Mono project enables you to build .NET apps that run on Linux and Unix as well as Windows. Check out the story from .NET Magazine's interview with Miguel de Icaza, Ximian cofounder and CTO" Added to which, AirLace writes "The Mono project has just achieved full self-hosting on Linux. While the C# compiler, itself written in C#, has been able to compile itself since March, Mono can now compile its own complete set of class libraries too. This announcement closely follows the release of the Phonic media player, the first .NET application for the GNOME desktop."

583 comments

  1. No I would not. by BigChigger · · Score: 0, Troll

    And Mono is why I swtiched from Gnome to KDE.

    Any more questions?

    BC

    1. Re:No I would not. by modulus · · Score: 2, Informative

      > And Mono is why I swtiched from Gnome to KDE.
      > Any more questions?

      Yes, I have the following question:

      Why does a small group of developers (some of whom happen to also work on gnome) working on the mono project constitute a reason to abandon gnome?

      Mono is in no way linked to the gnome desktop, and IMHO is unlikely to become thusly linked in the near future. The opinions of Miguel (sp?) may have misled you... there is no .NET in GNOME.

    2. Re:No I would not. by Lemmy+Caution · · Score: 2

      And if someone - anyone - started working on Mono on KDE, you'd leave KDE? If we keep this up, maybe we can push you all the way to CP/M.

    3. Re:No I would not. by racerx509 · · Score: 2, Funny

      Mono is why I switched girl friends.

      --
      13 year old white supremacists are shitty web designers.
    4. Re:No I would not. by JoeBuck · · Score: 5, Insightful

      Mono is a stupid reason to switch from Gnome to KDE, in that the Gnome project has not accepted Mono. It's a proposal from the Ximian folks that Gnome eventually accept Mono. I wouldn't be surprised to see the Gnome project split if Mono were forced on it in a central role (rather than as an optional add-on), as many Gnome developers are not fans of it at all.

      What will you do if some KDE developer says he wants to support .NET in the KDE framework? You'll then have to drop KDE, since you drop platforms based merely on proposals that they go in a direction you don't like.

    5. Re:No I would not. by AirLace · · Score: 2

      As someone has already pointed out, unlike the GNOME C# bindings which are hosted on a third-party site, go-mono.com, Qt# is already included in the main KDE distribution.

    6. Re:No I would not. by Anonymous Coward · · Score: 0

      The guy makes a +5 joke and only receives +1 automatic moderation.

      I guess AI is not ready for the Turing test.

    7. Re:No I would not. by Anonymous Coward · · Score: 0

      Plus, don't forget that Ximian's Mono provides an Open Source _alternative_ to Microsoft's .Net, which means that you can use Mono without paying Microsoft any money, and without being tied to any Microsoft services.

      Thus, instead of helping Microsoft, Mono helps _developers_ migrate _away_ from Microsoft.

      The Qt# bindings, on the other hand, simply provide support for .Net.

      Thus, Qt# helps Microsoft, and that's all it would do, if it weren't for the existance of Mono.

      Note that KDE/Konqueror also provides official support for Microsoft's ActiveX protocol through Reaktivate (see http://dot.kde.org/994747675/), thus helping Microsoft to de-commodtize the Internet, by encouraging the use of protocols that can only be accessed through a Microsoft-controlled middle layer.

  2. It's no use to resist .NET.... by FooBarWidget · · Score: 0, Offtopic

    No, I am not pro-M$.
    However, Microsoft has proven again and again that, in the end, they *will* win, especially if it's a Windows technology. .NET will soon be integrated in Windows, and developers *will* use it.
    Look at MS Visual Studio .NET. All I hear about it is praise from developers. You can create webservices ooh so fast and it's ooh so great. And "there is no competition; nothing else provides an environment that integrated and productive".

    Ignoring .NET is suicide. If you can't beat them, join them.

    1. Re:It's no use to resist .NET.... by kawaichan · · Score: 1

      FYI, .net will be included in the Windows .NET server OS which is gonna come out in a couple of months.

      Visual Studio .NET is already out (dev) and the servers will be out soon, what does this mean? It means that MS will need more developers to program their stuff in .NET (whatever that means)

      I think Passport has been a failure, look at it, there has been nothing useful for passport since its existance. It fully demostrates that companies are not willing to share data with Microsoft (for whatever reason)

      --

      kawai
    2. Re:It's no use to resist .NET.... by Restil · · Score: 5, Interesting

      We're playing the wrong game here. We need to have microsoft constantly chasing after US to keep up to date with the existing "standards", not the other way around. The open source community as a whole needs to be frontlining new standards. If we can keep Microsoft and other evil empires constantly playing catchup, it will severely limit the damage they can do overall. Sure, they'll play the embrace and extend game, but only if we give them enough time to do so.

      -Restil

      --
      Play with my webcams and lights here
    3. Re:It's no use to resist .NET.... by MrResistor · · Score: 2

      Developers may love it, but what about consumers? American consumers have proven time and again that they prefer a sense of ownership. They like to have their applications installed on their machine. As much as Microsoft would like all our apps to be pay-per-use webservices, I just don't believe that this is a future that the consumer is going to buy into.

      Don't get me wrong, I have nothing against the concept of services, in fact I like it. I'm currently planning a server/thinclient setup for my house. But, once again, it had better be my apps running from my server.

      Anyway, maybe I'm totally misreading the intention behind .NET. It seems to me that they're chasing UNIX and trying to get the remote user capability while still clinging to their misguided one-user-per-machine attitude.

      I just can't seem to get excited about .NET. I don't think the capabilities it offers are particularly innovative.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    4. Re:It's no use to resist .NET.... by Anonymous Coward · · Score: 0
      However, Microsoft has proven again and again that, in the end, they *will* win
      Like they are winning with the XBox against PS2 ? :-D
      Oh, sorry, you said "in the end"...
    5. Re:It's no use to resist .NET.... by MrResistor · · Score: 5, Insightful

      We need to have microsoft constantly chasing after US

      They are. Can you name a single "technology" MS has announced recently that *nix hasn't had for years (if not decades)? What does .NET offer, really? "Portable" code and remote apps? Java has offered portable code for about 7 years now, and remote apps predate Unix.

      All MS has done since they started developing NT is chase *nix. The only thing I can think of that they might have had a head start on is the GUI, but I have my doubts about that, too. What OS was Xerox using at PARC, anyway?

      The problem for *nix is that the general public isn't aware of that fact.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    6. Re:It's no use to resist .NET.... by ++good-duckspeak · · Score: 1
      We need to have microsoft constantly chasing after US to keep up to date with the existing "standards", not the other way around
      If you follow any standard dev lists you will notice a fair amount of participation by Microsoft. They are very aware of open standards but in most cases use their market power to create de facto standards or extensions.

      An effective ( and accepted ) "open standard" license that prevents Microsoft from using these tactics is the only way to beat them at the standards game.

      --
      Why is Triangle Man so MEAN?
    7. Re:It's no use to resist .NET.... by Noehre · · Score: 2, Insightful

      And the Linux croud hasn't been chasing Windows for the past several years in an attempt to copy the Windows "look and feel" on the desktop?

      Gnome/KDE are nothing more than attempts to mimic the Windows GUI.

      OpenOffice/etc. are nothing more than attempts to mimic popular Microsoft productivity applications.

    8. Re:It's no use to resist .NET.... by FuzzyBad-Mofo · · Score: 1
      Sorry, but I have used Visual Studio.NET and in my humble opinion it is a steaming pile. Sure, there are some nice features to the .NET framework, but Visual Studio is a joke. A few examples:
      • The editor (poorly) reformats code, even when it's explicitly told not to.
      • Half of the internal help documents are MIA
      • Does not fully support the CSS and HTML standards, creates code for IE. (big suprise there)
      • The standard web forms only support client side scripting on IE.
      These are only a few examples, I'm sure there are many more problems with Visual Studio. Again, it's not the framework I have a problem with, it's the editor and standard web forms.
    9. Re:It's no use to resist .NET.... by Anonymous Coward · · Score: 1, Insightful

      They are. Can you name a single "technology" MS has announced recently that *nix hasn't had for years (if not decades)?

      1) Drivers
      2) Games
      3) A broad user base (You and your 3 friends, who couldn't get laid in a whorehouse even if they had a $50 bill hanging out of their zippers, do not constitute a broad user base)

    10. Re:It's no use to resist .NET.... by MrResistor · · Score: 2

      Personal computer GUIs are all strikingly similar, whether you're talking about Mac, Windows, KDE, GNOME, fvwm, AmigaDOS... The list goes on and on. When you get right down to it there is really very little variation beyond the cosmetic, and even then the same elements are recognizable across the vast majority of them.

      I ask again; what OS was Xerox's GUI built on?

      Oh, and Openoffice owes far more to WordPerfect than to MSO. Perhaps it's time to take a step out of your MS-PR-department-provided box and take a look around. When you learn the real history of computing, you'll find that MS is actually one of the least innovative companies that has ever existed.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    11. Re:It's no use to resist .NET.... by swissmonkey · · Score: 2, Insightful

      Given that OpenOffice mimicks the GUI of MS Office(did you see how similar the GUI(buttons position, style, etc...) is ?) I tend to think that OpenOffice is actually nothing else that an Office clone, actually it's just worse, but very similar.

    12. Re:It's no use to resist .NET.... by Anonymous Coward · · Score: 0
      They are. Can you name a single "technology" (emphasis mine) MS has announced recently that *nix hasn't had for years (if not decades)?

      1) Drivers
      2) Games
      3) A broad user base
      Drivers are not a technology. (Linux has a loadable driver infrastructure. That's the only sense that drivers can be considered a technology in.)

      A user base is most certainly not a technology.

      Please make relevant points, and not 3 references to the fact that Windows is more widely adopted.
    13. Re:It's no use to resist .NET.... by MrResistor · · Score: 2

      Mono only is addressing the development and exection environments portion of the pie. Mono has nothing to do with the "web services" you are talking about.

      That maybe, and in truth that's what I would expect. However, this thread is not about Mono, but .NET and why it's going to take over the world. Microsofts vision of .NET seems to encompass all of the things you list, and while the server and developement/execution portions of that vision might be loved by developers, they're almost totally invisible to the consumer.

      The "privacy" and webservice parts are all that's going to be visible to the consumer will see, and I very much doubt that they will like what they see.

      I'm curious, though, what you see MS' vision of webservices is if not pay-per-use remote apps?

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    14. Re:It's no use to resist .NET.... by MrResistor · · Score: 2

      MS Office pretty much mimicks the old WordPerfect GUI, and OpenOffice follows WordPerfect much more closely than it follows MSO.

      I'll say it again, and a bit more bluntly this time: Microsoft has not produced a single innovation with regards to GUI design, even in terms of look-and-feel.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    15. Re:It's no use to resist .NET.... by Zeinfeld · · Score: 3, Insightful
      They are. Can you name a single "technology" MS has announced recently that *nix hasn't had for years (if not decades)?

      Can you name a single new technology that has appeared in UNIX in recent years that was not in VMS or MULTICS?

      This type of argument is pure sophistry, either Microsoft are accused of stealling other peoples stuff (hard to do with open standards) or they are ignoring open standards.

      Until WS-Security was proposed nobody had had any success with a transaction layer security enhancement. HTTPS failled, SHEN failled, PEM and MOSS failled. PGP and S/MIME had some success but they are limited to email.

      Now nobody would claim WS-Security to be amazingly novel, however Microsoft, IBM and VeriSign have got the whole industry behind a spec in that niche which has never happened before.

      As for all the 'nothing new has happened since Xerox' stuff, I suggest the people with that dellusion stop eating the mushrooms and go and use one of the things. OK so you can kinda sorta see the beginings of the ideas we use twenty years later, but they got as much wrong as they got right.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    16. Re:It's no use to resist .NET.... by Zeinfeld · · Score: 2
      Mono only is addressing the development and exection environments portion of the pie. Mono has nothing to do with the "web services" you are talking about.

      If you implement the .NET framework you can pretty quickly build the Web Services framework. Most of the Web Services support in .NET is bound up in the XML Serialization layer which uses the metadata supported in .NET to generate XML serialization and deserialization code directly from .NET classes.

      OK so this is a trick that appeared in the LISP machine 15 years ago but none of the mainstream companies have supported it since - up to now.

      Having tried to use the MSFT Web Services tools I decided that it would be easier to roll my own for my purposes (although since I bought the cheapo standard version of C# rather than the whole .NET studio that may just be I was doing things the hard way). However it is a heck of a lot easier to deal with XML in C# than in any other language I have used.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    17. Re:It's no use to resist .NET.... by kingkade · · Score: 1

      well i haven't used VS for css or html. i prefer a straight up text editor like UE32 or textpad :) so i can't comment on that.
      i agree with incomplete framework documentation anyway, but it's context-sensitive help if unbelievable useful not to mention popup members list and autocomplete..
      never had any problems with the editor...and i'm bias b/c i really like C#'s syntax...

    18. Re:It's no use to resist .NET.... by orthogonal · · Score: 1
      American consumers have proven time and again that they prefer a sense of ownership. They like to have their applications installed on their machine.

      Dude! I'm getting me that Japanese terabyte hologram disk, and then I'm gonna run a big ol' 2GHz dumb terminal!

      Yup, I'll put none o' that comppiled code on that there terabyte, I'll just fill it with my MS Windows swap file and a bunch of MS Active Desktop scripts written in Visual Basic for Applications!

      Dude!

    19. Re:It's no use to resist .NET.... by Clockwurk · · Score: 2, Interesting

      - Can you name a single "technology" MS has announced recently that *nix hasn't had for years (if not decades)?

      DirectX

      Optical Mice

      Scroll Wheel on Mouse (I think this was theirs)

      Back and Forwards Net buttons on Mice

      The Windows key :-P

    20. Re:It's no use to resist .NET.... by Anonymous Coward · · Score: 0

      I remember a school computer lab full of Sun workstations that all had optical mice. I don't know when the computers were deployed, but this was back in like 1996.

    21. Re:It's no use to resist .NET.... by Anonymous Coward · · Score: 0

      There is nothing new in DirectX. It's just a API wrapper around old ideas.

    22. Re:It's no use to resist .NET.... by sheldon · · Score: 2

      What does .NET offer, really? "Portable" code and remote apps? Java has offered portable code for about 7 years now, and remote apps predate Unix.

      Well actually so did Microsoft BASIC back 20 years ago.

      I've still got my Creative Computing Games books if you want to type in the code.

      Being "Portable" isn't what .NET is about so much as increasing developer productivity.

      Actually as far as like ASP.NET is concerned, I would use PHP as a more comparable example than Java.

      All MS has done since they started developing NT is chase *nix.

      And all Unix has done is chase the Mainframe. What is the Web anyone but 3270 terminals with color pictures?

      The problem for *nix is that the general public isn't aware of that fact.

      No, the public just doesn't care. That's the part that really bothers you.

    23. Re:It's no use to resist .NET.... by Anonymous Coward · · Score: 0

      Well put. The web is a joke, but I do believe there is some real power in the XML/SOAP stuff now being put out there - seems like a winner tech stack to me. MSFT should get alot of credit for their HUGE XML investments, and the foresight to look way beyond the browser - while the linux community is still playing with mozilla, the rest of world will be far past the 'bad' ol days of the HTML web and onto real business. My guess is they view the browser as a dead tech at this point.

    24. Re:It's no use to resist .NET.... by JamesOfTheDesert · · Score: 3, Insightful
      I'll say it again, and a bit more bluntly this time: Microsoft has not produced a single innovation with regards to GUI design, even in terms of look-and-feel.

      Gee, I guess if you repeat it often enough it becomes true. The site you linked is, judging by the snide comments abut Windows' "features", a tad biased. Do you have any other sources?

      What were the predecessors to the Visual Studio IDE? To IntelliSense? To drag-n-drop GUI building? Dropdown menus that show frequently-used items, adjusting themselves over time?

      I'm not trying to troll here, and it's not entirely off-topic. As with a previous post on MS projects that failed, debates about the future of .Net need to be framed in an accurate asessment of Microsoft's history of success and inovation.

      It seems most folks on slashdot believe Microsoft can simply bully its way to the top of any field, forcing people to adopt anythning it produces. Yet products like Bob suggest this isn't true. So, why do some, but by no means all, Microsoft products succeed? Clever copying of proven ideas? Subtle innovation? Reinvention of older ideas, with improvements based on 20/20 hindsight?

      People snipe at the idea of a .Net VM as a Java ripoff. The Java VM is a Pascal P-code VM ripoff, but done better. Java swiped ideas from C++, and improved certain things. Could it be a similar case for C#/.Net?

      --

      Java is the blue pill
      Choose the red pill
    25. Re:It's no use to resist .NET.... by macsuibhne · · Score: 1

      The O/S that Xerox used at PARC was called Pilot, which was written in the Mesa programming language, a high-level language with some similarities to Modula II, to run on Xerox' proprietary D-machine architecture. The operating system ran to some 24,000 lines of code, supporting the WIMP metaphor, shared memory, virtual memory, streams, threads and monitors, and XNS networking and Courier RPC. It came with a built in debugger (called Co-pilot, naturally), which you trapped into in the event of a serious error, at which point you could debug the source. It was released in 1980, the year before the IBM PC and MS/DOS.

      Tony.

      --
      -- "Quis custodiet ipsos custodes?" -- Juvenal
    26. Re:It's no use to resist .NET.... by MrResistor · · Score: 1, Offtopic

      The site you linked is, judging by the snide comments abut Windows' "features", a tad biased.

      That couldn't possibly be because MS has been consistently behind their competition in GUI design. Did you actually look at the screen shots?

      What were the predecessors to the Visual Studio IDE?... To drag-n-drop GUI building?

      One of these might fit the bill.

      To IntelliSense?

      Autocompletion was hardly a new thing. MS seems to be pretty vague about what else it does.

      Dropdown menus that show frequently-used items, adjusting themselves over time?

      I admit I can't think of an example off the top of my head, but then I don't have much more than a passing familiarity with most other GUIs.

      It seems most folks on slashdot believe Microsoft can simply bully its way to the top of any field, forcing people to adopt anythning it produces.

      Perhaps because it often does? OEM contracts come to mind.

      Yet products like Bob suggest this isn't true.

      Some things just suck so bad that no amount of bullying will help (and yes, I have used Bob).

      So, why do some, but by no means all, Microsoft products succeed? Clever copying of proven ideas? Subtle innovation? Reinvention of older ideas, with improvements based on 20/20 hindsight?

      I would replace "innovation" with "variation on a theme", and add the strategy of attrition. Just because a company or product failed doesn't mean there weren't some good ideas there. MS has always been good at picking up those ideas and running with them. Successful? Yes, but hardly innovative.

      People snipe at the idea of a .Net VM as a Java ripoff. The Java VM is a Pascal P-code VM ripoff, but done better. Java swiped ideas from C++, and improved certain things. Could it be a similar case for C#/.Net?

      I never claimed MS was the only one that did that. I just have a problem with them claiming credit for the idea, when anyone who takes a little time to investigate can find that it simply isn't true.

      For the record, I find Windows quite usable. MS has taken a lot of good ideas from a lot of sources and put them into something that works, but none of it is new (with the possible exception of menus hiding stuff, but I actually find that irritating).

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    27. Re:It's no use to resist .NET.... by MrResistor · · Score: 2

      DirectX

      Oooh... an API wrapper! that's origional!

      Optical Mice

      MS didn't invent the optical mouse, they bought it (or stole it, depending on who you ask). Regardless, laser based mice have existed at least as long as Microsoft has.

      Regardless, since *nix isn't hardware, I'd say you're reaching here.

      Scroll Wheel on Mouse (I think this was theirs)

      Again, hardware. I agree that scroll wheels could be a lot easier to set up in *nix, though.

      Back and Forwards Net buttons on Mice

      I saw mice with 10-key pads on them at Fry's long before MS came out with their 5-button mouse. Mapping the extra buttons to Forward and Back may have been new, though.

      The Windows key :-P

      Gotta give this one to Apple with the "open apple" and "closed apple" keys.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    28. Re:It's no use to resist .NET.... by MrResistor · · Score: 2

      either Microsoft are accused of stealling other peoples stuff (hard to do with open standards) or they are ignoring open standards.

      What do you mean "or"? MS has done both on occasion (or at least tried). SMB, HTML, Java...

      As for all the 'nothing new has happened since Xerox' stuff, I suggest the people with that dellusion stop eating the mushrooms and go and use one of the things. OK so you can kinda sorta see the beginings of the ideas we use twenty years later, but they got as much wrong as they got right.

      I never said nothing new had happened since Xerox, just that it didn't come out of Microsoft. MS has consistently trailed in the UI race since it entered.

      I also never said that UNIX was entirely new, either (although it at least started out with some new ideas).

      I don't have an inherent problem with MS taking other's ideas and using them, but I do have a problem with them calling it innovation.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    29. Re:It's no use to resist .NET.... by Helen+O'Boyle · · Score: 1
      All MS has done since they started developing NT is chase *nix. The only thing I can think of that they might have had a head start on is the GUI, but I have my doubts about that, too.

      Ummmm.... I was at Usenix in the early/mid-1990's when someone (Rob Kolstad?) got up and said something like, "Hey folks, how many of you have seen Visual Basic? Now I know we think of Windows as a toy OS, but if you haven't how easy VB makes Windows GUI app coding easy for the masses, you need to go look at it, and get worried." It was a very clear HELLO?!? to the UNIX dev tool community, that they needed to get to work, to play catch up and come up with something that made UNIX GUI app development as easy as VB made Windows GUI app development. Only nearly a decade later did a tool show up that is similarly easy for a typical lightweight IT apps programmer (as opposed to real, CS-trained coders like most of us) to use, to create apps -- and it was Kylix, by *BORLAND*, not a traditional UNIX tool company.

      Say what you will about Java. A monkey can use VB and turn out a data entry form. A somewhat-trained monkey can use Kylix on Linux and do the same. One has to be a bit more skilled to do the same task in any Java dev environment I've seen. UNIX is still trailing Windows in terms of development environments "anyone" can use to turn out good looking, reasonably functional apps.

      The Java people from Sun were at that Usenix. I know this, because there was a demo of the java-to-be product, perhaps even in the same session as the one in which the VB remark was made. So it can't be said that lots of folks didn't have clear hints that GUI app development needed to be monkey-accessible nearly a decade ago.

    30. Re:It's no use to resist .NET.... by MrResistor · · Score: 2

      Do you have any experiance with the interface builders listed here?

      I'm not doubting your story or anything, but details about these tools a pretty sketchy.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    31. Re:It's no use to resist .NET.... by Helen+O'Boyle · · Score: 1
      MrR writes:
      Do you have any experiance with the interface builders listed here [gmu.edu]? I'm not doubting your story or anything, but details about these tools a pretty sketchy.
      Thanks. I'd suggest not doubting my story. I was there, and it struck me by surprise so much that it's one of my more vivid memories from my Usenix-attending days.

      IBM's Visual Age Smalltalk was hampered by its choice of language and speed.

      I'll give you that NeXT had a darn nice dev environment. I didn't do much work on it, but of the interface builders I remember from that day and age, it was the one that worked most like an efficient tool and least like a research project. Still, it was NeXT-only, and NeXT boxes were rare in my neck of the woods in IT departments (where most developers are) even in comparison to AIX, Solaris and HP-UX based boxes. If it's not available for the platforms folks are actually using in the business world, is it truly an alternative?

    32. Re:It's no use to resist .NET.... by Anonymous Coward · · Score: 0

      > Sorry, but I have used Visual Studio.NET and in my humble opinion it is a steaming pile.

      Good. Then we can safely predict that, as Apache did to IIS, Mono is going to be much more successful that Microsoft's implementation of .Net, and freedom, and the progress of Linux, will be preserved. Another Microsoft lock-in scheme down the drain.

    33. Re:It's no use to resist .NET.... by vadim_t · · Score: 1

      Well, I'm not an expert, but I'm pretty sure that the command completion in bash wasn't made after IntelliSense, and menus that show frequently used items on the top probably were already done before in text mode.

      Now, I'd love to hear about a big innovation MS did. Did they invent something comparable in size to multitasking, for example?

    34. Re:It's no use to resist .NET.... by Anonymous Coward · · Score: 0

      That Miguel Icaza guy is an ignorant, B.O. smelling, garlic breathed, bean farting wetback spic.

    35. Re:It's no use to resist .NET.... by MrResistor · · Score: 2

      My objective is not to suggest alternatives, but rather to support my arguement that Microsoft does not innovate.

      As for Unix GUI tools, I have no difficulty understanding why they came around so late in the game. In many ways a GUI is anathema to Unix. Unix was built around the central philosophy of taking many small programs, each of which does one thing very well, and being able to string them together to accomplish complex tasks. GUIs effectively remove that ability.

      Am I wrong? Has someone found a way to implement the pipe graphically? Without the pipe, what advantage does Unix have?

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    36. Re:It's no use to resist .NET.... by Helen+O'Boyle · · Score: 1
      MrResistor writes:
      As for Unix GUI tools, I have no difficulty understanding why they came around so late in the game. In many ways a GUI is anathema to Unix.

      And that is why Unix is anathema to folks who don't read slashdot.

      Clearly, you're not seeing the point I'm trying to make. Perhaps that's because I spent last weekend doing a 200-mile bike ride and am still fried. Or perhaps you just don't get it.

      I'm not saying UNIX isn't a superior platform for folks not afraid of a command line.

      I am saying that for the 99.99% of the world that *IS* afraid of a command line, and the 97% of the developer community which is (sad but true in IT), GUI's and monkey-level GUI builders are where it's at. And for whatever reason (like the "we're better than that; clearly it's an issue of educating users that OUR way is better, not just giving them what they say they want, that we know isn't as good" attitude hinted at in the above post), UNIX platform and tool vendors preferred not to go after that market for a really long time. At the same time, they were fretting about eroding market share. Hello?

      Without the pipe, what advantage does Unix have?
      For one, from a developer's perspective, system call traces that don't require buying multi-hundred or multi-thousand-dollar third party packages, to do the job. ;-)
    37. Re:It's no use to resist .NET.... by MrResistor · · Score: 2

      I probably sounded a lot more "hardcore Unix" than I intended to. I'm fully aware of the need for monkey-level GUI tools on Unix (it just makes me sad) in order to gain popular acceptance, but at the same time I keep running into the limitations imposed by those tools while working on Windows.

      For example, I recently had a strong desire to do some mass database manipulation/extraction at work. The only experience I have with that sort of thing is from my Intro to Unix class, but we use Access for all the databases I have any reason to look at. I figured it would take me a few minutes to work out the syntax to do what I wanted with cut, but I could do it even with my limited knowledge, and hey, we use Windows and it should be even easier there, right? Our IT guy, who's Windows only but definately above monkey level, looked at me like I was mad (or maybe had a disfiguring disease) and said "No! It's not easy to do that at all!"

      Anyway, my point is that I'm all for making the hard things easy, but we need to be very careful that in the process we don't make the easy things hard, or even worse, the clever things impossible.

      For one, from a developer's perspective, system call traces that don't require buying multi-hundred or multi-thousand-dollar third party packages, to do the job. ;-)

      But, there's no reason any other OS couldn't have that, just nobody has done it. The pipe, and the whole philosophy around it, is the thing that sets Unix apart from all the rest.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
    38. Re:It's no use to resist .NET.... by MrResistor · · Score: 2

      1) Drivers
      2) Games
      3) A broad user base


      Interesting. None of those are technologies, per se, neither did any of them origionate with Microsoft. In fact, Unix had all of those before anyone had even heard of Microsoft.

      You and your 3 friends, who couldn't get laid in a whorehouse even if they had a $50 bill hanging out of their zippers

      That's probably true, but mostly because I would be to busy getting my ass kicked by my wife for being in a whorehouse in the first place. I have to admit that I've never attempted this experiment, though, since I've never had any difficulty getting laid, even without the assistance of a $50 bill.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
  3. What are the chances for survival!? by goldenfield · · Score: 3, Interesting

    We all know how MS feels about non-MS operating systems. We all know they're using .NET as a way to lock people into Windows servers and desktops. There's NO WAY they're gonna hang out and let poor Linux play in their reindeer games.

    No...they'll go ahead and change their infrastructure so that it doesn't work with open source code.

    1. Re:What are the chances for survival!? by Anonymous Coward · · Score: 0

      You have no chance to survive make your time.

    2. Re:What are the chances for survival!? by Joe+U · · Score: 1

      'We all know they're using .NET as a way to lock people into Windows servers and desktops'

      Couldn't the same be said for ASP or Win32, how is this any different?

    3. Re:What are the chances for survival!? by mgv · · Score: 5, Insightful

      No...they'll go ahead and change their infrastructure so that it doesn't work with open source code.

      Well, sometimes this works, and sometimes it fails.

      Despite numerous attempts to redefine HTML, its still a fairly broadly defined language, irrespective of what IE will render. .net (the concept) makes alot of sense, its just whether or not you trust M$ to implement it. (No prize for guessing my opinions on that one).

      But M$ do do some things right (Office apps and development suites). .net has the potential to be one of those things, and as long as mono exists also, I look forward to it.

      Michael

      --
      There is no cryptographic solution to the problem where the intended receiver and the attacker are the same entity.
    4. Re:What are the chances for survival!? by mr.+marbles · · Score: 3, Insightful

      even if that happens though the primary goal of the mono project isn't to interoperate with windows apps written for .NET. the point of the project is to make programmers lives easier by providing the tool that would make programming for open source OS easier. MS can't crush the project because it doesn't rely on anything more than the standard they submitted to ECMA. And the development tools are nice even if you wouldn't be able to run MS .NET programs.

    5. Re:What are the chances for survival!? by Anonymous Coward · · Score: 4, Insightful

      Exactly!

      Microsoft's track record with Java alone is reason enough to avoid .NET. Microsoft couldn't even be trusted to stick with the spec...they IMMEDIATELY started changing Java (adding worthless crap like *pointers* to a language that was designed NOT to need it). Why did they do it? Because, this is EXACTLY how microsoft gets ahead--embrace, extend, sieze control, and keep changing the API so no competitors can catch up. CHRIST folks, we've got the MEMOS sent around Microsoft HQ as part of public record. They went out of their way to "neutralize" Java as much as possible. .NET will be NO different. Why should it be? Almost all of Microsoft's former competitors complained that Microsoft had the upper hand--because Microsoft had access to the "hidden" APIs while their competitors did not. Will .NET be different? Why in the hell should it? This tactic has worked for Microsoft OVER AND OVER again. Why throw away a perfectly good tactic that has yet to fail?

      Do you honestly think Microsoft has suddenly turned over a new leaf? This is the company that FAKED EVIDENCE in a court of LAW for God's sake.

      Is Miguel smart? Possibly. Is he smart enough to outwit Bill Gates and his army of monopolists? I doubt it. Just look at the graveyard of those who have tried to dance with the devil...the legacy of the 90's computer industry is a full graveyard.

    6. Re:What are the chances for survival!? by Kindaian · · Score: 1

      Mono will survive because M$ is reported to be porting .NET to BSD...

      So... there will be a trunk for GNU/Linux...

      And any other OS that gets inspiration from BSD...

      Cheers...

      P.S.- I would suspect that XP is based in BSD but as i don't have access to XP sources or time to stroll at BSD sources... alas...

    7. Re:What are the chances for survival!? by Anonymous Coward · · Score: 0

      The architecture of BSD and NT aren't even remotely similar.

      Please just go die somewhere.

    8. Re:What are the chances for survival!? by Osty · · Score: 2, Informative

      Mono will survive because M$ is reported to be porting .NET to BSD...

      Already been done. It's called Rotor, and is a Shared Source project, meaning you can see the source and modify it for non-commercial uses, and it even has a nice clause saying that you can't taint yourself by looking at the code (oh, if only the GPL had such a clause. Instead, I can't look at GPL'ed software for fear of tainting my thought processes and inadvertantly ending up with GPL'ed code in software I write). Rotor is mostly meant for academic use and study, and is just a reference implementation (for instance, the GC is very primitive, and is much better in the .NET runtime from Microsoft). However, it builds for both Windows and FreeBSD (probably other BSDs).

      So... there will be a trunk for GNU/Linux...

      Not from Microsoft. You could probably compile Rotor with minor changes on a Linux system, but it'll be completely unsupported by MSFT (well, more unsupported than Rotor already is, which doesn't have any official support but the dev team helps out when they can).

      P.S.- I would suspect that XP is based in BSD but as i don't have access to XP sources or time to stroll at BSD sources... alas...

      You'd be wrong, of course. The reason people bring this up is because Microsoft once used the reference implementation of the TCP/IP stack which just happened to come from a BSD (hrm ... the BSD license is very liberal, not forcing you into any specific license, which makes it perfect for providing reference implementations -- anybody can start with that implementation and change it how they please and not be stuck with the GPL). XP is based on Win2K, which is based on NT4, which is based on earlier NTs, which ultimately derived from the same people that wrote VMS, so you could say that XP is a descendant (several generations removed) of VMS, but you won't find much (any?) VMS code in XP since NT wasn't directly based on VMS (just the concepts and ideas). (Throw some OS/2 in there, just to be complete.) However, XP != BSD, nor would I expect Microsoft to release any BSD-backed (or other *nix-backed) OS in the near-to-mid future (who knows about the long term, really? It's probably safe to say "not likely" here).

    9. Re:What are the chances for survival!? by ClosedSource · · Score: 2, Informative

      "We all know they're using .NET as a way to lock people into Windows servers and desktops."

      Lock people into Windows servers, maybe, but not into Windows desktops. Although MS only supports running ASP.NET on a Windows server, the client receives pure HTML that can be viewed in any browser on any platform. Most of .NET is platform independent on the client side.

    10. Re:What are the chances for survival!? by joshsnow · · Score: 2, Interesting

      They can change their infrastructure as much as they like - what they can't change is the fact that the APIs are out there, they're implemented and they're being used. That means that so long as MONO mirrors those apis, mono apps will always work with the original .NET framework.
      It's like all the old Windows 3 programs which still run on XP - Microsoft can't afford to ditch old APIs. Once .NET reaches critical mass (ie the point at which there's so much software that "changing their infrstructure" breaks code) MONO needs only be implemented to that standard and then we're all home and dry.

    11. Re:What are the chances for survival!? by dawnsnow · · Score: 1

      While I agree with you that MS won't be happy if mono /unix become more popular platform than windows, as long as they steal programmers and companies from java world, I think MS will be happy.

      I think .net is more nice framework than java/j2ee. .net already has not only C# but visual basic, C++, eiffel and etc. Only other popular language than can run on java runtime is jython(python). And I'm sure jython people can easily ported their code to .net. After all, all the nice new features of C# is copied from java.

      Think about it. If this trend continue, lot of current language developers want to port their language to .net. And .net will be their favorable choice.

      As long as MS makes damn good development tool, eg. Visual Studio .net, Windows will be major platform to develop software, whether the software will be deployed on mainframe Unix (assuming it has .net framework either by MS or mom), or other desktop.

    12. Re:What are the chances for survival!? by Darkling-MHCN · · Score: 1

      The chances are extremely good.

      Part of what you say is true.

      I've been developing with .NET for over a year now and it definitely does contain alot of functionality that leverages features of the windows operating system e.g built in windows security & authentication functionality. As such to leverage the full power of .NET people could be seduced into deploying a full MS environment.

      However that is not to say that there isn't a large amount of functionality that is platform independent ie solely reliant on the CLR and not leveraging Windows OS features. In fact I would say that the majority of features in .NET are independent of Windows and based on Open standards. Even things like System.DirectoryServices which is used to access Windows 2000 Server Active Directory's might be able to be developed on Linux as Active Directory is based on an open standard - LDAP.

      I think a large part of what you're saying is very untrue in that I dont believe MS is going to anything other than encourage and foster development on the Mono project as it's success is clearly in MS's favour.

      Looking at the larger picture MS clearly has bigger fish to fry than Linux. Sun would clearly be in it's sites... with J2EE and Solaris the very clear target of .NET. Linux and Mono offer a great migration path from Sun and is clearly an easier path than moving from J2EE/Sun Solaris to .NET/WinNT.

      Depending on your attitude and how paranoid you are this could be a true win/win relationship for Linux and MS.

      Increased momentum for Linux and decreased momentum for Sun.

    13. Re:What are the chances for survival!? by ealar+dlanvuli · · Score: 1

      Just to correct you, w2k, WME, and WXP all use a prety much cut-n-paste 'BSD network stack.

      It's rather sick that they didn't even bother to give a tip of the hat for 'borrowing' that code.

      --
      I live in a giant bucket.
    14. Re:What are the chances for survival!? by Anonymous Coward · · Score: 0

      congrats. you have completely misunderstood what .NET and SOAP are all about -- completely misunderstood.

    15. Re:What are the chances for survival!? by Planesdragon · · Score: 1

      This tactic has worked for Microsoft OVER AND OVER again. Why throw away a perfectly good tactic that has yet to fail?

      Because the US. Government is suing them for that tactic. It's a good bet that in two or six years they'll be a different administration in the white house, that'll be more than willing to correct the slap-on-the-wrist punnishment that MS is aiming for.

      Changing their tactics to encourage other companies to support them & make indirect money doing so is a VERY good strategy for Microsoft.

      If I came to your house, with godlike computing powers, and offered to make you an OSS system that does everything that MS's latest idea did, wouldn't you use it? History says *YES*.

      As for those who tried to "dance with the devil"... Dell, Gateway, Intel, NVidia, Apple, and AMD all seem to be doing just fine, at least in large part to a mid-90s alliance with Microsoft.

    16. Re:What are the chances for survival!? by ClosedSource · · Score: 1

      By all means enlighten us.

    17. Re:What are the chances for survival!? by Anonymous Coward · · Score: 0

      ftp.exe: Copyright (c) 1983 The Regents of the University of California. All rights reserved.

      You were saying...?

    18. Re:What are the chances for survival!? by ealar+dlanvuli · · Score: 1

      grep for "BSD" on everything (or at least the executable/library stuff) in your windows directory, compare that to the credit given for that code, see deficit, laugh.

      --
      I live in a giant bucket.
    19. Re:What are the chances for survival!? by rsborg · · Score: 2
      Although MS only supports running ASP.NET on a Windows server, the client receives pure HTML that can be viewed in any browser on any platform

      MS has already wrapped up that problem. Do you notice how many sites are not Mozilla friendly?
      Hell, even my company (a *large* enterprise software firm) produces supposedly "pure" html that coincidentally happens to not work on anything but IE.

      They have browser marketshare. They still have OS marketshare. Network effect of both platforms will keep people from straying, regardless of what "standards" exist. For complete dominance, they are attempting to crush Sun by eating their Java lunch.

      Go ahead, support the monopolist, foolish developer. Cry me a river when your "pure HTML" is required to break W3C standards to comply with next version of IE.

      --
      Make sure everyone's vote counts: Verified Voting
    20. Re:What are the chances for survival!? by Anonymous Coward · · Score: 0

      MS did office apps right? I can't believe I'm hearing that! The number of times I have sat literally screaming at Word because it has made it's mind up that I wanted something done in a particular way, and no matter what I do or which options I check or uncheck it continues to arse about with my intended format...... Back in the days of Amipro words stayed where they were put and didn't quietly morph into something else. Now THAT was a wysiwyg word processor to contend with. Come to think of it, 1-2-3 was a better spreadsheet than Excel as well. This "MS makes great office apps" line is BULLSHIT. They just sell the most.

    21. Re:What are the chances for survival!? by sql*kitten · · Score: 2

      We all know how MS feels about non-MS operating systems. We all know they're using .NET as a way to lock people into Windows servers and desktops. There's NO WAY they're gonna hang out and let poor Linux play in their reindeer games.

      FUD, fud fud. Get your complete C#/.NET development environment, including source code, for FreeBSD here.

    22. Re:What are the chances for survival!? by HiThere · · Score: 2

      To the extent that MS has control over .net, then it should be avoided. You are totally correct. You can, indeed, trust them ... to act like MS.

      The question is, to what extent can one depend on .net to stand independant of MS? To what extent is it vulnerable to copyright or patent claims?

      I sure don't know the answers to these, and until I find out, I'm not inclined to invest time in learning it. And, coming from MS, I'm not that interested in wasting time looking for the answers. I have these strong suspicions that there may be "submarine" patents... perhaps not in the traditional form, perhaps hidden by obscurity, or strange phraseology, or simple sillyness "A patent on the use of #. as demarcation in namespaces" or some such.
      Or it could be a trademark. True, you are required to defend trademarks, but not until you know about the violation. If MS has a trademark on the use of something that exists in the guts of .net, then the code would need to be altered so that all the uses had a trademark symbol, and then the compiler would need to be altered to ignore that, and then...

      I don't really know what to expect from them. Just that it will more than likely be unpleasant. It's been at least decades since they have done something that ended up being to my advantage. And I don't think they ever did anything that they didn't believe was to their advantage.

      If .net is successful, it would be effective action from MS against Sun, so it's possible that they've made a fair offering. But given their past history, I don't trust it. Not even enough to examine it carefully. (It's too easy to be fooled.)

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    23. Re:What are the chances for survival!? by ClosedSource · · Score: 1

      So you are claiming that the HTML returned returned by ASP.NET is not compatible with Mozilla. Any evidence to back that claim up?

    24. Re:What are the chances for survival!? by alext · · Score: 2

      I can't seem to find the Windows Forms API in that download - can you help me out?

      Or perhaps you meant:

      complete Dotnet development enviroment, except for the 90% of classes that are only available on Windows?

    25. Re:What are the chances for survival!? by rsborg · · Score: 1
      So you are claiming that the HTML returned returned by ASP.NET is not compatible with Mozilla. Any evidence to back that claim up?

      Javascript is broken on IE, so in order to "fix" things, you have to write for two platforms, IE and everyone else.

      If you can't see why this will make your page unrenderable with Mozilla, when IE is broken w/r/t standards, I wont try any further.

      --
      Make sure everyone's vote counts: Verified Voting
    26. Re:What are the chances for survival!? by ClosedSource · · Score: 1

      There is no client-side scripting using ASP.NET so it doesn't matter how IE or Mozilla handles Javascript. The whole point is to return only HTML.

      From a developer's point of view, the only purpose ASP.NET serves is to be platform and browser independent on the client side. If it doesn't deliver that, no one will use it. There are much better solutions than using a browser if one wants a Windows-only application.

  4. MOD TO FLAMEBAIT by Anonymous Coward · · Score: 0

    cause you're all anit-M$ here. damn anarchists

    1. Re:MOD TO FLAMEBAIT by FooBarWidget · · Score: 1

      > so just let them do what they want cause it's inevitable?

      You know, *a lot* of people say things like "Who cares? It's like like it will help a damn thing if I don't use their products. All I care about is their code, and right now, Windows XP contains great code.".

      Don't blame me. Blame everybody else.

  5. Who else is amused... by modulus · · Score: 5, Interesting

    That this "phonic" thing, built with the ultra-portable .net dealy, still only runs on linux (or at least nix-ish) machines with gtk?

    On a more serious note...

    Seriously. Where's the portability at? Will .net apps written for windows similarly only work with the "windows gui toolkit" (or whatever)?

    1. Re:Who else is amused... by Anonymous Coward · · Score: 0

      Il looks as if it works on windows, but not with Microsoft .Net runtime...

    2. Re:Who else is amused... by Tralfamadorian · · Score: 1

      I don't know very much about .NET, but I think that there are plans for mono to implement Linux/MacOSX/Other versions of the Windows.Forms namespace....

      Again, I am not completely sure what this is all about, but from what I've read, this would be similar to Java's AWT (though probably more advanced, like IBM's SWT which implements more advanced widgets even if the underlying toolkit doesn't support them).

      But you're right, as it is, GTK# doesn't work on windows, but it might in the future.

      But hey, it's a .NET app for linux, that in itself is interesting.

    3. Re:Who else is amused... by Koyaanisqatsi · · Score: 2, Interesting

      Will .net apps written for windows similarly only work with the "windows gui toolkit" (or whatever)?

      Yes, they will. As soon as the implementation of the Windows.Forms classes are implemented. That's within the scope of the project and is a big challenge, check it out here.

    4. Re:Who else is amused... by Osty · · Score: 1

      But you're right, as it is, GTK# doesn't work on windows, but it might in the future.

      And that's the problem. There shouldn't need to be any such thing as "GTK#", because Mono should be implementing Windows.Forms instead. It would then be the responsibility of the runtime on whatever system to translate these Windows.Forms calls into some widget set (Windows.Forms on Windows already translates these to Win32 calls, I believe the Rotor implementation for FreeBSD translates Windows.Forms to TK, and Mono should be implementing a GTK backend for this). The other plus for this is that if Mono in the future decides to use QT, or upgrades the runtime to use a newer, incompatible GTK version, there should be no change to the .NET app. You're not tied to GTK, just .NET. How the runtime implements Forms is not (should not be) a concern for the app-level programmer.

    5. Re:Who else is amused... by andrew_lewis · · Score: 1

      Amen to that!

    6. Re:Who else is amused... by Anonymous Coward · · Score: 0

      AMEN,

      This really shows platform dependence, and therefore you will need windows to run the "cool" .NET apps ...

      No thanks

    7. Re:Who else is amused... by calarts_nutmeg · · Score: 4, Insightful

      That's the biggest problem, .Net isn't as portable as java, also java is meant to be a great kitchen sink system, with everything from multimedia to raw socket connections. Also, if you don't like java, you can use python with jython to write java class files using a simple scripting language. Java is just so rich, the api has so many goodies to choose from, and the apps can be easily adapted from J2SE to the simpler J2ME CLDC, you still can only use C# to write desktop applications, and having it run clients on the handheld really isn't in the cards for c#, since all applications are supposed to run on MS servers. True I suppose things are getting ported to C#, but still, why go to all the effort to learn it when Java has such a huge head start, and Sun isn't try to kill linux either.

      --
      Check my site out for ogg vorbis music produced with linux.
    8. Re:Who else is amused... by Anonymous Coward · · Score: 0

      Because AWT was such a major success.
      The precise behavior, look, etc should be specified for WinForms and then they should, if anything, be designed using GDK for a target, not GTK.

    9. Re:Who else is amused... by samael · · Score: 4, Informative

      You can call non .NET programs from within .NET. If you decide to use a library that only exists in Windows (like DirectX) or in Linux (like that version of GTK) then of course it only works in that system.

      Once more of Mono is complete, you'll be able to do the whole of your program in it, including the libraries, and moving between Windows and Linux will be transparent.

    10. Re:Who else is amused... by joshsnow · · Score: 1

      .Net isn't as portable as it's made out to be - yet. AFAIK, the GTK# bindings are differerent to the Windows.Forms namnespace which Mickeysoft supply with their .net framework.
      So until XIMIAN/AN-OTHER reimplement the Windows.Forms namespace (all the Windows widgets basically) as GTK components, a Windows .NET GUI won't work in GNOME.
      Also of interest; The .NET framework is available as a free download for windows. Also, you don't need to buy/warez Visual Studio.NET - there is a Free (GPL) alternative which is shaping up quite nicely; SharpDevelop

    11. Re:Who else is amused... by jimmu · · Score: 1
      Seriously. Where's the portability at? Will .net apps written for windows similarly only work with the "windows gui toolkit" (or whatever)?
      Actually, yes. Its the System.Windows.Forms namespace. It contains all the objects and classes for GUI apps on windows, and it does only work on windows. The rest of the .net stuff will work (to my knowledge) on any system with the framework installed, but all the GUI stuff is windows only.
      --

      ----
      One of us needs to stick ones' head in a bucket of ice water.
      - Hobbes
    12. Re:Who else is amused... by Anonymous Coward · · Score: 0

      You can write non-client C#
      C# (not even counting all of .NET) is better than Java (the language).
      Microsoft has a large deployment base. Lots of people will learn and use C#, because that can mean a job.
      Microsoft has submitted C# and some of .NET to a standards body.
      Microsoft is going to do the work to port to BSD.
      Microsoft Labs members have and continue to make efforts supporting the use of other non-traditional languages on .NET.
      Microsoft isn't afraid to design a platform for performance, unlike Sun.
      C# and .NET will be used on WinCE handhelds.

      Common Java runtimes still run like ass, and the language is a piece of crap.

    13. Re:Who else is amused... by Osty · · Score: 1

      quoting the whole parent, for it was from an AC:

      Because AWT was such a major success.
      The precise behavior, look, etc should be specified for WinForms and then they should, if anything, be designed using GDK for a target, not GTK.

      I can only assume you were being sarcastic about the success of AWT, so I won't bother with that. However, as far as Look&Feel goes, I believe that Swing got it wrong. According to Swing (and things like Mozilla's XUL), it's important for your application to look exactly the same across all systems on which it runs. I disagree, as do many others. Instead, your application should adopt the look&feel of the target platform you're using. Do you really want an ugly GTK-looking thing on Mac OS X? It will look really out of place among all the pretty OS X apps. Same goes for on Windows XP. The new Visual Style theming capability is great, but I get annoyed when I use an app that doesn't support visual styles. All of my other apps look great, all of them using the same theme. But there's just that one that looks completely out of place. No, it's better for something like this that you implement the backend using native widget sets, and your runtime will take care of figuring out what it should use (depending on where you're running of course).

      The problem with AWT is that it was basically dumbed down, trying to find a least common denominator API that would make it easy to implement AWT for most platforms. Rather, a better approach would be what Windows.Forms does. It defines certain things (you have forms, buttons, scrollbars, toolbars, etc). Sure, a lot of these things are drawn directly from Windows, but they can be implemented on many other platforms as well. Maybe your GTK-based backend has to munge together three or for different widgets to implement some single widget in Windows.Forms, but that's okay. You do it once in the runtime, and then you don't ever have to do it again, and you don't limit the high-level API based on the limitations of the underlying API. If that means that Mono does end up just scrapping GTK and going directly down to GDK, so be it. I personally think they can implement Windows.Forms just fine using GTK.

    14. Re:Who else is amused... by GorgarWillEatYou · · Score: 1

      Why add another layer in. Windows Forms is a Wrapper around win32 calls why make it wrapper around gtk or qt or anything. Wrap the bare bones xlib and be done with it.

    15. Re:Who else is amused... by Tralfamadorian · · Score: 1

      But that's the thing...

      the people working on mono WANT to implement Windows Forms, they just have to do it. On their page it reads that they want to implement it with GTK+ on Unix platforms, and with Cocoa on OS X.

    16. Re:Who else is amused... by badzilla · · Score: 1

      Why? Perhaps it's not just pure technical issues.

      Java : proprietary to a large foreign corporation, you currently get to use it for no charge if you agree to their licensing terms. Free, as in beer.

      C# : Open standard (ECMA 334 and 335.) Free, as in beer AND also Free, as in speech.

      Does this count for anything?

      --
      "Don't belong. Never join. Think for yourself. Peace." V.Stone, Microsoft Corporation
    17. Re:Who else is amused... by danielwright · · Score: 1

      That's just not correct. The .NET Compact Framework is the exact functional equivalent of J2ME - it will run on Windows CE / PocketPC devices at least (and possibly others). Admittedly, it is still in beta, but the .NET SDK was only released a few months ago, so that's not surprising. On a similar note, the .NET Framework APIs are maturing in future versions, so it won't be long until they are functionally equivalent to the Java APIs (they are already pretty close, at release 1.0).

    18. Re:Who else is amused... by Joe+Tie. · · Score: 1

      Instead, your application should adopt the look&feel of the target platform you're using. Do you really want an ugly GTK-looking thing on Mac OS X?

      That's why they should be using skinlf, if they want a pretty OS X'ish gui. Aparently it can even automaticaly load current themes being used in Linux. I havn't tried it yet, but pretty cool if it works as advertised.

      --
      Everything will be taken away from you.
    19. Re:Who else is amused... by Anonymous+Hobo · · Score: 1

      And, to be pedantic, Java isn't as portable as C.

      --
      .
    20. Re:Who else is amused... by Anonymous Coward · · Score: 0

      Or as fast, and just to rehash old news, Java is a C++ derivative (a semi good one). C# is also a C++ derivative (guess what - looks something like java), but they got alot of stuff right that Java hasnt done yet. I think the framework 1.0 .Net is as good or better than the Java class libs, and certainly has much better management functions to make developers produce better code.

    21. Re:Who else is amused... by Osty · · Score: 1

      Two problems with that.

      1. Look: You're relying on skins to match the look&feel, which means you either pick a skin and use it on all platforms, or you have to programmatically figure out which platform you're on and pick the most-appropriate skin. Giving the user the option to pick their theme would work, too, but that's a bit of a cop-out if your goal is to fit in with the L&F of a given platform.
      2. Feel: Assuming you figure out #1, you still have the issue of "feel", or more precisely "consistency". Just browsing the screenshots, it appears that the themes don't actually change the "feel" of any widgets, only the look. That means things like scrollbars are always going to have the NeXT-style arrows, even though things like Windows don't use those types of scroll ends. So, even though your app may now look like a native app, it's not going to act like one.
      Skins can only do so much. In this case, I think choosing to use skins is a suboptimal solution. Why go to all the trouble to implement skinning in your application, when you could get native-L&F compatibility for free (and be able to leverage any system/widget kit-wide skinning capabilities) if the runtime was simply developed correctly?

      Of course, exceptions can be made. Just as my own personal rule of thumb, if the application is "arty" (a media player, movie player, fancy image viewer, etc), then making it skinnable separate from the OS is a viable option. However, if the application is more mundane, like a word processor or some business app or an IRC client (this could probably fit in either category) or a web browser (good example: galeon; bad example: mozilla), you should try to blend into the look&feel for your target platform (.NET is a platform, but here I mean the platform on which the .NET platform is running and not the .NET platform itself). Of course, there have been numerous apps that have broken this rule of thumb (ever see the old IBM apps that came with the consumer Aptivas? a PIM that looked like a day organizer, a phone app that looked like a phone, etc. They were horrible. Even the CD player that looked like a CD player was awful, and I'm usually okay with media players being funky).

    22. Re:Who else is amused... by UranusReallyHertz · · Score: 1

      It would if it were ANY other company than Microsoft. This IS /. after all!

      --
      Smoking is an expensive, slow, and unreliable method of suicide.
    23. Re:Who else is amused... by Malcontent · · Score: 2

      Will it run on palms?

      --

      War is necrophilia.

    24. Re:Who else is amused... by mark_space2001 · · Score: 1
      > You can call non .NET programs from within .NET.

      Ugh. Sounds like a security hole big enough to drive a double rig full of viruses (viri?) through. At least Java puts some conrols on the abilities of a running Java program.

    25. Re:Who else is amused... by Anonymous Coward · · Score: 0

      ...which you can just as easily bypass.

    26. Re:Who else is amused... by Anonymous Coward · · Score: 0
      Funny, people have been writing extensions to Java every since the thing came out, exercising they're free speech.

      Things like Pizza and GJ for example. The restriction is that Java is trademarked by Sun, so the extensions can't call themselves Java, which is quite reasonable.

      Why don't you try to do a little backup search next time you motherfucking troll whore.

    27. Re:Who else is amused... by Anonymous Coward · · Score: 0

      go whine somewhere else, bitch

    28. Re:Who else is amused... by Anonymous Coward · · Score: 0

      Weell guess what, C# isn't as fast as C either, or any faster than Java. Duh. C# designers also added a whole lotta crap to the language to please the old C++ developers. It is much closer to C++ than Java is, and in my book therefore much poorer language (cause everyone should stay as far as possible from that shit pile they call C++)

    29. Re:Who else is amused... by liloldme · · Score: 1, Insightful
      C# (not even counting all of .NET) is better than Java (the language).

      No it's not, the language sucks, as can be read from this FAQ for example.

      Microsoft has a large deployment base. Lots of people will learn and use C#, because that can mean a job.

      A quick search on Monster.com does not support this claim.


      Microsoft is going to do the work to port to BSD.

      Yeah or so they say... big fucking deal, Java already runs on dozens of different platforms.

      Microsoft Labs members have and continue to make efforts supporting the use of other non-traditional languages on .NET

      JVM supports more languages than .NET ever will.


      Microsoft isn't afraid to design a platform for performance, unlike Sun

      There is no speed difference, both platforms run on a virtual machine.

      C# and .NET will be used on WinCE handhelds.

      Will be? oh oh ... well how about Nokia ships millions of cell phones already with Java embedded? WinCE is dead.

      Common Java runtimes still run like ass, and the language is a piece of crap.

      You're just a pathetic little shit who hasn't got a fucking clue what you're talking about.

    30. Re:Who else is amused... by liloldme · · Score: 1
      I can only assume you were being sarcastic about the success of AWT, so I won't bother with that

      No the point he was making is AWT failed because it was such a fucking pain in the ass to tweak the GUI for all different platforms when native peer widgets were used. Therefore Swing came about to solve that problem.

      I believe that Swing got it wrong. According to Swing (and things like Mozilla's XUL), it's important for your application to look exactly the same across all systems on which it runs.

      Again, you're wrong. Swing supplies L&F for different platforms (Motif, Windows, Mac) and one cross platform L&F. The point of Swing was that to the

      programmer there's no difference what platform it is being run on. If I develop on Windows I can be sure the L&F doesn't suck on Mac. This Swing achieved very well. Any attempt going back to native peers (ala SWT) will again suck, you have to test the app on every fucken platform.

      Instead, your application should adopt the look&feel of the target platform you're using

      That's what Swing does.

      Do you really want an ugly GTK-looking thing on Mac OS X?

      No, with my Swing apps that is automatically switched to MacOS L&F. I don't have to do a thing.

      No, it's better for something like this that you implement the backend using native widget sets,

      It was tried and it failed. This is one of the reasons I'm not too keen on using .NET -- these problems were seen and worked around in Java years ago. Do I want to go through that same pain again? No thanks.

    31. Re:Who else is amused... by Anonymous Coward · · Score: 0

      more biased crap...

      I'm looking for a job at the moment - I call agencies and they say 'how much .net experience do you have?'. I say 'none' they say 'oh'.

      A surprisigly large number of jobs are looking for people with .net experience (that's commercial experience BTW).

      try this: http://www.it.jobserve.com/jobserve/searchresults. asp?jobType=*&d=5&order=Rank&page=1&q=c%2B%2B+and+ .net

      143 results. says a lot for my future career in a platform that's only just been released.

    32. Re:Who else is amused... by liloldme · · Score: 1
      Uhh... you do realize that .NET exp just means VB to them -- I'm not saying there arent a whole lot of VB jobs out there, but that there isn't suddenly more .NET jobs available. That hasn't changed one bit. It is just all the jobs that used to be VB exp is now .NET exp.

      So yeah if you were a VB developer then sure it makes sense to "upgrade" yourself to .NET (I mean you've already chosen to go down that dead end path anyway, it's not like it makes much of a difference to you now). There's absolutely no reason for anyone doing real programming jobs to start learning .NET though. Unless they're keen on taking the old VB monkey programming jobs that they now call fancy .NET experience.

    33. Re:Who else is amused... by croanon · · Score: 0

      >>You can write non-client C#
      So What??

      >>C# (not even counting all of .NET) is better than Java (the language).
      But Java is working anyway. :) And it has been working for 7 years. It is tested, optimized, getting better and better. All the big firms except for MS is embracing Java anyway. There are hundreds of ready to use libraries, frameworks, successful open source projects, millions of Java developers. The runtimes are getting better and better. It supports real WORA promiss. It will be #1 known language next year. Who cares about C# when there is Java?

      Microsoft has a large deployment base. Lots of people will learn and use C#, because that can mean a job.
      And good thing is C# is very close to Java. (Actually it is copy of it with different syntax, and not so important fixes/improvements etc.) So, it will be easy for people to move to Java.


      >>Microsoft has submitted C# and some of .NET to a standards body.
      Which is nothing. Standards my ass. First they did not standardized every aspect of .NET. Many important parts are not standardized. They can change those parts and all those work would explode in Icaza's ass. You would have propriatery .NET implementation for Linux, which would not work better than Java. It is another VM anyway.

      >>Microsoft is going to do the work to port to BSD.
      Of course they would, since they are planning to release BSD based OS in the future as far as I know. They will start polluting BSD with Windows propriatery .NET libraries from the start.

      Microsoft Labs members have and continue to make efforts supporting the use of other non-traditional languages on .NET.
      Which is again useless, language bindings do not work fast. They will never ever work fast enough. It is not efficient to call unmanaged code from .NET. My firm tried it, and abandoned it at once, after seeing the huge performance hit. Do not get me wrong. JNI also do not work fast too. No legacy code linking in the world produces results that would make project managers feel confortable. So, forget about calling already implemented code from .NET. It is more related with problem domain. Only some problem domains may permit it.

      Microsoft isn't afraid to design a platform for performance, unlike Sun.
      Are you nuts? Did you ever see .NET and JVM comparisons? They are not much different. Even Java is faster in many cases.

      C# and .NET will be used on WinCE handhelds.
      So what? What I am supposed to do with crap Win CE? On mobiles and handhelds, Java is already becoming a de facto standard. Read some before posting.

      Common Java runtimes still run like ass, and the language is a piece of crap.
      Do you know something called rimmming?

      --
      Dear Bill, do you have a .net tatoo on your ass for marketing?
    34. Re:Who else is amused... by Anonymous Coward · · Score: 0

      You must be clinically retarded. Or work in the Sun Marketing Dept.

      Java and .Net both consist of 2 separate pieces:
      a virtual machine (CLR, JVM); and a language on top of it that gets compiled into bytecode. You can compile java (source code) into java VM code. You can use Jython to produce java VM code. You can even use a Java VM assembler to write Java code in assembly language.

      Likewise, you can compile C# code into .Net CLR. Or compile VB.Net code into .Net CLR. Or compile Visual C.Net code into .Net CLR. Or compile Perl.Net code into CLR. OR code in .Net assembly. Last I checked, there were over 30 3rd party (non-MS) languages being modified to generate .Net CLR code.

      As for portability, consider this: MS has had C# and .Net certified as open standards, something Sun has refused to do with Java.

      As for desktop/Server, check the sample code on MSDN. Half of it is server/backend stuff.

      Also, hate to burst your bubble, but MS has a Windows CE .Net framework in beta, and Palm Source is including .Net compatability in their next major version of Palm OS.

    35. Re:Who else is amused... by GooberToo · · Score: 2

      Gtk# doesn't currently work on Windows as the Microsoft runtime is incompatible with Gtk+ libraries that aren't linked with MSVC's lib.exe tool. Tor Lillqvist's Gtk+ for Windows won't work. While there's no active effort within the Mono project to recompile the DLLs, you're welcome to try yourself. build-dll is an example of how this has been achieved in the past.

      This is something I try to point out from time to time. Until there becomes a defacto GUI widget toolkit for all .NET platforms, saying .NET and MONO allows for cross platform development is ultimately an invalid assertion.

      Unlike Java which provides its own GUI toolkit, most MONO applications are going to use their own native widget set. That means on Windows, MFC and on Unix/Linux, Motif, GTK+, Qt, FLTK, etc. Since few of these toolkits have .NET bindings, let alone are cross platform, it means writing all of the GUI over again for each perspective platform.

      Tell me again why I'd waste my time?

      If I want cross platform, I can already use Python + wxWindows (wxPython) or even Java to truely be platform indepenent. So please, tell me why I'd waste me time with Mono, let alone C# in general.

      Shesh...what a waste of resources.

    36. Re:Who else is amused... by Anonymous Coward · · Score: 0

      We went through this whole security issue the last time this came up. And the time before that. And the time before *that*. Go try to read a little about the .NET platform before you comment again. Or just pay attention.

    37. Re:Who else is amused... by HiThere · · Score: 2

      To be fair, MS has put a reasonable amount of effort into getting other languages available for the .net platform. Of course, most of them had to be butchered to make them fit...

      There's this old story about this chap called Procrustes...

      Eiffel had to be butchered into Eiffel#. Yeah, they got Bernard himself to do it, but I still say butchered.

      If I understand correctly Perl is implemented via a .com interface (did I really hear that correctly?).

      C++ was turned into C#, eliminating multiple inheritance. I'll agree with everyone else that C++ had a lousy model for multiple inheritance, but there are problems that interfaces just don't handle nicely.

      etc. (Well, to be honest, that's about all the languages I know about.)

      And what you end up with is another JVM, only incompatible. And the guts are controlled by MS.

      I might be willing to *use* .net on Linux, if it were convenient. For small projects. If it didn't need to be portable. If I want portable it seems to me my choices are Python, Ruby, Java, Eiffel, C, C++, Ada, Haskell, Scheme, Lisp, ... (the only problematical ones on the list are C and C++, but I figure that with gcc it counts, even if you do need to use twisted defines.)

      And of these choices, the only one that does graphics portably (well, and that I know well enough to try to do graphics in) is Java. If only dialogs are needed, then I can use Ruby or Python, and Tcl or Fox.

      None of these are C#, though it may someday join the list. What is its special advantage? It's certainly not more portable than Python, Ruby, Java, or Ada. I just don't see the point.

      If I want portable speed, I 'd use Ada. Totally standard on all platforms. Very powerful object model. A bit static and finicky, but powerful, fast, rugged, stable, etc.

      If I want something flexible, I'd pick either Ruby or Python. They're pretty evenly matched in most places. Python has better libraries, I like Ruby's syntax better. Both link easily with routines in C for spots where you need to optimize. (Well, really it's for calling precompilled libraries. You need to be doing something pretty significant for the overhead to justify the linkage problems and costs.)

      If I want a portable graphic environment I'd choose Java. Python could probably handle this, but Java is better at it.

      I'm sure that C# must have some advantages, but I don't know them. When should I choose to use them, outside of when I need to talk to another C# program?

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
  6. I've not been following this very closely by Anonymous Coward · · Score: 0

    Has .NET started to be deployed, or is it still on the drawing board?

    1. Re:I've not been following this very closely by Anonymous Coward · · Score: 0

      Visual Studio .NET was released in February with the final .NET framework. Windows .NET server will be released early next year.

  7. subtle answer to troubling question by Mojojojo · · Score: 1, Insightful

    So Miguel provided an answer to something that's been troubling me...COM. He mentioned having to emulate some win32 stuff. MS hasn't done away with COM, just wrapped it with .NET, so I've always figured any free alternative would never really work since it would have to support COM to run windows programs that strayed from .NET only code. Nothing in .NET replaces the generic interfaces you can make and program to in COM... I'm curious what the future will hold.

    1. Re:subtle answer to troubling question by k2enemy · · Score: 1
      i don't think the mono project plans on providing real support for non 100% .net code. i believe the emulation of win32 is in relation to the implementation of Windows.Forms, not providing support for COM. i could be wrong, but this is what i've gathered from reading about the project.

      from the faq:
      Will you support COM?
      The runtime will support XPCOM on Unix systems and COM on Windows. Most of the code for dynamic trampolines exists already.

    2. Re:subtle answer to troubling question by feldkamp · · Score: 2, Insightful

      while microsoft is going to support COM, they do want it to fade away in favor of .net components...

      There are .net equivalents of generic COM interfaces.

      Honestly, though, I think there is just too much invested in COM by various companies to get away from it, at least within the next 10 years.

    3. Re:subtle answer to troubling question by Anonymous Coward · · Score: 0

      Presumably some of the COM stuff would be wrapped as CORBA.

    4. Re:subtle answer to troubling question by Anonymous Coward · · Score: 0

      Think you have misunderstood something
      about the .NET / COM connection ..

      COM support in .NET is just there to make
      legacy COM code to be called from the framework, just like old "c" code in a dll .NET applications don't need to do single
      call to anything COM, unless it ofcouse
      needs some functionality in a legacy
      COM control or something .NET do replace those generic Interfaces you
      used when programming with COM

    5. Re:subtle answer to troubling question by Anonymous Coward · · Score: 0

      When will Microsoft come out with .ORG and .CC? The FSF is already rolling out G.NU. LAME names.

    6. Re:subtle answer to troubling question by gakguk · · Score: 1

      COM interop and PInvoke is a pain in the ass. Although developing on top of .NET is nice and easy, it gets much more difficult when you have marshalling in between two pieces of your code. COM interop is also a resource killer, they don't support it on small devices with .NET Compact Framework.

      With all the investment in COM (COM+ after W2K) and Win32 API, COM interop and PInvoke is here to stay for a while, but I believe if MS would have known this three years ago there wouldn't be any COM+.

    7. Re:subtle answer to troubling question by Anonymous Coward · · Score: 0

      This is not the case - .net doesn;t just wrapper COM. In most cases, COM wrappers existed to the Win32 API, and the .net classes simply wrapper the same API.

      you do not need COM in order to get .NET working. Whilst there may be some features that need it, for the vast majority of the platform, COM is unnecessary.

  8. Yes, I definitively would! by Koyaanisqatsi · · Score: 5, Interesting

    The .Net framework is a very clean and interesting initiative. Forget Passport, forget web-services and all the other pieces and focus only on the framework and the common language runtime (that the focus of MONO) - its neat, and being able to compile code on several platforms without worrying about ports is a great achievement.

    Off course, don't use platform-specific calls (PInvoke) if you want interoperability, but almost everything else is ok.

    1. Re:Yes, I definitively would! by n-baxley · · Score: 2, Insightful

      ...being able to compile code on several platforms without worrying about ports is a great achievement.


      It is! But it happened 7 years ago with the release of Java.

    2. Re:Yes, I definitively would! by TheConfusedOne · · Score: 1

      Wow?!? Really?!? You can compile code on several different platforms?

      Huh, you can already do that with ANSI C and with Java (you may have heard of that one). I'll admit I haven't done much research on .NET, but then I haven't heard anything that really makes this worth my time and efforts when I can already do all my work perfectly well with Java.

      So, what real advantages are there for going with .NET/MONO? (Also, how long would I have to wait before I could start taking advantage of the technology?)

      --
      --- I wish I could hear the soundtrack to my life. That way I'd know when to duck.
    3. Re:Yes, I definitively would! by rickms · · Score: 1

      "Forget Passport, forget web-services and all the other pieces and focus only on the framework and the common language runtime (that the focus of MONO) - its neat, and being able to compile code on several platforms without worrying about ports is a great achievement." WHAT?!!! Yeah thank Sun for it... ever hear of JAVA?! I don't understand why people think .NET is a great achievement, when all it does is copy the idealism of Java. Rick

      --
      Making something out of nothing : MD5 ("") = d41d8cd98f00b204e9800998ecf8427e
    4. Re:Yes, I definitively would! by Anonymous Coward · · Score: 0

      Last time I checked Java/J2EE utilizes one programming language Java. .NET lets you choose from many - primarily C++,C#, and VB.NET. No matter which one you choose they get compiled down to the same Common Language Runtime (CLR). This means that I can program in VB.NET and still have the efficiencies of coding in C++ or C#.

    5. Re:Yes, I definitively would! by Anonymous Coward · · Score: 0

      Yes and how many companies release shelf software in Java ? .NET and C# will be limited to the web space (where it will be trounced by the very apt. EJB and Java) unless it is uber fast for regular applications....

    6. Re:Yes, I definitively would! by pohl · · Score: 1

      And before that with NeXT's OpenStep, which is now MacOSX. It's amazing to me that people will look at .NET and think this is something MS invented.

      --

      The "cue the foo posts in 3, 2, 1..." posts will commence with no subsequent foo posts in 3, 2, 1...

    7. Re:Yes, I definitively would! by Anonymous Coward · · Score: 0

      .NET is a framework, C# is a programming language.
      J2EE is a framework, Java is a programming language .NET has an almost zero learning curve for existing VB, C++, and ASP developers since the framework allows you to use any of several languages. .NET framework is free to implement.

      J2EE has a higher learning curve (not as much for C++ developers). J2EE requires Tomcat (free) or a costly implementation (JRun,Webshere,etc.)

    8. Re:Yes, I definitively would! by Anonymous Coward · · Score: 0

      No one said that Microsoft invented the idea but they sure have come close to perfecting it. Anyway, do you know who invented the first telephone? It sure as hell wasn't Alexander Graham Bell. How about the first car? Nope, not Henry Ford (not even close). Invention is great. Innovation is better.

    9. Re:Yes, I definitively would! by Anonymous Coward · · Score: 0

      You act like the typical C/C++ programmer that's never taken a step outside to see other possibilities exist.

      You want cross platform? There are better solutions than Microsoft's bastardized C++ mixed with Java:

      - Python
      - Ruby
      - Squeak
      - Perl
      - JAVA
      .
      .
      .

      Why do you think .NET is "new" and "exciting"? There isn't a damned thing C-flat does that other languages don't already do, and better.

      Maybe Java has fallen flat in it's promise of write once, run everywhere but Java isn't the only game in town. I program in both Squeak and Python and darned if it doesn't just WORK across platform, almost every time.

    10. Re:Yes, I definitively would! by brsmith4 · · Score: 1

      ANSI C??? Are you out of your mind? Yeah, hello world! and mindless loops work fine when you cross compile. But what about when you want to program in GUI environments? Yeah, I have heard of wxWindows, but that is not ANSI C. What about coding for network protocols? Winsock is similar but almost completely different when it comes to coding than the BSD sockets or Linux sockets. So yeah, if you think in terms of simple, calculate-this-for-me ANSI programs, then you are right. But if you wanna write something USEFUL, no. Also, advantages for .NET: hmmmmm, you can program the same thing in one of 50 gazillion different languages. If Mono comes through, as long as i don't use pInvoke, my Linux mono programs will work exactly the same way, no modification, with network calls and all, on a Windows .Net machine. I see a shitload of possibilities with this. Don't even get me started on the corporate IT ramifications.

    11. Re:Yes, I definitively would! by Anonymous Coward · · Score: 0

      The .NET framework is not about C# alone. It is about using whatever language you want and having it compiled into a Common Language Runtime. Currently C++,VB.NET and C# (and maybe even COBOL believe it or not) are supported directly by Microsoft but there is nothing stopping somebody from implementing the rest.

    12. Re:Yes, I definitively would! by tidge · · Score: 1

      That's just it. It copies what Java does, and does it better. Not to mention that the development tools are cheaper. I'm not talking about any development tools, I'm talking about the ones with all the bells and whistles of Visual Studio.

    13. Re:Yes, I definitively would! by BlueGecko · · Score: 2

      Actually, it happened over twenty years ago with the release of Smalltalk-76. But who's counting? At least the good ideas keep getting another chance in the sunlight before getting politely brushed under the carpet again.

    14. Re:Yes, I definitively would! by Anonymous Coward · · Score: 0

      Of course it's clean. "mono" is Spanish for "monkey" and "net" is French for "clean".

    15. Re:Yes, I definitively would! by pmz · · Score: 1

      Also, advantages for .NET: hmmmmm, you can program the same thing in one of 50 gazillion different languages.

      Yes, when they are really all the same language. The language support in .NET is really just marketing spin.

      my Linux mono programs will work exactly the same way, no modification, with network calls and all, on a Windows .Net machine.

      You may be very enthusiastic, now, but you will become wiser in time. Underlying the different .NET implementations will be all the same platform-dependent crap that never went away. Do you really really think that something that works one way under Linux will really truly work identically under Windows?

      I see a shitload of possibilities with this.

      Yes, "shit" is pretty much accurate.

    16. Re:Yes, I definitively would! by pmz · · Score: 1

      .NET has an almost zero learning curve for existing VB, C++, and ASP developers since the framework allows you to use any of several languages.

      This is untrue. Since when did new application frameworks have a zero learning curve? .NET, once you brush aside the marketing drivel from Microsoft, is no less complex than anything else, including J2EE. Complexity just comes with the territory.

    17. Re:Yes, I definitively would! by Iamthefallen · · Score: 2

      Hello, I would like to write a program in C++, VB and Python to run on win32, MacOS X and *nix platforms, please explain how I can do this under JVM since I know I can (or will be able to) under the CLR.

      --
      Wax-Museum Fire Results In Hundreds Of New Danny DeVito Statues
    18. Re:Yes, I definitively would! by pmz · · Score: 1

      I wish you Microsoft-marketing-drones would stop polluting Slashdot with lies. Not worrying about porting is a pipe dream. "Write once, test everywhere" applies to .NET just as much as anything else.

    19. Re:Yes, I definitively would! by mikec · · Score: 2

      There are no plans to port C++ to CLR. What you get is a lobotomized version: C# with a C++ skin. That's about as useful as a broken arm.

    20. Re:Yes, I definitively would! by Anonymous Coward · · Score: 0

      Have you written an application using the .NET framework? The hardest part of learning a new framework is typically learning a new language. With .NET you can continue to code in C++.

    21. Re:Yes, I definitively would! by Iamthefallen · · Score: 2

      ehr actually, you can use C++ under it, it's just not very much optimized for it (or much more fun than ye old C++)

      --
      Wax-Museum Fire Results In Hundreds Of New Danny DeVito Statues
    22. Re:Yes, I definitively would! by Tablizer · · Score: 2

      (* Actually, it happened over twenty years ago with the release of Smalltalk-76. But who's counting? At least the good ideas keep getting another chance in the sunlight before getting politely brushed under the carpet again. *)

      I don't think Smalltalk was the first cross-flatform interpreted language.

      Maybe the first tied to a GUI, but I think it is dumb to have the GUI API be language-specific anyhow. Hear that Sun?

    23. Re:Yes, I definitively would! by Tony+Hoyle · · Score: 2

      The CLR has no templates... C++ without templates is not truly C++ - no STL so basically you're down to making C with the occasional class.

    24. Re:Yes, I definitively would! by Choron · · Score: 1

      Well if you want to write some VB code in the first place it seems that you won't need a JVM for this kind of job. You can use lots of interesting languages instead (python included) but no lame languages has been ported yet.

      --
      "Naughty, naughty, naughty, you filthy old soomka !"
    25. Re:Yes, I definitively would! by jhunsake · · Score: 1

      No one claims Henry Ford invented the first car. No one.

      He is known for assembly lines.

    26. Re:Yes, I definitively would! by kingkade · · Score: 1

      not true, you can't use some OO features from vb that would otherwise be available through managed c++ or c#

    27. Re:Yes, I definitively would! by Anonymous Coward · · Score: 0

      Go read up on what .NET denotes actually is please.

    28. Re:Yes, I definitively would! by kingkade · · Score: 1
      the differences are:
      • .NET CLR and C# lang spec was approved by ECMA -- Java was not
      • C# uses much more advance JIT (not to mention a fast ms compiler) and many language enhancements (read: if it isn't broken, don't fix it) over Java
    29. Re:Yes, I definitively would! by Anonymous Coward · · Score: 0

      exactly.

    30. Re:Yes, I definitively would! by Anonymous Coward · · Score: 0

      Well, under the bonnet* things are not so clean. ILASM is, unfortunately, a stack based design that is very similar to the JVM, initially intended to support data-level interoperability between C#, VB and Managed C++.

      The type system is highly OO-centric, as are the semantics of ILASM, which means you have to jump through hoops to represent things like closures, algebraic data types and so forth that we will probably see enter the mainstream (in some watered down fashion) ten or fifteen years from now.

      A more general, Hindley-Milner style type system would have supported all the OO stuff you could ask for and leave room for efficient implementations of modern computational structures (i.e. what you will find in Haskell, OCaml, Mercury, but not C#, Java, C++.)

      Don't get me started on the stack-based security model (suffice to say that it inhibits all sorts of common optimizations, most notably inlining.)

      At the risk of sounding slightly snippy, that's what you get when you don't talk to the research labs when you start work on a new design.

      It's a bit like XML: a great idea brought low through being designed by people who (seemingly) didn't know enough.

      * "hood" if you're American.

    31. Re:Yes, I definitively would! by Omega1045 · · Score: 1

      Don't forget web services. This is a cross platform standard (or soon to be) that works quite well. I currently am building an ASP.NET web site that consumes web services from an Apache implementation of SOAP and WSDL. I found this Apache based service in the Microsoft UDDI. It works very well!

      --

      Great ideas often receive violent opposition from mediocre minds. - Albert Einstein

    32. Re:Yes, I definitively would! by SubtleNuance · · Score: 1

      hey
      assmuncher,
      can
      you
      please
      put
      a
      few
      more
      line
      breaks
      in
      your
      sig

      .

    33. Re:Yes, I definitively would! by jpmorgan · · Score: 1

      Yes, when they are really all the same language. The language support in .NET is really just marketing spin. Better not tell the Eiffel# guys that! You may be very enthusiastic, now, but you will become wiser in time. Underlying the different .NET implementations will be all the same platform-dependent crap that never went away. Do you really really think that something that works one way under Linux will really truly work identically under Windows? If WINE is possible, then a clean implementation designed to be portable certainly is.

    34. Re:Yes, I definitively would! by jpmorgan · · Score: 1

      The CLR doesn't support templates, but C++.NET does - they're just exactly like normal C++ templates, completely static and implemented at compile time.

      What the CLR doesn't support are more advanced runtime generics semantics (although this can be emulated somewhat, just not as efficiently). That's slated for a future version.

    35. Re:Yes, I definitively would! by liloldme · · Score: 1
      and being able to compile code on several platforms without worrying about ports is a great achievement.

      Eh? Java did this seven or eight years ago. If anything, Mono shows the lack of vision on the part of Miguel and others.

    36. Re:Yes, I definitively would! by liloldme · · Score: 1
      # C# uses much more advance JIT

      Please inform us what great advancements Microsoft has made compared to Java jitters (such as HotSpot).

      I would really really like to know.

      Or are you just full of shit?

    37. Re:Yes, I definitively would! by liloldme · · Score: 1
      VB.NET and still have the efficiencies of coding in C++ or C#.

      Efficiencies?? What the fuck are you talking about? They all run on top of the same virtual machine.

    38. Re:Yes, I definitively would! by liloldme · · Score: 1
      J2EE requires Tomcat (free) or a costly implementation (JRun,Webshere,etc.)

      Uhh, Tomcat is hardly a full blown J2EE platform. Try JBoss instead.

      It's amazing the amount of ignorance of most .NET zealots here. You don't know a fucking thing about the alternatives that have been offered to you, free of charge, for years.

      Though fine by me, go burn your money on the next dead end solution (.NET) that is nothing but glorified Visual Basic.

    39. Re:Yes, I definitively would! by liloldme · · Score: 1

      First of all, C++ does not work, you have to use Managed C++ which is not the same language. If someone wants to keep on using VB, they don't need a .NET platform. C# is a failed attempt at copying the rather elegant design of Java. And last, JVM supports more languages already than .NET ever will.

    40. Re:Yes, I definitively would! by QuaintRcky · · Score: 2, Informative

      C++ - write it and hook it in via JNI
      VB - You wanna code in VB?!?!?!?!
      Python - run Jython (python 2.0 language on the Java VM)
      Also, check out Languages that run on the Java VM for a surprising number of languages (including basic) that already run on top of the Java VM, on any platform that supports java, hell - even the GUI works properly :-).

    41. Re:Yes, I definitively would! by TheConfusedOne · · Score: 1

      The point with the languages is that you have to change the other language to fit the syntax that the CLR expects. Look at all the changes they've had to do to VB to make it a language that runs under CLR.

      As far as the work identically part. Microsoft has already asserted that they plan on .NET to "run best" on Windows. That means that the really useful features won't be ported. Microsoft has no vested interest in cross-platform compatibility, in fact, it's against their business model.

      --
      --- I wish I could hear the soundtrack to my life. That way I'd know when to duck.
    42. Re:Yes, I definitively would! by TheConfusedOne · · Score: 1

      ANSI C was an illustrative point. The fact is that cross-platform compilation has been around for a long while. Granted, the usefulness has been steadily improving.

      The issue remains, what is the new and useful thing that .NET is bringing to the table?

      The multi-language thing is a red herring. The average software project is tough enough to control now as it is, the last thing you need is every developer writing in his/her language of choice. (Certainly will not simplify the process of consolidating duplicate functions.)

      --
      --- I wish I could hear the soundtrack to my life. That way I'd know when to duck.
    43. Re:Yes, I definitively would! by brsmith4 · · Score: 1

      I would tend to agree with you on the point of every developer writing in his/her language of choice. It makes working as a team even more of a bitch than it already is. As for what it actually brings to the table... hmmmm. we will just have to wait and see. My company is using it right now and so far, I have seen nothing that cannot be accomplished with java, php, mysql, or other existing technologies.

    44. Re:Yes, I definitively would! by HiThere · · Score: 2

      Better not tell the Eiffel# guys that!

      But you notice it's Eiffel#, not Eiffel. They are re-writing the language to fit into .net , and I don't yet find the result to be interesting.

      I'm not sure just how much of what was Eiffel will be saved by the time the re-write is finished. And once I heard that they were taking out multiple-inheritance, I haven't wanted to look at the rest of the butchery. Multiple-inheritance may be bad in C++, but in Eiffel it's one of the strong points of the language. To have gotten Bernard himself to make the changes doesn't make it any better. I suppose that they could find a strength to add to make up for the change, but the new language sure wouldn't be Eiffel.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    45. Re:Yes, I definitively would! by HiThere · · Score: 2

      On windows this might be a reasonable choice. Under some circumstances. However, claiming that "it does what Java does", without saying what it is you are talking about, doesn't communicate much. Do you mean crossplatform graphics? I feel that remains to be demonstrated. But since I don't know what you mean, it's really pointless speculation.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    46. Re:Yes, I definitively would! by HiThere · · Score: 2

      applies to .NET just as much as anything else.

      Perhaps that should be "will apply to .Net...". It's probably too soon for the present tense.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    47. Re:Yes, I definitively would! by kingkade · · Score: 1

      Though you've got a rather nasty attitude to a person expressing a simple opinion, here are some benchmarks of .NET vs J2EE architecture here
      and an interesting IO benchmark here
      this computation benchmark is interesting (java w/ hotspot jitter
      here is a simplified benchmark with integer and fp operations
      Also, to my understanding, the .NET IL is not stack based as is the JVM which Sun had said is not designed for speed but for simple architectures in embeded designs.
      One of the advantages over Java is that C# allows inline allocation (as opposed to heap allocation) for simple structs or primitives.
      Try not to use foul language, it just makes you look reactionary and foolish.
      Then again all these benchmarks could be fabricated but since i have had experience with C# development and Java (w/ AWT and swing) 1.3, I noticed the speed difference right away...

    48. Re:Yes, I definitively would! by liloldme · · Score: 1
      Ok, so let me get this straight...

      You do not then have, say, a white paper which explains a new approach or strategies to optimize byte codes at runtime that Microsoft is taking advantage of in their JIT implementation. All you have to show for are bunch of micro benchmarks, which tells us nothing about how the jit compiler themselves work.

      Do you realize how stupid that makes you look? The links you post are pretty telling themselves -- you obviously have very little understanding of the whole issue (the fact that you throw in a benchmark comparing web applications implemented in NET and J2EE and claim that is an indication of the advancement Microsoft has made in their JIT compiler itself is laughable -- here's a hint: the database access itself is so time consuming that it hides any differences in JIT speed of the application code).

      I therefore conclude that you are, indeed, full of shit, and Microsoft is using the same approach to optimizing bytecodes as is SUN and IBM and pretty much every one else out there. I also suggest that you stop believing everything Microsoft marketing is telling you.

      Have a nice day.

    49. Re:Yes, I definitively would! by kingkade · · Score: 1

      Hi again,
      Once again, those links were benchmarks in various areas where java is competing with .NET in general (as per my original post) so i posted a link on traffic load handling and scalability with comparisons to J2EE, an IO benchmark, and a computational benchmark (for calculating digits of pi) WITH THE HOTSPOT JIT vs THE C# JIT...did you even read these "micro benchmarks"? I almost fell on the floor laughing when I read you wrote that but didn't even acknowledge their results.
      When something doesn't say what you want it to, you just dismiss it. I guess you'll dismiss me as working for MS next :D.
      You're more predicatable than sunrise.
      So therefore giving extra info that strengthened my other points does not make me look stupid as you so eloquently put it.
      IMPORTANT: Like i said, the design of the bytecode (which is open) is designed for client, web service applications as opposed to the embeded architecture as is the jvm bytecode AFAIK. Also, like i said already, the CLR/language features make it easier to compile from IL to native such as inline stack allocation types (see boxing types) where as everything in java in a reference type, operator overloading (operators for that matter), delegates, and property members to name a few.
      Also, again remember that is rubbed your nose in these facts already and told you why the CLR lends itself to better JIT compiling than Java does. Again, JVM bytecode is stack-based.
      I've programmed for straight JVM as well as Java, JSP, servlets, JavaBeans, JSP tags, ASP (& ADO), C#, and many of these technologies and am pretty indiscriminant although you seem to want to turn in into an "us versus them" *argument*.
      Funny how you acuse (and continue to do it) ppl of being full of sh!t (hint: not a valid argument -- ad nauseum). It's ok, I know you're feeling manly behind your anonymity, like many jerks on /. So, in light of this, i do not declare you full of shit, but just an ignorant person who refuses to make a point or carry on an intelligent conversation w/o resorting to soap opera-like drama, name-calling, whining, and complaining about lack of references without presenting any of their own.
      Also, about a white paper, i actually had a friend show me the .NET technical paper awhile ago, and will post in if I can find it (hopefully).

    50. Re:Yes, I definitively would! by kingkade · · Score: 1

      here is one paper but not the original one i had, interesting comparison. BTW, to clarify: .NET CLR is also stack-based but a bit different in that it seems to have been entirely design for JIT compiling at the expense of interpretation. Also, designed for multiple lang suppor, which is a cool feature.
      Unfortunately Java could have been revised faster but Sun sat on it's hands for too long and unfortunately MS came along and made it better. Hopefully since it is open MS won't be able to "break compatibility" too much and projects the dotgnum and Mono will be useable so that i can run programs on either Linux or Windows transparetly. That would be the ultimate goal...

    51. Re:Yes, I definitively would! by liloldme · · Score: 1
      Once again, those links were benchmarks in various areas where java is competing with .NET in general (as per my original post) so i posted a link on traffic load handling and scalability with comparisons to J2EE, an IO benchmark, and a computational benchmark (for calculating digits of pi) WITH THE HOTSPOT JIT vs THE C# JIT...did you even read these "micro benchmarks"?

      Look, I can just as easily point you to benchmarks that show Java VMs outperforming a NET runtime, or even compiled C apps. The bottom line that I'm trying to get through your thick skull is that these micro benchmarks are meaningless.

      Now you on the other hand claimed MS has made some advancements in how bytecodes are optimized at runtime. When I have asked you to explain what these new technical innovations are, you have posted nothing but irrelevant garble.

      I almost fell on the floor laughing when I read you wrote that but didn't even acknowledge their results.

      Laugh all you want, it is quite clear that you lack the technical understanding to answer my question what new advancements Microsoft has made in the virtual machine technology.

      designed for client, web service applications

      First of all, no, the CLR bytecodes were not designed specifically for client applications. Second of all, web services operate on the server, which would therefore contradict this claim as well. Again, the only thing you are demonstrating here is your lack of understanding.

      I've programmed for straight JVM as well as Java, JSP, servlets, JavaBeans, JSP tags, ASP (& ADO), C#

      Look, what languages or components you have programmed is completely irrelevant in the discussion of how the runtime compilers work. I want to know what MS runtime compiler does so different from anyone else that warrants your claim that their compiler is somehow more "advanced" than anyone else in the industry. And you're obviously completely unable to answer this question.

      The rest of your rant made so very little sense to me that I will not bother trying to dissect it. I do suggest that you try to learn to articulate a bit clearer.

      i actually had a friend show me the .NET technical paper awhile ago, and will post in if I can find it

      Let's hope your friend is a bit more knowledgeable than you are.

    52. Re:Yes, I definitively would! by el_chicano · · Score: 2
      Funny how you acuse (and continue to do it) ppl of being full of sh!t (hint: not a valid argument -- ad nauseum).
      I think you meant to say ad hominem , not ad nauseam . When you make simple mistakes like that it makes it hard to believe you really know what you are talking about.

      Your rampant misspellings also detract from your message, as they make you sound like a 13-year-old script kiddie rather than a serious programmer. If you don't want to learn how to spell English properly, at least add a spellchecker to the list of software you know how to use...
      --
      A man who wants nothing is invincible
    53. Re:Yes, I definitively would! by kingkade · · Score: 1

      So what you're saying is you've never misspelled anything or inadvertently mangled grammer.
      Also, "script-kiddie"?? Wow, amazing how fools widen the scope of its meaning -- so out of context.
      I wonder if you see the ridiculous irony that you point out the "argumentum ad hominem" logical fallacy and then post these comments.
      Contribute something to the argument (or what's left of it) or just don't post. I can already tell that you have nothing to contribute, but will let you get the last word if it lets you sleep.

    54. Re:Yes, I definitively would! by kingkade · · Score: 1

      RTF paper. Reading is an important gift, use it.
      Oh yeah, "designed for client [and!] web service applications". It was a misspelling, but you already covered that in your other response.
      My rant made little sense, hmmmmm. Pot. Kettle. Black.
      For the last time, I said the "technical innovation" i am trying to pound through *your* thick head is that one of its design goals were to favor JIT compiling at the expense of interpretation. OK? It is also developed for a target for mulitple languages (yes, I know Java has many languages that compile to JVM).
      Now, to me, this would explain why those benchmarks (ohh, sorry microbenchmarks -- you mean the ones by IBM too??) always show C# jitted code to have a nice edge on Java's jitted code.
      I could not read the whole paper (obviously) and know every complex technical design issue that went into making the CLI so adaptable to being "jitted" at the expense of bad for interpretation (one reson is "virtual" functions for adding stack operands, unaware of type which is part of the data itself).
      You mention you can offer benchmarks that support you, why haven't you posted them? Hmmm? At least you would have put forth something that just your witty responses (*pause* ad hominem) you would have at least had respect instead of calling someone "full of shit". BTW, I checked most of your other responses that you have posted toward people that are equally rude and provide no other purpose other than to chastise someone. That "other" persons post should have been directed at you...

  9. Re:blah by Anonymous Coward · · Score: 0

    you're a fucking idiot. you think anything that comes out of microsoft is bad just because it's microsoft. have you ever actually used .net???? it is excellent. and what's wrong with making money??

  10. bad news for Linux? by tps12 · · Score: 2, Insightful

    Hey, this sounded pretty cool at first. I mean, the more languages the better, right? ;) Plus, I hate it when the Winblowz lusers get to play with pretty toys I can't get on my Linux boxen.

    But then I reconsidered. First, a little background. C# was, is, and always will be, a Micro$oft invention. Like it did with SMB and OLE, not to mention DirectX and ZIP, M$ will have no reservations about mucking with C# just to break Mono compatibility.

    In the case of SMB, we live with this. SMB has become a de facto standard in the enterprise, so Samba is forced to follow M$'s lead and keep up. But no such market forces exist for C#. Right now, it's a minority player against giants like Java and C++.

    By supporting C# through Mono, Linux only serves to make it more popular. In doing so, it makes M$ more powerful. The Mono project is about as counterproductive toward Linux advancement as a Free Software project can be. :(

    --

    Karma: Good (despite my invention of the Karma: sig)
    1. Re:bad news for Linux? by Anonymous Coward · · Score: 0

      Beautiful troll. "giants like Java", MS mucking with ZIP - I almost bit it myself.

    2. Re:bad news for Linux? by Anonymous Coward · · Score: 0

      The Mono project is about as counterproductive toward Linux advancement as a Free Software project can be. :(

      After I read that statement, I fell out of my chair laughing hysterically.

    3. Re:bad news for Linux? by Quarters · · Score: 2

      I think Phil Katz (if he were still living) and the employees of PKWare would have something to say about you attributing the creation of the .zip compressed data file format to MS.

    4. Re:bad news for Linux? by Carnage4Life · · Score: 2, Informative

      But then I reconsidered. First, a little background. C# was, is, and always will be, a Micro$oft invention. Like it did with SMB and OLE, not to mention DirectX and ZIP, M$ will have no reservations about mucking with C# just to break Mono compatibility.

      C# is an ECMA standard, like C++ which is an ISO standard unlike Java which is Sun Microsystem's property. Thus Sun has complete control over the future of Java while Microsoft does not have the same for C#. So claiming supporting C# is supporting Microsoft is way off base. Question: Were DirectX, OLE and SMB also international standards or are they technologies wholly owned by M$?

    5. Re:bad news for Linux? by miguel · · Score: 5, Informative

      Developers in the Windows world that do not care about cross platform issues (which is, 99% of them) are tired of C++, and Visual Basic, and C# happens to be a nice language to move to delivered by the company that does their OS.

      So people will be adopting C# as a programming language no matter what anyone does. The language is here, and the tools are here, and the community is rapidly growing.

      So what we are enabling is to bring a number of things to Linux: we bring the people, the knowledge and we are reusing Microsoft's investment in documenting, promoting and producing training materials to benefit us.

      So, I am fairly possitive that this is good.

      And then, there is the added advantage of open source: now you got a compiler, a runtime and classes. If they serve your purposes, take it, improve it, extend it, change it, modify it, rip it, research, reuse what you feel like reusing.

      Miguel

    6. Re:bad news for Linux? by k2enemy · · Score: 1

      the c# specification has been standardized so i wouldn't worry too much. i suppose ms could stray from the spec, but i really don't see it happening.

    7. Re:bad news for Linux? by IIRCAFAIKIANAL · · Score: 2, Insightful

      "First, a little background. C# was, is, and always will be, a Micro$oft invention."

      C# is supposed to be an open, standardized language (standardized via the ECMA) - see here - in contrast, directx and the rest were all closed, proprietary systems. M$ would lose a lot more than they would gain by mucking with the standard.

      They, however, may unofficially extend it... that's a lot more likely, if you think they are planning evil.

      --
      Robots are everywhere, and they eat old people's medicine for fuel.
    8. Re:bad news for Linux? by Anonymous Coward · · Score: 0

      And because you are "fairly possitive that this is good," (positive, by the way) you'll plow ahead without really listening to the arguments of all those around you? People will adopt the C# language if it catches on, and making it available on other platforms would help it catch on. Then once it's popular enough for Microsoft to take the reigns, they'll play around with it however they like -- they're already doing it with SMB, remember? You're offering no more than, say, GCC already offers, except you're throwing in the additional bonus of contributing to the success of a company whose business model is based upon crushing ALL competition. How can you possibly think that is positive, unless some other factor you haven't mentioned proves this to be a worthwhile pursuit?

    9. Re:bad news for Linux? by Anonymous Coward · · Score: 0
      i really don't see it happening

      Blind, huh?

    10. Re:bad news for Linux? by Anonymous Coward · · Score: 0

      Neither is M$, or Winblowz.

    11. Re:bad news for Linux? by oPless · · Score: 2
      LOOK, I'm utterly sick of newbies thinking "M$ wrote SMB" I shall say this:

      HEY DID NOT.
      SMB = NetBIOS Over TCPIP

      RFC 1001 / 1002


      A Portion of RFC 1001 is below:

      OVERVIEW OF NetBIOS

      ... NetBIOS was designed for use by groups of PCs, sharing a broadcast medium. Both connection (Session) and connectionless (Datagram) services are provided, and broadcast and multicast are supported. Participants are identified by name. Assignment of names is distributed and highly dynamic...


      NetBIOS applications employ NetBIOS mechanisms to locate resources, establish connections, send and receive data with an application peer, and terminate connections. For purposes of discussion, these mechanisms will collectively be called the NetBIOS Service.
      This service can be implemented in many different ways. One of the first implementations was for personal computers running the PC-DOS and MS-DOS operating systems. It is possible to implement NetBIOS within other operating systems, or as processes which are, themselves, simply application programs as far as the host operating system is concerned.

      The NetBIOS specification, published by IBM as "Technical Reference PC Network"[2] defines the interface and services available to the NetBIOS user. The protocols outlined by that document pertain only to the IBM PC Network and are not generally applicable to other networks.


      [2] IBM Corp., "IBM PC Network Technical Reference Manual", No. 6322916, First Edition, September 1984


      In fact dont take my word for it, check out The History Of SMB or Here oh, and Here


      Now my little SMB rant is over, I shall rip apart the rest of your comment.

      1. C# is a unashamed ripoff of Suns Java Language, submitted to ECMA for standardisation. As has their CLR (or Virtual machine)

      What they may do however is add more windows specific extensions (Like they did with Java, which Sun got upset about) in libraries. I doubt that they will make significant changes to the virtual machine nor the core api. They'll just bolt on more and more crap (just like Sun are doing with Java)


      2. OLE - wrong, this is another IBM invention
      Dynamic Data Exchange [DDE], Object Linking and Embedding [OLE] (now known as ActiveX), and Component Object Model [COM] are all derived from IBM technology - If in doubt look Here

      3. Direct X - a half baked api to get closer to the hardware than a protected mode O/S normally allowed, in fact they had to move for the most part the display drivers into RING0 to accomplish this. NT 3.x had lots of issues with graphical update speed.

      4. ZIP - I'm sure PKWare Inc. would like to know how M$ has hijacked ZIP file compression...

      5. Back to SMB - a "de facto" standard is:
      A format, language, or protocol that has become a standard not because it has been approved by a standards organization but because it is widely used and recognized by the industry as being standard.

      It IS a standard! Masquerading as CIFS/NetBIOS over TCP/IP etc. It's as much as a standard as POP3 and SNMP.

      Samba is forced^H^H^H^H^H^Hchooses to adapt to Redmonds bugs/incompatabilities, due to the plain fact that the userbase of windows clients is so mingboggingly huge.

      6. Supporting C# (I think you mean CLR here) under a liberal license, is a good thing. It doesn't make M$ more powerful, any more than jumping up and down makes an effect on earths orbit. CLR is here, and on 90% of windows updated machines right now. Many people would have Loved VB to be available on *nix. Now with M$ making all its languages (If I understand it right) run under CLR their wishes come true.



      I Really hate saying this, but I think CLR will actually become what Java promised back in 95 total cross platform compatability.


      The CLR Genie is out of the bottle. There is little now Redmond can do to do otherwise. Mono is basically removing a whole bunch of porting work off M$ and putting it back into the hands of the developers (where it should be, fs) - Do you really think we would be in a messed up situation with Java now, if SUN had opensourced the JVM from the word go? No, I didn't think so.

      So please, before you post check your facts, and stop presenting (IMO) poorly formed opinions. And who ever modded this troll to +4 needs taken outside with petrol+matches!


    12. Re:bad news for Linux? by Yarn · · Score: 2

      Dear oPless.

      "You've been trolled"

      However, it's brought some interesting links to light.

      --
      -Yarn - Rio Karma: Excellent
    13. Re:bad news for Linux? by Anonymous Coward · · Score: 0

      a troll with a good point

    14. Re:bad news for Linux? by Xerithane · · Score: 2

      ...you'll plow ahead without really listening to the arguments of all those around you?

      Sorry, but it's his company first off, and he does listen to the arguments of those around him. So freaking what? No one is forcing you to use .NET or Mono. What harm does it cause to the linux community to add another language that increases interoperability with other operating systems, even if it is one that most the zealot nuts don't like.

      People will adopt the C# language if it catches on, and making it available on other platforms would help it catch on. Then once it's popular enough for Microsoft to take the reigns, they'll play around with it however they like.

      You mean just like Sun tried to do? It will be much less effective for Microsoft to try to do that because of clean room implementation. The Mono C# compiler uses the specs of the language. If Microsoft wants to break interoperability they still can, beyond that you don't have to worry about them having the power to enforce licensing for people using the syntax of the language.

      You're offering no more than, say, GCC already offers, except you're throwing in the additional bonus of contributing to the success of a company whose business model is based upon crushing ALL competition.

      Sorry - I didn't realize that GCC provided .NET capable development with C# -- could you provide a link? Sometimes in helping fortify yourself, you help fortify your enemy. I would like to remind you that the Microsoft development community is not the enemy, the company, maybe is. Working with the Microsoft developing community is a step forward in getting a unified platform architecture -- maybe that's what he wants? I know I'd like to be able to have my software run the same way on OS X, Win, and all flavors of Unix.

      How can you possibly think that is positive, unless some other factor you haven't mentioned proves this to be a worthwhile pursuit?

      Simple -- how can you possibly think that it isn't positive. Everyone is entitled to their opinions. I stand nothing to gain, and I think it's a great idea and will probably start developing for it. Miguel has been very open, including his Slashdot interview, what more do you think you are entitled to? You aren't even entitled to that, he did it to help support the community that supports him. I applaud his efforts, and his ability to look past the evil face of Microsoft to see that there is in fact a good thing.

      As for SMB, I can still smbmount all my boxes so I'm not losing sleep about that, either.

      You need to relax, either come up with an alternative to .NET or shut the hell up because it frankly, is none of your business what he does with his time.

      --
      Dacels Jewelers can't be trusted.
    15. Re:bad news for Linux? by oPless · · Score: 1

      Thanks for that. :-)

    16. Re:bad news for Linux? by Steveftoth · · Score: 2


      I Really hate saying this, but I think CLR will actually become what Java promised back in 95 total cross platform compatability.

      I would agree, but you said it yourself, that MS is adding all these libs to the system that programmers will use. If you actually want to be able to run your program cross-platform, then you'll need to have different code paths that use different libs under different platforms. Java only works cross platform because they have created a platform that is so generic that is can be supported on almost any modern computer. C# and it's libs don't try to do this at all. They depend on MS specific functions to run, just another layer between you and the real C apis. Good because it makes the programmers job easier, bad because it really is MS specific. Java did promise cross platform compatability, and it is really close to being the same over all platforms (a few bugs withstanding). Unfortunatly, the only cross platform part of java is the JVM and if you can't do something in the JVM, suddendly you lose the cross platform part of java.

    17. Re:bad news for Linux? by zapp · · Score: 1

      There are several problems with your arguments...

      Microsoft doesn't change code constantly to defer competators from being compatible, ever think maybe they are one of the few who are truely innovating?

      Also .NET is, as other people have said, a standardized platform. While it is true Microsoft has only been pushing for development in its languages for its platforms (ASP,VB,C# mostly), it can be easilly extended to Perl, Python, PHP, Java...

      Yes, Microsoft does have problems playing well with others, but if they're the only ones pushing new technologies through, they're going to be in the lead. Until open source stops trying to "keep up" and starts coming up with ideas that will *LEAD* the industry... it'll be 2nd best.

      --
      no comment
    18. Re:bad news for Linux? by oPless · · Score: 2

      firstly I want to apologise for that missing tag :-)

      I agree totally with your comments, but Java has been screwed over totally with swing, and god knows what else Sun dreams up to bolt on it.

      The whole point is that the software community has now a virtual machine that is completely independant of Suns tinkering.

      For example windows.forms will be a boon for those like me hate swing - yes I prefer awt, sure it was awkward to fiddle with, but swing was not the answer to it!

      Java is a fine language and yes, I am a java advocate. Until recently I was in charge of integrating native written APIs into a sensor framework, for an enterprise-level security application - I know all about the benifits of cross-platform compatability.

      But! Many real world apps will need to bash native APIs. Mostly this will diminish the advantages that cross platform provides. A rich(er) set of APIs reduce that need. Java keeps getting bloated with APIs that are really badly planned and can break backwards compatability (serialisation appears to change/break per release of the VM)

      I for one look forward to writing in the java language with a truely portable and free VM that I have the option of writing modules in other languages. (Right tool for the right job, etc)

    19. Re:bad news for Linux? by NotoriousQ · · Score: 2

      Good...just the person I wanted to say something to....

      One request for the whole strategy for mono:
      please, please, please make sure mono goes for some standards...do not just mirror .NET....but fix it where you think it should be fixed, and always keep in mind cross platform...it seems that MS already forgot that to some extent. I think that once mono has some people using it....having a more stable crossplatform system will be something that will keep MS in check, when they will try to change serious things on a whim.

      Oh and if you have a couple mins, take a glance at
      my other post on this story as it has a couple more frustrations in .NET that mono libs can fix.

      Thanks

      --
      badness 10000
    20. Re:bad news for Linux? by pkphilip · · Score: 1
      I don't think companies make their plans based on what is purportedly tiring them.

      There are a few things NOT going for .NET

      1. The cross platform hype is a farce for most REAL apps.
      If you look at the facts of the case - .NET is pretty much just an API which exists over the Win32 API - but the .NET standard is a small subset of the Win32 API.. and it covers just over 150 (or roundabouts) classes. The Win32 API is far richer than the .NET API. Ofcourse one could argue that PInvoke can be used to call external apps - but that is a kludge not a solution.

      Most non-trivial apps will require access to the classes not covered under the .NET standard. But if those classes are used, the application ceases to be "cross-platform" compatible.

      Currently, the Java API standard covers a lot more ground than the .NET standard... and also, a lot of work has already been carried out to make sure that Java works about the same on most platforms.

      2. Limited API - non availability of native specialized libraries
      Even the 1500+ classes which form part of .NET don't necessarily suffice for most complex apps. Most apps will require access to specialized libraries - for instance compression libs, image handling libs, encryption libs etc...

      For example, A sophisticated image viewer application like ACDSEE might need to interact with specialized external libraries for processing different image formats and so on.

      The companies creating these specialized libraries (in languages such C++, Delphi, VB etc) have been developing and polishing up these libraries for years. It is very unlikely that these same companies can deliver libraries for .NET, which will retain the maturity of their current offerings in "legacy" languages like C++, Delphi etc.

      Also, most of these companies have already made massive investments in porting their libraries to Java.

      3. Developer availability and technology comfort.
      There is nothing or very little that .NET offers that Java doesn't already offer. From standard apps, to web based apps and services, Java handles them all just as well as .NET does. Java's cross platform features and its rich API are already fairly well know. A lot of programmers are already fairly familiar with Java. To get these programmers to use .NET, they will need to be retrained and there really doesn't seem to be any benefit in that.

      So in all, IMHO .NET isn't really a viable option for most businesses.
    21. Re:bad news for Linux? by Anonymous Coward · · Score: 0

      de facto standard in the enterprise .. cute.

    22. Re:bad news for Linux? by Anonymous Coward · · Score: 0

      Are you suggesting we (Linux users) have the ability to embrace and extend C#?

      More to the point, don't you think we _should_?

    23. Re:bad news for Linux? by croanon · · Score: 0

      There are many people who do refuse to shift to C# as a programming language. Only Windows people are being forced to. 90 percent of Java developers will not.
      Even the language is here, the tools will be there maybe next year (for Linux), I won't touch a single line of Mono code. Because, there is no need to while there is Java. I know hundreds of Java programmers in Prague, none is interested in C#, and Mono.
      Why should I be interested? I am happy with Java. I write a Java program, it works on Linux, Unix, Mac, Windows, Free BSD, etc, etc.
      Mono will help to M$ more than it will help to Linux. Now M$ will be able to say, "do you see? .NET is cross-platform".
      If you ask my real idea, I believe, Mono project is nothing more than product of Ximian's and especially YOUR desire to be famous, etc, since they were always clouded by KDE.
      So, take your MONOpolist project and stick it in your ARSE. I will never use it. :)
      Cheers Miguel.

      --
      Dear Bill, do you have a .net tatoo on your ass for marketing?
    24. Re:bad news for Linux? by sql*kitten · · Score: 2

      First, a little background. C# was, is, and always will be, a Micro$oft invention. Like it did with SMB and OLE, not to mention DirectX and ZIP, M$ will have no reservations about mucking with C# just to break Mono compatibility.

      More FUD. In fact, C# and the CLI are ECMA standards. Unlike, say, Java, which is controlled by a single vendor.

    25. Re:bad news for Linux? by liloldme · · Score: 1
      Unlike, say, Java, which is controlled by a single vendor

      No it's not. See JCP.

      You can stuff your FUD up your ass.

    26. Re:bad news for Linux? by Anonymous Coward · · Score: 0

      Rather ironic that you would note that "everyone is entitled to their opinions," then promptly order another user to "shut the hell up" in the same reply. Typical double-standards, wouldn't expect anything less from a troll like yourself.

  11. MOD TO FLAMEBAIT by Anonymous Coward · · Score: 0

    so just let them do what they want cause it's inevitable? wow, what a loser attitude. bet you'll never get laid

  12. Useful technology by Jonner · · Score: 4, Interesting

    I am not interested in .NET because of M$'s clout, but I am somewhat interested in CLR and the standard libraries because it may be a genuinely useful technology. I'm not interested much in C#, as it appears to be quite similar to Java with some C++-like stuff, but if the promise of easy cross-language development is true, that is interesting. Of course, that is possible with a JVM and standard Java libraries, but the CLR may be superior in that respect. Let's wait and see.

    1. Re:Useful technology by alext · · Score: 2

      How can it be superior if it doesn't have standard libraries? There are no standard GUI, database etc. libraries - you're thinking of Java (the platform).

  13. Dumb question.... by Anonymous Coward · · Score: 0

    I thought I read some time ago that Microsoft put some sort of clause in the EULA for .NET or its VS.NET that said that software using certain licenses (GPL) can't be written in .NET. Is Mono GPL or similarly licensed? If so, doesn't writing the Mono C# compiler in C# make it illegal?

    Is that not the case? Just curious.

  14. zerg by Lord+Omlette · · Score: 2
    Gtk# doesn't currently work on Windows as the Microsoft runtime is incompatible with Gtk+ libraries that aren't linked with MSVC's lib.exe tool. Tor Lillqvist's Gtk+ for Windows won't work. While there's no active effort within the Mono project to recompile the DLLs, you're welcome to try yourself. build- dll is an example of how this has been achieved in the past.

    Another consideration is porting SoundStream to Win32. This should be trivial for anyone familiar with Windows sound programming.
    Absolutely brilliant! What's stopping people from implementing WinForms on Mono instead of being forced to use this shit?
    Windows Forms is probably going to be the trickiest one because we might have to do some emulation of the Win32 layer.
    ARGHROWARSD;FLKJSDF!!

    My favorite part of .NET and my main reason for using it is the one that's gonna take the longest to find on other platforms? GODDAMMIT
    --
    [o]_O
  15. How could you want any more? by DigitalCH · · Score: 1

    Every language on every platform... (eventually I know). But still it is a grander vision than java offers.

    1. Re:How could you want any more? by SuperKendall · · Score: 1

      Any language you like - as long as the language features are a subset of C# (no need to worry about the rest, they'll just toss 'em out and the thought police will make sure you forget they ever existed).

      What a wonderful world!

      --
      "There is more worth loving than we have strength to love." - Brian Jay Stanley
  16. Don't feed the trolls by Anonymous Coward · · Score: 0, Insightful

    Maybe if a valid reason was given for "switching to KDE" aside from Gnome being able (able, not forced) to use Mono this wouldn't be a troll.

    But it is.

  17. proven way to tell by Anonymous Coward · · Score: 0

    You can't say there aren't any explanations for this. The coordination of events is just too uncanny for my test.

    I mean, really, is the elevation of the trip meter really at stake when I've got less than 24 hours to beautify my pancake??!

    Yeah, you know I gotcha babe. Just 10 pounds more, and the scales tip in my favor. No more Saturday night bingo for me. It's phosphate glands from now on.

  18. What about Dot-GNU? by Koyaanisqatsi · · Score: 3, Interesting


    On a side note, I would like to see Ximian or the GNU Foundation talking at how MONO and DOT-GNU differ on purpose or how they are similar.

    Frankly, they seem to have the same end goal, and I'm afraid this is a duplicate effort that would be better off if they joined forces.

    Dot-GNU: http://www.gnu.org/projects/dotgnu/index.html

    1. Re:What about Dot-GNU? by BoVLB · · Score: 1
      I would like to [know] how MONO and DOT-GNU differ

      A good question. I seem to recall reading a comment in the DotGNU FAQ that Mono wasn't as "clean-room" and might therefore be more easily killed by Microsoft under some legal theory of intellectual property rights. Unfortunately, that was several weeks ago, and I can no longer find any such reference.

    2. Re:What about Dot-GNU? by krammit · · Score: 1

      I'm not sure they have the same goal in mind. Mono's main goal is to create an open implentation of .NET. What DotGNU set out to do is create an alternative implementation of the basic framework. Mono is recreating all the MS C# libraries so that programs compilied with .NET will run without recompilation under Mono. DotGNU is creating it's own core class libraries that focus more on security and privacy. Their approach is completely independent of whatever MS does with .NET in the future. As far as I can tell, all they have in common is that they are both implementing the ECMA stuff, which is NOT .NET.

      --
      "Watch your cornhole, bud."
    3. Re:What about Dot-GNU? by DevilM · · Score: 2, Informative

      I co-authored an article that compares all the open source implementations of the .NET CLI. You can find it here.

    4. Re:What about Dot-GNU? by miguel · · Score: 5, Informative

      DotGNU is = Portable.NET + other_stuff.

      Portable.NET and Mono are doing the same things. Mono is a lot more advanced than Portable.NET: JIT, a working compiler, large development team.

      About the `other_stuff', I have never been able to figure out what it is, or what they are doing.

      It is a duplicated effort as you very well point out. From the Ximian perspective, we did have the resources to work on this project, and we had our developers work on it.

    5. Re:What about Dot-GNU? by jpmorgan · · Score: 1

      Unfortunately, this is the DotGNU team spreading their FUD again - they hate Mono and have been trying to kill it for ages.

      The truth of the matter is the situation is reversed. Mono was written from published specifications, whereas DotGNU's Portable.NET was written after reverse engieneering parts of Microsoft's .NET Framework.

      Who's on the shakey foundation now? The DotGNU people are just asses. Miguel de Icaza has done more good for Free Software than they ever will.

  19. Really? by Codex+The+Sloth · · Score: 3, Insightful

    Microsoft has proven again and again that, in the end, they *will* win

    Really? They *always* win?

    Bob
    MSN
    IIS
    MSN
    ASP Microsoft Office
    Hailstorm
    etc, etc

    Yeah... it's hopeless...

    --
    I am not a number! I am a man! And don't you ... oh wait, I'm #93427. Ha ha! In your face #93428!
    1. Re:Really? by FooBarWidget · · Score: 1

      > MSN

      MSN won. It's more popular than ICQ now, dispite that ICQ 2001+ has become much better and faster. Almost ever teenager uses Hotmail.

    2. Re:Really? by Anonymous Coward · · Score: 0

      What were you trying to prove by that post? Microsoft Office is the number one Office Suite, IIS is number web server (per web server not per site - there is a difference) but MSN is not the nnumber on dialup, MSN messenger is not the number 1 IM, and hailstorm was renamed Passport.

    3. Re:Really? by Codex+The+Sloth · · Score: 2

      MSN was originally a AOL-esque non-internet service. Didn't catch on. Then it was an internet service provider. Didn't catch on. Then it's just a bunch of lame bug-factory web sites including the ultra hackable Hotmail and MSN Messenger. It's caught on but do they make money from it? Don't think so 'cos they keep selling parts off. It's still no Yahoo! or AOL and that's what the original poster meant by "win".

      --
      I am not a number! I am a man! And don't you ... oh wait, I'm #93427. Ha ha! In your face #93428!
    4. Re:Really? by rseuhs · · Score: 2
      MSN won. It's more popular than ICQ now, dispite that ICQ 2001+ has become much better and faster. Almost ever teenager uses Hotmail.

      Proprietary MSN should extinguish the internet.

      "Internet will never be popular" - Bill Gates (Doesn't that ring a bell?)

      "The Internet? We are not interested in it" - Bill Gates.

      MSN failed completely, now it's just another ISP. And ICQ is still a lot more popular than MSN-Messenger.

    5. Re:Really? by rseuhs · · Score: 2, Troll
      Hey, you forgot:

      • XBox
      • COOl
      • Windows/Alpha
      • Windows/PPC
      • Windows/Mips
      • Blackbird
      • PenWindows
      • Modular Windows
      • "HomeR"
      • "Otto"
      • Ultimate TV
      Actually, most Microsoft-projects fail miserably.
    6. Re:Really? by Anonymous Coward · · Score: 0

      Its the ones they win you got to watch for. Edison failed over a thousand times before he got the light bulb right.

    7. Re:Really? by MAXOMENOS · · Score: 2
      And of course:
      • Antitrust Trial
    8. Re:Really? by BrookHarty · · Score: 2

      Xbox failed? Please tell that to everyone I know buying an Xbox, or people buying 2 (now that its 150 bux) to network Halo. In my corner of the woods, Xbox seems to be doing damn good. And BTW, Windows on Alpha was a rather good idea, We have some NT 4 boxes on alpha we finaly retired due to code red. They run linux just fine now, but to be fair, NT 4 is quite old.

    9. Re:Really? by rseuhs · · Score: 2
      Xbox failed? Please tell that to everyone I know buying an Xbox, or people buying 2 (now that its 150 bux) to network Halo. In my corner of the woods, Xbox seems to be doing damn good.

      Microsoft is the only one losing money and is behind Sony and Nintendo nevertheless. I'm just waiting for them to pull the plug, XBox will never make money for them.

      And BTW, Windows on Alpha was a rather good idea, We have some NT 4 boxes on alpha we finaly retired due to code red. They run linux just fine now, but to be fair, NT 4 is quite old.

      Isn't "good idea" and "have had to retire them" a contradiction?

      Windows/Alpha showed that Microsoft products can be discontinued anytime without warning.

    10. Re:Really? by swissmonkey · · Score: 1

      NT4 Alpha, NT4 PPC and NT4 MIPS failed more because the CPU failed to gain market share than because of NT4.

      The sales of machines with these processors were way too small to justify commitment from MS which is a company selling products by the million.

      As for XBox, I fail to see how it could be flagged as a failure.

    11. Re:Really? by Anonymous Coward · · Score: 0

      Yes, it failed. There can be only two platform games, and they are game cube and playstation 2.

      HALO SUCKS AS A 1ST PERSON SHOOTER !!!

      http://www.penny-arcade.com/view.php3?date=2001- 11 -28&res=l

      Maybe panzer dragoon will prop it up awhile, but Sony is just playing with them.

      http://www.penny-arcade.com/view.php3?date=2001- 05 -30&res=l

    12. Re:Really? by Anonymous Coward · · Score: 0

      The quote should be "I am not a number, I am a free man !". Be sseing you !

    13. Re:Really? by Gnulix · · Score: 1

      Its the ones they win you got to watch for. Edison failed over a thousand times before he got the light bulb right.

      Edison stole all his inventions. Either from employees or from outside sources. He was the Bill Gates of his time...

  20. Slim to none by germinatoras · · Score: 1

    And Slim left town.

    The work that Miguel is doing is admirable - he obviously has the talent and motivation to achieve quite a technical feat. Since the .NET platform will inevitably become popular as developers are brainwashed, strongarmed, forced by managers into using it. So the value of running .NET applications on Linux clearly speaks for itself. Not that I think this is a "good" thing at all, but maybe when MicrosoftOffice.NET comes out, then Linux will finally be a contender on the desktop.

    But none of that will ever be a reality. Microsoft has a covert plan somewhere to torpedo any potential threats to its control on the desktop.

  21. bad/good news for Linux? by Anonymous Coward · · Score: 0
  22. mono != supporting MS by k2enemy · · Score: 2, Informative
    before everyone burns mono for having ties to microsoft, keep in mind that the framework part of .net isn't proprietary. the cli is an open standard, free for anyone to implement. plus, what mono is doing with recreating the class libraries will provide more competition to microsoft, not less.

    the other parts of .net such as passport, application services and MS web services are the troubling part. mono has nothing to do with these.

    1. Re:mono != supporting MS by Anonymous Coward · · Score: 0
      I think some people are concerned that Microsoft may have some
      patent lurking in the background that they will use to squash Mono sometime in the future if it becomes a threat.
      I took a quick glance at the CLI spec and didn't see any mention of patent claims, good or bad. The ECMA policy only states that they will not pass recommendations unless the patentee is willing to license the technology on a RAND basis, but they also have this disclaimer: should an implementor discover another patent, he has to obtain a license agreement with the patent owner and inform ECMA of the existence of the patent.

      That doesn't give me much of a warm fuzzy about the safety of implementing open-source software with Mono.

    2. Re:mono != supporting MS by Anonymous Coward · · Score: 0

      It's still a waste, and legitimizes Microsoft. This same effort could go into Gnu Classpath instead.

    3. Re:mono != supporting MS by alext · · Score: 2

      FYI 'the framework part' of Dotnet is not the CLI - frameworks are component libraries not interpreters/compilers.

      See .NET Framework Essentials, Thai & Lam, pub. O'Reilly.

      This sort of nonsense just plays into the 'Dotnet is a standard' myth.

    4. Re:mono != supporting MS by k2enemy · · Score: 1

      nowhere in my comment did i say that the framework was the cli.

  23. Oh my darling, oh my darling...... by mickwd · · Score: 1, Troll

    ......Oh my darling Java clients.

    Why do I keep getting the feeling that Linux is still on the rebound from Java ?

    Come on, everyone knows they were made for each other. They even share a common interest in
    opposing Microsoft.

    But Linux got sniffy because Java wouldn't open herself to him completely. Maybe she felt
    she was too good for him, maybe she thought he'd never make good, just because he came from
    the wrong side of the enterprise.

    So what does he do ? He goes for another another girl who looks just like her.

    "How I missed her,
    How I missed her,
    How I missed my Java clients,
    Till I kissed her
    Little sister,
    And forgot my Java clients."

    1. Re:Oh my darling, oh my darling...... by Jonner · · Score: 1

      Of course, there's nothing stopping someone from writing a Java compiler for the CLI, but then again, the class libraries would have to be there for it to be useful.

    2. Re:Oh my darling, oh my darling...... by pohl · · Score: 1

      +1 Funny.

      --

      The "cue the foo posts in 3, 2, 1..." posts will commence with no subsequent foo posts in 3, 2, 1...

  24. Time Travel? by Anonymous Coward · · Score: 0

    * The Mono C# compiler was able to compile itself on December
    28th, 2002. The resulting image contained errors though.

    1. Re:Time Travel? by Anonymous Coward · · Score: 0

      It did say it containted errors ... at least they admited to the bug.

  25. *neutral* news for Linux? by Anonymous Coward · · Score: 0

    What exactly is your objection?

    Are you suggesting that the Linux support of a programming language invented by Microsoft will have no impact whatsoever on Linux?

    This is either going to be good news for Linux or bad news for Linux. If it takes tps12 to point this out to the rest of us slashbots, then so be it.

    1. Re:*neutral* news for Linux? by Anonymous Coward · · Score: 0

      Oh EAT ME tps12!

  26. No personal use of .NET or Mono by Daimaou · · Score: 4, Insightful

    I use C#, ASP.NET and VS.NET at work. I find developing web applications with these MS technologies glumed together as irritating as it gets. While the integration between disperate technologies is commendible, VS.NET is slower than frozen mud. Give me a good text editor and command line tools any day.

    I think that the whole Mono project will turn out to be a major debacle. Microsoft is going to integrate and complicate .NET with Windows to the point that Mono will never work. MS will release new .NET crap every year and Mono will play catch up for a year so it finally works again just as MS is releasing a new incompatible version.

    In the past, Microsoft has either presented an "open" standard, or pushed someone else's open standard, only to hijack it in the end, to the detriment of non-Windows users and developers.

    I think the Open Source community would be better off backing a web technology like J2EE and not .NET. Microsoft has proven time and again that it can't play well with others. I think Java has a good record for working everywhere consistantly.

    I would recommend consulting members of the Wine and Samba development groups. I'm sure they have plenty of horror stories about working with constantly changing MS technologies.

    1. Re:No personal use of .NET or Mono by Anonymous Coward · · Score: 0

      You really can't compare this to Wine and Samba. Those are projects reverse engineering because Microsoft doesn't release the specs. Mono is working from standards that even if Microsoft changes them they will at least still have the specs.

    2. Re:No personal use of .NET or Mono by erasmus_ · · Score: 5, Insightful

      How does .NET prevent you from using a good text editor and command line tools? All the files, including forms, code, resource, and project files are simple text/XML files. That means that you can use any text editor, then use the command line compilation tools, which are vbc for VB.NET, cs for C#, etc. And as others above have pointed out, C# has been approved by a standards body, so unlike Samba, there are not going to be issues of trying to integrate with something the vendor (MS) does not necessarily want you integrating with.

      --
      Please subscribe to see the more insightful version of th
    3. Re:No personal use of .NET or Mono by MagPulse · · Score: 2, Informative
      "I think that the whole Mono project will turn out to be a major debacle ... MS will release new .NET crap every year and Mono will play catch up..."
      Miguel replies to this in his FAQ on the Mono web site:
      "Question 37: Do you fear that Microsoft will change the spec and render Mono useless?

      No. Microsoft proved with the CLI and the C# language that it was possible to create a powerful foundation for many languages to interoperate. We will always have that.

      Even if changes happened in the platform which were undocumented, the existing platform would a value on its own."
      Mono will be useful no matter what Microsoft does. Mono is taking Microsoft's expensive, paid-for research and applying it.
    4. Re:No personal use of .NET or Mono by Osty · · Score: 1

      How does .NET prevent you from using a good text editor and command line tools? All the files, including forms, code, resource, and project files are simple text/XML files. That means that you can use any text editor, then use the command line compilation tools, which are vbc for VB.NET, cs for C#, etc.

      What's more, if you don't want to use the VS.NET IDE, save yourself $800+ and just download the framework for free (I would post a URL, but my internet connection at work is all wonky. Look for it at MSDN). You get all the commandline tools necessary for compilation, so you can use your own text editor (vim, source insight, notepad if you must, etc), cobble together some makefiles, and build all the .NET apps you want for free. Sure, you don't get the fancy Forms designer, but if you're not doing GUI development, what's that matter? And if you are, well, anything you can do with the Forms designer, you can do with code.

    5. Re:No personal use of .NET or Mono by alext · · Score: 2

      Boy, this is getting annoying. Any further posts that deliberately confuse the (standard) C Sharp language with the (proprietary) Dotnet platform should be modded down on principle IMHO.

    6. Re:No personal use of .NET or Mono by MagPulse · · Score: 1

      Or you can use SharpDevelop, specifically written to use the free compiler in the .NET framework SDK.

      Unfortunately, it doesn't have a GUI editor to work with WinForms yet. This attempt is the best I've seen.

    7. Re:No personal use of .NET or Mono by soap.xml · · Score: 3, Insightful

      C# is a language. .Net is the platform. The standards bodies have approved the languge but not the PLATFORM. It is the platform that ms is pushing, the language just happens to be new and fancy, but the real push is for .Net the platform. They own the platform, control the platform, license out the platform and ultimatly have the final say on anything about the platform. That is why there may be issues. That is why people should not just jump in head first without having a good plan.

    8. Re:No personal use of .NET or Mono by jpmorgan · · Score: 1

      Uh, WRONG. Both the language and the platform are standards.

      The C# standard is ECMA-334 aand the platform is ECMA-335.

      You should check your facts before spouting off in bold.

    9. Re:No personal use of .NET or Mono by liloldme · · Score: 1

      you do realize that by platform people mean the libraries (database, transactions, gui, and shit) and not the virtual machine?

    10. Re:No personal use of .NET or Mono by Anonymous Coward · · Score: 0
      You do realize that if you actually tried to read shit then you might learn something. From the ECMA-335 standard:

      This Standard ECMA-335 defines the Common Language Infrastructure (CLI) in which applications written in multiple high level languages may be executed in different system environments without the need to rewrite the application to take into consideration the unique characteristics of those environments.

      CLI is a runtime environment, with:

      a file format; a common type system; an extensible metadata system; an intermediate language; access to the underlying platform; a factored base class library.

      This ECMA Standard consists of several sections in order to facilitate understanding various components by describing those components in their separate sections. These sections are:

      Partition I: Architecture Partition II: Metadata Definition and Semantics Partition III: CIL Instruction Set Partition IV: Profiles and Libraries Partition V: Annexes

      It looks like the libraries are taken care of.

    11. Re:No personal use of .NET or Mono by liloldme · · Score: 1
      I have.

      Download the libraries - last time it included barely enough to implement a Hello World. Less than 100 classes.

      So why don't you figure out what the fuck you're talking about before you start flaming me, bitch.

      It looks like the libraries are taken care of.

      No they're not you moron. There's nothing on that spec that defines a platform comparable to MS.NET or J2EE. The part IV on that spec is fucking 16 pages long. That's pathetic.

      Maybe you should actually spend time reading the actual spec which is linked on that page, you fucking retard.

  27. Mono by Anonymous Coward · · Score: 0

    I thought Mononucleosis was bad for people? Why are programmers trying to spread a virus?

  28. It's not the code stupid... by chuckw · · Score: 5, Insightful

    Two of our developers just came back from a .NET training session and were wowed beyond belief. (Note: This session was put on by a private company, not Microsoft). These guys were hardcore Linux/Java hackers working on our latest web based application. What changed their mind? It was the tools. The code had *NOTHING* to do with it as far as they were concerned. I told them there were OSS alternatives that pretty much replicated all of the .NET functionality. They still shook their heads saying it's the tools they were introduced to that made the real difference, not the code. One small example they used was that the MSFT tools allow you to backtrace a transaction all the way from your HTML front end clear on in to the database with a simple click of a button. There were a lot of other examples, but that was the one that stood out in my mind the most. It was the fact that they could write code faster and worry less about the crap that tipped the scales.

    The thinking progresses with the argument that since we're developing on Microsoft tools we should be running a Microsoft OS on our servers since no two JVM's 'er I mean CLR's are alike...

    --
    *Condense fact from the vapor of nuance*
    1. Re:It's not the code stupid... by waspleg · · Score: 1

      yes, i recently talked with a friend who does freelance web development, who also runs linux, was singing the praises of .Net, the languages? no

      it was the seamless integration of everything which was so impressive

      although i haven't used it, i'm sure that mono hasn't reached anywhere near the level of polish that goes into something a multibillion dollar corporation bets their future on.

    2. Re:It's not the code stupid... by consumer · · Score: 3, Insightful
      One small example they used was that the MSFT tools allow you to backtrace a transaction all the way from your HTML front end clear on in to the database with a simple click of a button.

      I bet this works just fine until the day when you need to deviate from the Microsoft plan in some way (maybe you have to do some unusual database stuff, or even talk to a non-Microsoft database that your warehouse uses or use something like a dbm file) and then it will all fall apart. People who learned how to use the tools instead of learning how to design and write programs will be lost when this happens. There is no substitute for understanding how things work, and Microsoft usually makes it harder to do that than other options like Perl or Java.

    3. Re:It's not the code stupid... by tidge · · Score: 1

      Well, from the IBM DB2 end, it works fine

    4. Re:It's not the code stupid... by Anonymous Coward · · Score: 0

      kiss my ass you dick-faced greedy-ass bullshit whore cocksucker soon to be middle-aged fat balding unhappy put a gun in your mouth corporate twat suit.

    5. Re:It's not the code stupid... by Anonymous Coward · · Score: 0

      With Oracle it works fine.

    6. Re:It's not the code stupid... by Iamthefallen · · Score: 4, Insightful

      When that day comes you look up how to do it, if you spend your time with a bad buggy tool solely to get better understanding of the system/framework, you're wasting a lot more precious time. Start coding, when you get stuck, pick up a book or ask around.

      --
      Wax-Museum Fire Results In Hundreds Of New Danny DeVito Statues
    7. Re:It's not the code stupid... by pmz · · Score: 1

      Two of our developers just came back from a .NET training session and were wowed beyond belief.


      That wasn't a training session, it was a marketing session. Usually, people get these warm fuzzy first impressions, and the enthusiasm wears off after actually using the tools for a few weeks.

      And, how much of all those nifty features actually work as expected. With compexity comes bugs bugs bugs!

      This has happened with every major IDE to date. This is also why I still use vi and make.

    8. Re:It's not the code stupid... by Eryq · · Score: 2, Insightful

      Exactly.

      The WONderful thing about using GUIs to develop solutions in problem domain X is that by the time the GUI has been coded, shipped, and is on your computer, what you really need is something which solves problem X', or even problem Y.

      Case in point:

      When I first started coding Java GUIs, I used JBuilder's GUI-based GUI designer. I still think that it rocks. But now that I know more than the basics, I use Emacs, and copy-and-paste from prior implementations. Why?

      • Because I want to color outside of JBuilder's [simple] box, and have more control over how the code is organized.
      • Because now that I know some of the finer points of threads, etc., I can produce cleaner GUI code than JBuilder can.
      • Because JBuilder gets confused if my code deviates too much from their expectations, and I got tired of dumbing things down to suit the GUI builder.

      Tools are great... if you don't mind the fact that you can only do what the tool builder lets you do.

      Now read that last sentence again, and remember who the tool builder of VisualStudio is.

      Where do I want to go today? Whereever I damn well please, thank you.

      --
      I'm a bloodsucking fiend! Look at my outfit!
    9. Re:It's not the code stupid... by jafac · · Score: 2

      The consequence of worrying less about the crap means that there's gonna be more crap you didn't worry about in the end product.

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
    10. Re:It's not the code stupid... by I_redwolf · · Score: 1, Flamebait

      The above post is typical; "it's the tools". It's gonna be those same tools that make the overall code poor. Designs will be poor, code will be badly written and it's because of the "tools". Any good coder or coder worth their weight in salary wants to make sure that they spend time working with every bit of their code. Backtracing a problem makes you a better coder, it makes you understand problems when you have to do it yourself. This is why I don't recognize VB coders as real coders because they can't fucking understand simple concepts. All I see .NET as is VB, with a likeness of Java claiming to be cross portable etc etc; Just Microsoft taking ideas from other people again and mucking them together. There won't be any different applications coming from this, any different ideas or code being made. Anything different at all EXCEPT that it will eventually and I'll bet my life on it.. Block others from using some website or whatever app it is unless they are using a Microsoft certified platform. Thats Microsoft's goal, not being open, not playing fairly, none of that matters. Why can't the opensource community get this through their head; it's like Microsoft gives you a cookie and you happily sit there and eat it while it goes back to pouring cyanide in your milk.

      Miguel is constantly chasing after Microsoft technologies, and I don't know why. Microsoft hasn't had a proven technology that worked well EVER. Unix consistently has.

    11. Re:It's not the code stupid... by Anonymous Coward · · Score: 0

      That's not always true. Why hire some high paid guy full time when you can hire Joe Schmoe off the street to do the same job with the special tools. When something goes wrong, you can get someone to do some contract work. And if you are the high paid guy who knows what you're doing, who says that he wont want something easier too?

    12. Re:It's not the code stupid... by Tony+Hoyle · · Score: 2

      Heh. I went to an MSDN conference where they put together a simple app and was actually put off .net. The thing ran like treacle. They had a multi-user app that was supposed to book cinema tickets and it was taking 30 seconds for the web page to appear.. on a LAN! The whole database backend looked like an explosion at a spagetti factory, too (and no locking, but then I can put that down to the fact that it was only a demo).

      God help us if that ever gets popular... you'll need a quad Xeon just to run a small website.

    13. Re:It's not the code stupid... by damiam · · Score: 1

      Very very few.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    14. Re:It's not the code stupid... by Bodrius · · Score: 3, Informative

      I don't know about the HMTL-down-to-DB stuff.

      But I have to say the MSFT tools are really impressive, precisely because you don't have to choose between using the tools and designing and writing the program yourself.

      Jumping back and forth between the code and the GUI is a breeze, and the code auto-generated by the GUI is amazingly clean, easy to modify by hand.

      But it's the simple idea of #region what I have found makes the greatest difference in coding. I expect to see similar support for these in other tools, and I hope in other languages/platforms.

      As a matter of fact, what I like about Visual Studio .NET has nothing to do with "Microsoft plan", or locking yourself out of your own source code, or limiting what you can do with your code. You can work in as low a level you want and never touch a wizard/GUI-builder. They're just simple ideas that help you to write CODE faster, easier, AND better.

      There's no reason for other tools not to be able to copy VS.NET functionalities and provide decent IDEs for Java and other platforms. I fully expect them to do so, because I'm a Java programmer. As a result of .NET, I expect the Java development tools dramatically, and I suspect the same will happen with other languages.

      --
      Freedom is the freedom to say 2+2=4, everything else follows...
    15. Re:It's not the code stupid... by m_pll · · Score: 1
      God help us if that ever gets popular... you'll need a quad Xeon just to run a small website.

      I recently noticed that Carpoint now seems to be running on ASP.NET (the default page still has .asp extension, but the rest are .aspx). Definitely not a small site.

    16. Re:It's not the code stupid... by lient · · Score: 1

      My coworkers really like JBuilder and its GUI builder too. I've never been big on tools to create code for me. I get too annoyed with the code they generate and end up rewriting it anyway.

      Emacs has so many features that I can't stand using a special purpose editor, anymore. Special purpose editors like JBuilder and MSVC want to do everything for you. By doing so, they lock you into their system. Requiring the installation of a particular non-portable editor to build code that otherwise would be is ridiculous, IMHO.

    17. Re:It's not the code stupid... by Chris+Johnson · · Score: 2
      You can do just as impressive demos with other sorts of tools in other sorts of contexts.

      On the Mac, for light-duty applications with extensive GUI widget use, the development tool REALbasic is like that. You can drag controls onto a window and build working 'mockup' applications without even writing code, even to the point that they will have tabbing between windows, drag and drop, etc... if you can program well using widgets and an object model you can knock out functional apps absurdly fast.

      I'm of the mind that what needs to happen is Microsoft needs to be clubbed over the head until dead, because if not for them, LOTS of people would be making IDEs and tools like this. The way things stand, you have to have a product as great as REALbasic, AND you have to have it on an alternate platform like the Mac, in order to get anywhere with it. And since there's lots of gearheads programming Linux, they're not racing to develop this sort of thing... not their style or their culture...

  29. .NET C# J# by m0rph3us0 · · Score: 1

    Why do we need C#, its just a java syntax, with different class names. A different VM, and different byte code. Really it doesn't seem like their is much point to this whole C# business other then when MS feels like it they change the C# license, or start sueing other companies for IP infringement. Doesn't seem like that good of an idea. At least Sun isn't in the market position to start pushing their weight around. Personally, I would rather see development into a better JVM. The .NET framework on linux seems to be just a way for MS to get its hooks into Open Source with out actually having to do anything, we're inviting them in. Does the .NET framework actually provide anything that isn't easily achievable with other tools? I would think that if someone wanted to build extremely fast portable GUI apps they would write them in C/C++ using portable libraries such as GTK. As far as network services go, java seems plenty fast. And speeding up java is probably only a matter of better JVM's and / or compilers. Hopefully the lasting effect of .NET will be to encourage Sun to improve java.

    1. Re:.NET C# J# by certsoft · · Score: 1
      A different VM, and different byte code.

      I think that's one of the key differences, a different VM and byte code. A byte code that is designed to support other languages, including those that have a clue about unsigned and signed integers of different sizes beyond what Java supports.

      Borland has announced Delphi for .NET, I wonder if they plan on having Kylix for Mono?

    2. Re:.NET C# J# by Anonymous Coward · · Score: 0

      Why do we need Java? It's just C++ syntax with different class names...

    3. Re:.NET C# J# by mr.+marbles · · Score: 1

      the main thing is the with JVM you have to program in Java. With mono you can program in any language you want and compile it for mono. this is great cause it allows code reuse, you would be able to use the work of others in your own work even if their work isn't written in the same programming language. As i understand it the CORBA stuff in GNOME does the same thing except that mono solves the problem with smaller objects (or whatever they call it).

    4. Re:.NET C# J# by Anonymous Coward · · Score: 0
      Why do we need C#

      Because .net is less expressive than most languages. It needs a downgraded language so that programmers don't write perfect-looking programs that turn out to be un-compilable.

  30. Join them? by Anonymous Coward · · Score: 0

    Ok, then why don't you be the first to format your hard drive and install windows?

    If there's no point trying to "beat" microsoft, then you have no reason to have Linux (or any other OS). Just give in and go Windows, then.

    1. Re:Join them? by FooBarWidget · · Score: 1

      > Ok, then why don't you be the first to format your hard drive and install windows?

      I already have Windows...
      And unfortunately, I still need it for games and for scanning.

    2. Re:Join them? by Anonymous Coward · · Score: 0

      Games are the biggest reason Linux is not going ever going to be a #1 desktop. Kids have a huge say in what kind of PC their families get. One of the problems Apple has in attracting kids is the lack of games (or slow ports).

      Scanning, I'd say, is secondary. There are scanners that work well with Linux (granted not that many and not as well as with Windows). Most of what people scan at work has nothing to do with work, from what I've seen (save for graphics artists).

    3. Re:Join them? by King+of+the+World · · Score: 1

      The hassle of nVidia cards and nVidia drivers are the main reason. Games will follow if they can get an audience.

  31. Bob... by sterno · · Score: 4, Insightful

    Microsoft Bob... Need I say more? :)

    Overall .Net is going to get used by the places that have tended towards being heavily windows environments originally. Companies that have been using Unix, Linux, and Java will probably not be moving to .Net anytime soon.

    Personally I'd be very interested in using .Net on Linux provided that it works well and provided that I can have faith that, in the long term, I'll be able to do this without risking a microsoft tax or lock-in.

    My big concern down the road is that Microsoft is going to start using patents and license restrictions to control the fate of .Net. Wait until enough people develop .Net solutions on alternative platforms then say, "well that's great, now you can pay us a license fee."

    I just can't believe that Microsoft would develop any technology that wasn't designed from the ground up to further their control. If just about any other company had put forth .Net I'd probably see it as a good thing. Hell, I've been a java developer for a while and I don't think much better of Sun than I do of Microsoft. The only reason I trust sun to stick with some level of openess is that it's about the only ammunition they have available to leverage against Microsoft's hegemony.

    --
    This sig has been temporarily disconnected or is no longer in service
    1. Re:Bob... by JFMulder · · Score: 2

      Wait until enough people develop .Net solutions on alternative platforms then say, "well that's great, now you can pay us a license fee."
      Now that would be a diabolical plan. but IIRC, you can't apply for a patent if something has been in the wild for one year. So if Microsoft hasn't applied yet for a pattent on some core aspect of C#, then it probably isn't going to happen. Is there anyone who can clarify that?

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

      NO. SUBMARINE PATENTS. 2-3 years after it has been in the wild a submarine patent can surface and kill the products using the patent.

  32. consciousness by Anonymous Coward · · Score: 0

    TOE Ff. 2Ah. Explanation: 1. A conscious entity is the essence of free will. a. There is a finite and constant number of conscious entities. b. Each is separate from all conscious entities. c. Each has no beginning. d. Each has no end. e. Each establishes a sphere expanding at the speed of light upon denaturing of the conscious system. f. Each cannot be active (inputting and outputting) if they are not coupled with a conscious seat. g. Each has a nonquantized infinite storage of previous quantized input. g1. The storage resists attempts to glean information from it. g2. The storage cannot be directly shared--it must go through conscious seats. h. Other than the storage of g, each is identical to all other conscious entities. 2. A conscious seat is the physical portion of a conscious system. 3. A conscious system is the fusion of one conscious entity with one seat of consciousness. a. It has a beginning. b. It has an end (denaturing). c. It is formed under the following conditions. c1. A seat is ready to accept an entity. c2. At least one entity's sphere of influence encompasses the seat. c3. The center of one of the spheres is closest to the seat. This one is caught. d. It has a quantized input and output. e. It must be either active (inputting and outputting) or inactive (doing neither yet not denaturing). f. Output is determined by the entity's storage, system input, and free will. 4. The universe. a. It is quantized in time and space. b. It has no beginning. c. It has no end. d. Space is bounded. e. Energy is finite and constant. Meaning: The meaning of all conscious entities is to pursue two goals--love and power. A conscious entity, in a conscious system... -Common subgoals: C1. controls reality. C2. knows reality. C3. has mastery of potential reality. C4. has mastery of the abstract plane. C5. never denatures from its seat. -Love subgoals: L1. and one other are the only conscious entities that can be active in a conscious system for all future time and space. L2. is bound by a seed of love to the other conscious entity. -Power subgoals: P1. is the only conscious entity that can be active in a conscious system for all future time and space.

  33. M$ business plan by Anonymous Coward · · Score: 0

    1. .NET
    2. ?
    3. Profit

  34. MONO and GNOME are seperate by jaaron · · Score: 3, Insightful

    Mono has nothing to do with GNOME. If you'd do your research you'd realize that they are seperate projects and that the rumors that GNOME is going to be based on .NET are just that -- rumors. There are some people that are involved in both projects, however, the GNOME project has come out and said they currently have no plans to move to MONO or .NET any time soon. Maybe someday, who knows? But they are SEPERATE projects. Read Miguel de Icaza's own reply to this idea.

    Besides, have you ever looked at the MONO project? They're doing some really impressive stuff. You probably shouldn't write it off just because you're afraid of M$. I'm a java programmer and an avid Linux user, however, there are some features of C# and the .NET framework that are really nice. What's more, unlike Sun, M$ has given their language and technology up to be standardized. In that sense, it's more free than Java.

    --
    Who said Freedom was Fair?
    1. Re:MONO and GNOME are seperate by alext · · Score: 2

      Presumably the person that modded this as Insightful reads every discussion from the bottom up?

      Or would the parent poster care to share some insight into the standardization status of Dotnet APIs like Windows Forms and ADO.NET?

    2. Re:MONO and GNOME are seperate by GrassyKnowl · · Score: 1

      I would not give Microsoft a beachead in the Linux and open source platform. What Microsoft probably wants to do is make .Net an indespensable component and require license fees later on. If they can do this, they will control the Linux platfrom.

      Wake up and stop prostituting with a monopolist.

    3. Re:MONO and GNOME are seperate by Mark+Pitman · · Score: 1
      What Microsoft probably wants to do is make .Net an indespensable component and require license fees later on. If they can do this, they will control the Linux platfrom.

      Since Mono is not being developed by Microsoft and is being released under various open source licenses, this is not a possibility. Microsoft has already submitted the C# language specs and the CLR specs to ECMA anyway. There's no "taking it back" now. It might be a good idea for you to read the FAQ on the Mono site.

    4. Re:MONO and GNOME are seperate by Anonymous._.Coward · · Score: 1
      Not only have Microsoft submitted the C# and CLR (latter called CLI in this context) specs to ECMA, they have been accepted and standardised. C# is ECMA-334 and and CLI is ECMA-335.

      Anyone can implement their own versions under any license.

      --

      take a triptonica to subthunk

  35. what's wrong with you people by Anonymous Coward · · Score: 0

    What the hell is wrong with you people! Get lives!

  36. It *is* the code by Koyaanisqatsi · · Score: 3, Insightful

    I can't speak for all the "dot-net languages", but I've been writing lots of ASP.Net code in C# and VB.Net recently and guess what? It's not the tools, it is the framework itself.

    I'm not using Visual Studio, I'm working out of the .Net SDK and what makes me all wowed is how quickly I can do things that used to take hours to build on ASP 2.0, like complex form interfaces, data validation, query output, etc. It's well worth looking at the samples to get acquainted with, I bet you'll be surprised with how powerfull and flexible the framework is :-)

    1. Re:It *is* the code by Tablizer · · Score: 2

      (* I'm not using Visual Studio, I'm working out of the .Net SDK and what makes me all wowed is how quickly I can do things that used to take hours to build on ASP 2.0, like complex form interfaces, data validation, query output, etc. *)

      That is because pre-NET ASP had no form management framework. These can be added/used/built without marrying yourself to Gates.

      From my reading, I found ASP.NET is too geared toward winning benchmark tests rather than code simplicity and RAD. It's out-of-the-box forms managers is better than what old ASP had, but that is not saying much.

  37. funny... by krammit · · Score: 1

    Just as Mono starts making a little headway, Microsoft starts mapping out .NET V.2. I really would like to see this project accomplish what it set out to do, but you can't like it's odds.

    --
    "Watch your cornhole, bud."
    1. Re:funny... by miguel · · Score: 3

      Well, .NET 1.0 was released on January, so by that metric Mono is already late to the game. But so is every other piece of free software, and we still manage to do a great job.

      Miguel

    2. Re:funny... by alext · · Score: 2

      A great new 'way to develop'? What exactly are you driving at here?

      As a matter of interest, what do you think the chances of a cross-platform (Mono, Dotnet) version of Photoshop are?

  38. This is the end.. by Anonymous Coward · · Score: 0

    I mean.. great.. first this thing compiles it self. Soon it will escape from it's binary cage and then it will kill us all!

    Good work, hackers..

  39. SOAP blows bubbles. by Anonymous Coward · · Score: 0

    XML-RPC rules.

  40. Not that great an example... by sterno · · Score: 5, Insightful

    There was an article just the other day on here about how web developers are designing for Microsoft now and ignoring standards. Though Microsoft is never going to make themselves fully incompatible with other browsers, they have continued to distinguish themselves from the competition by their "innovations". The result is that while I can surf websites on linux using mozilla, I will be given a decidedly different experience doing so. Some sites will refuse to let me in all together, and others will just break horribly.

    Now, you might say the reaction to this is that those companies will suffer from losing my business. Yeah, so they are losing what, 5% of the market? Ooooo, big deal. This causes people who don't have a tolerance for these glitches to go with a windows platform out of their lack of patience for that stuff.

    --
    This sig has been temporarily disconnected or is no longer in service
    1. Re:Not that great an example... by Anonymous Coward · · Score: 1, Insightful

      And that article was mostly bullshit since standards compliance has been dramatically increasing on the web not decreasing. The amount of Bugzilla evangelism bugs has really dropped off and it's getting rare to find recently done sites that bust things.

    2. Re:Not that great an example... by Salsaman · · Score: 2
      Still, what would you rather invest in - a company that aims to reach 95% of their potential market, or one which aims to reach 100% ?

      I know what my answer is, and it ain't the 95%.

    3. Re:Not that great an example... by flacco · · Score: 2
      Yeah, so they are losing what, 5% of the market? Ooooo, big deal.

      They're throwing away 5% of the market and giving it to a competitor. And in many businesses that IS a big deal.

      --
      pr0n - keeping monitor glass spotless since 1981.
    4. Re:Not that great an example... by Anonymous Coward · · Score: 0

      > And that article was mostly bullshit since standards compliance has been dramatically increasing on the web not decreasing. The amount of Bugzilla evangelism bugs has really dropped off and it's getting rare to find recently done sites that bust things.

      Exactly, and I hope someboby mods up your post.

      The article, that sterno's post refers to, was pure Microsoft propaganda, and there is no way that sterno's post deserves its current score of 5.

      Apparently, being duped by Microsoft earns high points these days.

  41. Yes as long as IBM CLR by Anonymous Coward · · Score: 0

    I'm hoping that once the CLR is ISO standardized it will be adopted by IBM and made accessible in their future tooling. IBM is large enough to help bridge the gaps between Sun and MS.

    This would give them the best of both worlds and push forward both J2EE and .Net for open and closed source efforts.

  42. makes me nervous by Dr.+Awktagon · · Score: 5, Insightful

    I guess I have to make my obligitory post on this subject:

    As a technology person, I like the .NET framework, the web services aspects, the runtime, and I think C# is infinitely better than C++ (then again, what isn't...). I'm looking forward to playing with C# on my Linux machine.

    But I'm just a little creeped out by the idea of using Mono for anything important (business-related), such as deploying services or products. I really have trouble figuring out what Microsoft has to gain from allowing Mono to exist indefinitely. They have plenty to gain from a sweeping, cross-plaform, bait-and-switch ploy.. they can just wait until Mono is somewhat established, apps are built and deployed... then break it and wait patiently for the inevitable migration back to Windows.

    I would like to hear from Microsoft that they won't sue any Mono developer (or user) for patent infringement. I'd like to hear that all relevant APIs and specification are public and open and will stay that way. Miguel's attitude seems to be one of "hope", quote:

    So I think the APIs will remain fairly stable, and I hope that Microsoft won't go into proprietary protocols or protocols that would make it really hard for us to implement Mono. There's is always the possibility it will do so. Microsoft has some strange patterns in terms of how it competes. I really hope it will "behave like a good citizen," as Steve Ballmer said recently it would.

    Now, I could be all wrong, Microsoft actually might not mind that we will use their technology and not their products...but...this is Microsoft we're talking about here.

    Sure this sounds like fear, uncertainty, and doubt, but that's exactly what I feel whenever I think about Mono......

    1. Re:makes me nervous by DavidJA · · Score: 1

      ...I like the .NET framework, the web services aspects, the runtime, and I think C# is infinitely better than C++...But I'm just a little creeped out by the idea of using Mono for anything important...

      Why not develop in C# for Mono then IF(when) MS breaks Mono, if you still like C# then move the app to a Win32 platform!

      Please don't say "it's microsoft, it must be bad", when you last experience with Microsoft's products was probably Win95.

      I don't particualy like microsoft myself, but I'm open-minded enough to give their technolagies a try.

    2. Re:makes me nervous by Anonymous Coward · · Score: 0

      >> Why not develop in C# for Mono then IF(when) MS breaks Mono, if you still like C# then move the app to a Win32 platform! ................

      In other words, fall for the bait and switch, hook line and sinker!!!

      Microsoft should thank Mono then, for giving them new customers when that happens.

    3. Re:makes me nervous by dybvandal · · Score: 1
      they can just wait until Mono is somewhat established, apps are built and deployed... then break it and wait patiently for the inevitable migration back to Windows.

      how can they break Mono? they can only break compatiblity to .Net

      will all your Mono based apps still work (on Linux, Windows .. etc)? Yes they will!

      everybody that thinks that .Net makes technical merit can't be creeped by M$ involvedment because .Net lives in Mono without M$ direct involvement

      if M$ makes changes to .Net that dont improve .Net but only break compatiblity to Mono WE DO NOT HAVE TO CARE

      the only problem I see are people building up their .Net infrastructure around Microsoft development tools, because these guys will have a problem if M$ breaks compatibility

    4. Re:makes me nervous by DavidJA · · Score: 1

      In other words, fall for the bait and switch, hook line and sinker!!!

      No, try the technology, IF you think that it's better then everything else out there then use it!

      Don't let the fact that it was developed by Microsoft stop you from using it if it is the best solution for you.

    5. Re:makes me nervous by nihilogos · · Score: 3, Interesting

      and I think C# is infinitely better than C++ (then again, what isn't...). I'm looking forward to playing with C# on my Linux machine.

      Language X > Language Y statements are some of the most pointless ever made. Suppose you wanted to write an accelerated 3d game? Suppose you wanted to do some numerical physics?

      And you might be waiting a while for C# on your linux machine. You can still get java which does the same stuff however.

      --
      :wq
    6. Re:makes me nervous by plierhead · · Score: 1
      "But I'm just a little creeped out by the idea of using Mono for anything important (business-related)"

      You've hit the nail on the head - mono will be great for fiddling with but in a huge enterprise-wide deployment theres no way that it would be adopted by any IT manager who valued his job. All it does is play into Microsoft's hands ("Why yes you SHOULD use .NET, Mr. customer. Its completely open, there's even an open source version that runs on linux !").

      I don't know Ximian's real agenda but it must be tempting for them to think about the old bait and switch - get people hooked on the GPL'ed mono code and then offer the same code under a "for fee" redistributable license. Its been done before.

      --

      [x] auto-moderate all posts by this user as insightful

    7. Re: makes me nervous by baquiano · · Score: 1

      As I see it, there's really nothing to worry about. Imagine the following long-term scenarios:

      (a) .NET fails to gain mindshare (and market share) among developers and, after years of fruitless marketing, slowly fades into oblivion. In this scenario, Mono is simply irrelevant.

      (b) .NET catches on like wildfire on a savannah, and the market is flooded with 'Designed for .NET' software. In this case, assuming that Mono effectively achieves total compatibility, the underlying OS will suddenly become irrelevant, and [GNU/]Linux will benefit from instant availability of commercial development efforts. [GNU/]Linux might become mainstream!

      (c) .NET gains enough maket share to stay alive and kicking, but is just another player in an increasingly heterogeous world (this is my bet, BTW). In this scenario, .NET is much like Java: a strong niche player, but a niche player nonetheless, with no real power to really affect the Open Source movement in significant ways.

      Note that if Micro$oft is really committed to make .NET a truly platform-agnostic standard, then any advantage that .NET-on-Windows might have could vanish when the technology is mature enough. Again, look at Java. Is Sun's JVM implementation on Solaris significantly better that [pick you favorite JVM] on [pick your favorite OS]? Has the fact that Sun invented Java improved the situation for Solaris in the server arena? THe same could happen for .NET: Mono could potentially be better than Microsoft's .NET implementation (at least on certain niches).

      In conclussion: at worst, Mono simply doesn't hurt, at best, it could help a lot.

      --
      You're bound to be unhappy if you optimize everything. --Donald Knuth
    8. Re:makes me nervous by Zeinfeld · · Score: 2
      Language X > Language Y statements are some of the most pointless ever made. Suppose you wanted to write an accelerated 3d game? Suppose you wanted to do some numerical physics?

      There is probably a good deal of discussion about baseball which is more pointless. But just because most discussion in that vein is pointless does not mean that all of it is.

      C++ was from the start a language with major difficulties. C had a bunch of problems that could only be fixed by taking bad ideas out of C, C++ took nothing out and added a lot more complexity in.

      Java and C# both started from the premise that people wanted a good language for writing new code in and absolute backwards compatibility was not their principle concern. As a result C# has a switch statement that allows a compiler to catch the common programming error of forgetting the break statement, Java likewise avoids that problem (slightly differently). Both C# and Java eliminate buffer overrun errors which are the #1 cause of security problems and so it goes on.

      But the main reason for using C# or Java is that you don't have the tortured aaa::b.c->d.e->g (x,y) syntax which is only necessary because in the dim and distant past much of the C and C++ core was coded as separate preprocessors.

      As for the efficiency question, C# is certainly as fast as C++ if you use the compile on install option and for numeric stuff is quite a bit better as the compilers are optimised for the specific intel processors.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    9. Re:makes me nervous by miguel · · Score: 2

      People said the same thing about Linux a few years ago, so this comment has no effect on me ;-)

      Love and Peace

      Miguel.

    10. Re:makes me nervous by nihilogos · · Score: 2

      C++ was from the start a language with major difficulties. C had a bunch of problems that could only be fixed by taking bad ideas out of C, C++ took nothing out and added a lot more complexity in.

      Simpler I/O, simpler memory allocation, a standard library of useful types all make C++ a lot easier to program in than C. The standard library containers also make it a lot easier to avoid buffer overflows.

      But the main reason for using C# or Java is that you don't have the tortured aaa::b.c->d.e->g (x,y) syntax which is only necessary because in the dim and distant past much of the C and C++ core was coded as separate preprocessors.

      If someone *really* needs to use a member function of some member pointer in some pointer in some namespace I'd like to see how C# or java avoids syntax like this without trivial substitutions of "." for "->".

      As for the efficiency question, C# is certainly as fast as C++ if you use the compile on install option and for numeric stuff is quite a bit better as the compilers are optimised for the specific intel processors.

      Could you provide links to some benchmarks?

      --
      :wq
    11. Re:makes me nervous by Zeinfeld · · Score: 2
      If someone *really* needs to use a member function of some member pointer in some pointer in some namespace I'd like to see how C# or java avoids syntax like this without trivial substitutions of "." for "->".

      It is the trivial substitution of . for any of ., :: or -> that is the advantage. Instead of having to spend 30 seconds remembering whether something is a structure, a pointer or whatever each time you just hit the same key.

      And yeeeessss this is not exactly rocket science, but add up the time saved from not having the compiler reject a change because of finger trouble and you have probably saved yourself 15 minutes or so over the course of the day.

      More importantly for me, not having to piss arround with the C++ indirection operator guessing game means that I keep my train of thought focused on the problem I am trying to solve and not the makework introduced by the braindamage in the language.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    12. Re:makes me nervous by alext · · Score: 2

      Let me get this straight:

      You're claiming that Linux was threatened by MS in the same way as some (including me) believe Mono is now?

      I guess I'm just not reading the right news sources! Feel free to clue me in as to where I can find stories like the following:

      I really have trouble figuring out what Microsoft has to gain from allowing Linux to exist indefinitely.

      They have plenty to gain from a sweeping, cross-plaform, bait-and-switch ploy
      [MS baiting with Linux?]

      They can just wait until Linux is somewhat established, apps are built and deployed... then break it and wait patiently for the inevitable migration back to Windows.

    13. Re:makes me nervous by lient · · Score: 1

      Instead of having to spend 30 seconds remembering whether something is a structure, a pointer or whatever each time you just hit the same key.

      If you have a pointer, you have to dereference it and then use the dot operator to call something. Arrow is simply a shortcut for dereference and call something. Yes, having a smart dot operator that does the right thing for a pointer helps you forget you have a pointer. This is NOT a good thing, however. The difference between a pointer and a stack object is more than just syntactic. They need to be handled differently in your code. Having the syntax the same makes it easier to forget the differences and your responsibilities as far as cleanup, etc...

    14. Re:makes me nervous by Zeinfeld · · Score: 2
      Having the syntax the same makes it easier to forget the differences and your responsibilities as far as cleanup, etc...

      Which is handled by garnage collection.

      I would much rather pay 10% extra for faster processing hardware than 20% extra on my programming budget to have people's memory allocation bugs discovered and fixed.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    15. Re:makes me nervous by nihilogos · · Score: 2

      Which is handled by garbage collection.

      would much rather pay 10% extra for faster processing hardware than 20% extra on my programming budget to have people's memory allocation bugs discovered and fixed.


      And very often automatic garbage collection is undesirable. If I am writing a complicated 3d game I don't want the garbage collector kicking in halfway through rendering a frame. I know in some languages such as Python you can control its behaviour but this is way more of a pain than looking after your own memory.

      If you are writing a high performance app or for an embedded appliance memory considerations are important. Pointers are an excellent way to get the most out of your resources.

      I don't doubt that C# is a great language for writing web interfaces to MS databases. However calling it "better" than C++ is silly.

      --
      :wq
    16. Re:makes me nervous by elflord · · Score: 1
      Which is handled by garnage collection. I would much rather pay 10% extra for faster processing hardware than 20% extra on my programming budget to have people's memory allocation bugs discovered and fixed.

      If you're foolish enough to make decisions like this without knowing anything about the context, there's a good reason you aren't the one making these decisions (just a guess)

      As for "memory allocation bugs", I rarely have memory allocation bugs in my C++ code. if you really think memory allocation bugs are the major issue with C++ development, you don't know C++ very well. HTH,

    17. Re:makes me nervous by elflord · · Score: 1
      C++ was from the start a language with major difficulties. C had a bunch of problems that could only be fixed by taking bad ideas out of C,

      Nonsense. C was, and still is one of the most successful programming languages in existance. All programming languages make different tradeoffs, and C consistently makes tradeoffs in favor of simplicity and performance.

      C++ took nothing out and added a lot more complexity in.

      In practice, one can get by without using very much of the standard C library for the most part.

      Java and C# both started from the premise that people wanted a good language for writing new code in and absolute backwards compatibility was not their principle concern.

      Wrong. Java and C# made completely different design tradeoffs to C++. The move was towards more runtime flexibility and less compile time checking. The reason for this is that there were certain application domains where these tradeoffs were appropriate. It has nothing to do with trying to design a "better" language than C++.

      As with most posters who insist that one tool is "better" than the other, you make the mistake of confusing design tradeoffs with a free lunch.

      As a result C# has a switch statement that allows a compiler to catch the common programming error of forgetting the break statement, Java likewise avoids that problem (slightly differently).

      switch statements are rarely necessary, and the programming error you cite is not common if you rarely use switch.

      Both C# and Java eliminate buffer overrun errors which are the #1 cause of security problems and so it goes on.

      C++ does not have a problem with buffer overrun errors if you use it sensibly. The main causes of errors -- out of bounds array indexing, and static arrays -- are addressed by dynamic container classes, and STL algorithms (as opposed to writing loops). The nice thing about using the STL algorithm approach is it eliminates the cause of the problem (logic errors with loop bounds) rather than just treating symptoms.

      is that you don't have the tortured aaa::b.c->d.e->g (x,y) syntax

      Java has its own issues with syntax, which is pretty funny given that you're claiming it wasn't burdened by backward compatibility. The syntax is as bad as C++, but at least C++ has the excuse that it's C compatible. Compared to Eiffel or python, java syntax is a bad joke.

      As for the efficiency question, C# is certainly as fast as C++ if you use the compile on install option and for numeric stuff is quite a bit better as the compilers are optimised for the specific intel processors.

      do you have any supporting evidence for this claim ? VM vs native code are not the only performance issues that Java and C# have.

    18. Re:makes me nervous by Zeinfeld · · Score: 2
      If you're foolish enough to make decisions like this without knowing anything about the context, there's a good reason you aren't the one making these decisions (just a guess)

      If a decision of that type was made I would be one of the people who made it. In practice there are very few projects where we begin from a completely new code base. For our new applications we generally use Java, but that is largely because we hired a group of folk out of JavaSoft.

      The basis on which the decision would be made is programmer productivity, the quality of the end result and the cost of ongoing maintenance.

      There are applications where I would not want to use Java. There are not very many and even fewer where I would not use C#. The remaining ones are cases where I would not want to use C++ either.

      It is actually quite easy to override the automatic garbage collection, you simply call the dispose method explicitly when you have finished with an object. If you forget you might end up with the garbage collection getting triggered, but that is a much smaller penalty than a memory leak. You can even replace the standard stop and collect garbage collector with an incremental one if your application demands.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    19. Re:makes me nervous by elflord · · Score: 1
      The basis on which the decision would be made is programmer productivity, the quality of the end result and the cost of ongoing maintenance.

      Right. I think the main thing you get moving to java is a tradeoff -- you lose quality in the end result, but increase productivity. You're right that you can speed up an application by throwing more hardware at it, but this requires all your users to do the same. Actually, the fact that *you* can throw more hardware at the problem is an argument in favor of a system with tougher compile requirements and lower runtime requirements.

      It is actually quite easy to override the automatic garbage collection, you simply call the dispose method explicitly when you have finished with an object. If you forget you might end up with the garbage collection getting triggered, but that is a much smaller penalty than a memory leak.

      if you're having serious problems with memory leaks in C++ based projects, then you not only have incompetent developers, you have a project management problem. Memory leaks nearly always boil down to severe problems with coding style. Java is not a silver bullet either, and it will not save you from incompetent project managers and developers.

    20. Re:makes me nervous by lient · · Score: 1

      If you want garbage collection in c++, you can have it.

      http://www.hpl.hp.com/personal/Hans_Boehm/gc/

      You should also use the shared_ptr in http://www.boost.org

      Just because a feature is not built into the language doesn't mean it can't be done. It just means I have more choices, which I like a lot.

    21. Re:makes me nervous by Zeinfeld · · Score: 2
      if you're having serious problems with memory leaks in C++ based projects, then you not only have incompetent developers,

      Actually buffer overrun bugs would be a bigger worry.

      I didn't have those problems when I wrote C because I had a bunch of macros that handled it all for me. But other folk seemed to have difficulties...

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    22. Re:makes me nervous by elflord · · Score: 1
      Actually buffer overrun bugs would be a bigger worry. I didn't have those problems when I wrote C because I had a bunch of macros that handled it all for me. But other folk seemed to have difficulties...

      Again, most buffer overruns are a result of unchecked index based access, or static buffers that turn out to be too small. Neither of these are an issue with the C++ code I write-- you use STL algorithms, and iterators, and dynamic vectors as opposed to fixed size static arrays.

      If there are substantial problems with large numbers of developers using their tools poorly, you have a much bigger problem on your hands than choice of language.

  43. Java? .NET scales better! by DavidJA · · Score: 1

    It is! But it happened 7 years ago with the release of Java.

    Correct, this was done a long time ago by Java, but according to this survey, Microsoft have done it a lot better. Read past the part where they compare Microsoft's BETA JDBC drivers to the rest of them, and

    Java on Oracle was the best at Jacva with a response time of 600 pages per second for 800 users, but just look at the .NET tests for the same app. 800 pages per second for 850 users!

    1. Re:Java? .NET scales better! by Anonymous Coward · · Score: 0

      Maybe I'm glanced over the review too quickly but I couldn't any information about what jsp server they used. Tomcat? BEA WebLogic? Makes a noticeable difference.

    2. Re:Java? .NET scales better! by Anonymous Coward · · Score: 0

      And it's just the beginning. I bet if they retested with the recently released Oracle Managed provider, they would get some nice stuff with oracle as backend. Our testing of the final java driver to hook a legacy java app running on an e10K to a SQL server was impressive. Java app couldnt process data fast enough to keep 2 way box busy. Oracle on the other hand breaths hard on a 16 way partition. It's amazing what people get used to - they think something is great on a 32 way machine and then it's compared to a 2 way or 4 way modern intel, and boy do folks feel stupid for spending all that money.

  44. Mono by noxavior · · Score: 1

    nucleosis? Doesn't anyone doing stuff for Microsoft these days come up with names *other* then toxic, deadly, contagious stuff?

    --
    Karma:This parrot is dead! (and so is the joke.)
  45. Qt#: KDE has Mono bindings in cvs. by Anonymous Coward · · Score: 2, Interesting

    Hmm, that does not seem a wise choice in light of this: http://qtcsharp.sourceforge.net and this: http://developer.kde.org/language-bindings/qtcshar p/index.html

    You can find these bindings in KDE's cvs for quite sometime. ;-)

    Cheers!

  46. the first one's always free by Anonymous Coward · · Score: 0
    Why would someone intentionally flirt with danger? Every day someone smokes their first "rock" or injects heroin for the first time. Mono: just say "no".

    Mono does not make any sense for those interested in free software. Embracing Mono only helps one company: Microsoft. It lends legitamacy to their scheme to capture control of the net and and net transactions.

    Just because a hack can be done doesn't mean that it should be done.

  47. The real difference between .NET and Java by MeowMeow+Jones · · Score: 1

    I can take a binary shared library and inherit my own classes from it transparently even if the source code NO LONGER EXISTS. This library could have been written in COBOL or FORTRAM. It doesn't matter. There's no need to design home-made wrappers.

    Can Java do that?

    Isn't C++'s problem that it's only really reusable on a source code level?

    --

    Trolls throughout history:
    Jonathan Swift

    1. Re:The real difference between .NET and Java by Anonymous Coward · · Score: 0

      I fail to see how that is a good thing. From my limited knowledge, that's not going to happen with COBOL. Now if you are talking about OO Cobol, I doubt you're going to find many working examples in production today. The financial systems I am aware of written in Cobol is the non OO flavor. Your argument would make sense if C# an OO language could inherit from Cobol a non OO language. My knowledge is limited, so correct me if I am wrong.

    2. Re:The real difference between .NET and Java by Anonymous Coward · · Score: 0

      Everything gets compiled into IL Assembly. This assembly language is the CLR supreme God. If it can't be done here then it can't be done in any of the other higher level languages. You can write code in the IL Assembly but who really wants to. Its up to the language implementation themselves what they can use from the Assembly code and what they can't. Some things in C# cannot be used from VB.NET and some can by using some tricks. Hope this helps somehwat.

    3. Re:The real difference between .NET and Java by Anonymous Coward · · Score: 0

      That's not FORTRAM, it's FORTRAN for FORmula TRANslation. It's not the matter.

      The matter is that although you can generate java bytecodes from any language, Sun doesn't actively market it as such.

      BTW, you don't need the original Java source code to execute code in the JVM, you just need the bytecodes.

      If your answer to this is "Java [the language] is the only language that fully uses the Java Virtual Machine" then, please, take some time to notice that C# is the only language that fully maps the CLR. VB# is being upgraded, eg, with short circuit evaluation operators, and C++ for .Net is being downgraded by dropping multiple class inheritance.

      All the rest is very good marketing/hype/etc.

    4. Re:The real difference between .NET and Java by Anonymous Coward · · Score: 0

      What's FORTRAM??

    5. Re:The real difference between .NET and Java by Anonymous Coward · · Score: 0
      Everything gets compiled into IL Assembly. This assembly language is the CLR supreme God

      So strickly speaking it's not really inheriting Cobol or what ever language. You're just using the library. The benefit is really reuse of old out-dated code and ease of using those libraries. That is an improvement over Java, since it's a pain to use Corba in Java. But that is hardly a spike in a vampire's heart.

      Until .NET is open sourced or made into a full public standard with full royalty free implementation and specification, you can count me out.

    6. Re:The real difference between .NET and Java by Anonymous Coward · · Score: 0

      What appeals to me is that I can write the front end in Object Cobol++ and
      the back end in C#. That's pretty darn useful, to my way of thinking.

  48. MIGUEL has lost his MIND! by Anonymous Coward · · Score: 0

    I think Miguel is crazy. He has totally lost it. The hell with .NET!

  49. DINGDINGDINGDING!!! by Anonymous Coward · · Score: 0

    Bingo!

    Here's a man that's learned from the history of the past decade: let Microsoft set a standard and they will:

    1) Change the API with every moon cycle to the point where only Microsoft can use it effectively
    2) Keep parts of the API hidden so only Microsoft can use it, thus giving them a leg-up over the competition.

    People, look at the past 10 years. Look at Microsoft's never-ending strategy of embrace, extend, obfuscate, and destroy. They're using the same damned tactics NOW, and yet everyone is ignoring this fact simply based upon the fact that Miguel d'Icaza has put his questionable imprimatur upon it.

    I don't care WHAT Miguel says. Talk to Borland. Talk to Watcom. Talk to any of the ghosts from Microsoft's conquests, you'll hear the same story over and over again. You ignore Microsoft's strategy at your own peril.

  50. Yes: What turnip truck did you fall off of? by GroundBounce · · Score: 2

    1. Mono is a separate project from GNOME

    2. KDE and QT are also developing bindings for MONO

    What are you going to do now? Switch to TWM?

  51. CLR is a superset of JVM by truth_revealed · · Score: 1

    Every JVM opcode has a .Net CLR equivalent opcode. However, not every CLR construct has an efficient JVM equivalent: unsigned types, auto (un)boxing, versioned assemblies, delegates, stack-based structs, and unmanaged code just to name a few. Any code written in Java can trivially be ported to C# (see Ant/Nant, JUnit/NUnit) but porting from C# to Java is more difficult if programmers take advantage of these extra CLR features - and most do because they reduce coding time and complexity. Microsoft certainly knows how to play the game.

  52. I think that was something else... by sterno · · Score: 1

    I believe that what you are thinking of was the licensing they put around information they released related to SAMBA.

    --
    This sig has been temporarily disconnected or is no longer in service
  53. Why .NET is good for Linux by rseuhs · · Score: 4, Insightful
    Now, take a step back, cool off and take a deep breath.

    Look at .NET, what is it? Basically it's just another API (plus some other enhancements, but I told you to take a step back and look at the bigger picture.) like the Win32 API

    Microsoft wants to fuel upgrades just like the transition from Win16 to Win32 fueled upgrades.

    The worst case in a Linux-point-of-view is that everything stays the same - Windows-apps don't run under Linux.

    The best case is that .NET apps run under Mono/Linux right from the start.

    .NET could be the biggest blunder of Microsoft's history, taking away the only advantage they really got (a huge software library).

    1. Re:Why .NET is good for Linux by GigsVT · · Score: 1

      Do you really think they won't break things if they are the epicenter of the actual development efforts? There really hasn't been one example of MS implementing a standard and not breaking it in some way so that is "works best with Windows(tm)".

      --
      I've had enough abrasive sigs. Kittens are cute and fuzzy.
    2. Re:Why .NET is good for Linux by Anonymous Coward · · Score: 0

      you go by opinion and state no facts. tell me, what standards have MS implemented? you make it sound like you know everything that they have implemented. i know one thing, though, your ass is on goatse.cx. go away, you keep arguing for the sake of arguing, like a half baked lawyer with nothing else to do.

  54. SMB is not M$ by prestomation · · Score: 1

    As far as I can tell from this site, Microsoft DID NOT create SMB. IBM did. They were the first ones to really use it, but they didn't actually create it.

  55. Great. by mindstrm · · Score: 1, Redundant

    So that means we can run Office.NET and, presumably, every other MS application that is built to .NET standards?

    If not, what's the big deal?

    1. Re:Great. by mindstrm · · Score: 2

      Okay

      But that's as long as they don't use any native methods, right?

      So I can write something that will run on multiple platforms.. you mean like java does now?

    2. Re:Great. by mindstrm · · Score: 1

      Yes.
      And you can be sure most of those will have some definite use of native methods or something that will tie them inherently to microsoft's platform.

  56. hmmm... by r0b0t+b0y · · Score: 2, Funny

    from the Ximian web site:

    * The Mono C# compiler was able to compile itself on December
    28th, 2002. The resulting image contained errors though.

    i'd say it was a good guess that they have errors with announcements like that...

    --


    ----
    i do not use drugs, i AM drugs -- Dali
  57. Making the interviewers' point by einhverfr · · Score: 5, Interesting

    About some people using a technology out of religion rather than merit.

    This interview is a very interesting interview in part because it seems to indicate that Mono is a good way of getting Windows developers into Open Source software development-- something that Microsoft has generally been pretty successful at preventing. I have generally likes what I have seen in .NET but I tend to see it as an exit strategy from the OS market (in a world where the OS market is saturating in the key markets in the developed world). This is a real reason that open source, being more flexible in its development pace (and giving customers what they need through community effort rather than centralized marketing). So, I wish Mono the best.

    --

    LedgerSMB: Open source Accounting/ERP
    1. Re:Making the interviewers' point by alext · · Score: 2

      Huh? Windows developers by definition target Windows - no VS user is going to install Red Hat just for the hell of it.

      Mono allows Windows developers to embrace and extend Open Source written in C Sharp, traffic the other way is impeded by the fact that so many essential APIs in Dotnet are proprietary.

  58. Just Wondering by teetam · · Score: 1
    Will there be a JVM to CLR (or vice versa) translator?

    Is someone already working on something like this?

    --
    All your favorite sites in one place!
    1. Re:Just Wondering by miguel · · Score: 4, Informative

      We are not planning ourselves on writing one, but several people have expressed their interest on doing so.

      There is already a proof that this can be done (Microsoft's JUMP), but it is not fundamentally a hard problem either.

      There are three groups of people to my knowledge working on free software versions of such a tool.

      Miguel

  59. Re:Ximians business plan by Anonymous Coward · · Score: 0

    1. Give away GNOME for free
    2. Give away MONO for free
    3. ???
    4. Profit

  60. We're talking about the platform not the language by alext · · Score: 5, Interesting

    This doesn't really add up to much.

    Only about 120 classes of the 1200 in the Dotnet platform are standardized as part of the C Sharp language, so standardization offers little protection if your application uses a GUI (Windows Forms, Web Forms) or a database (ADO Dotnet). Not only are these libraries not standardized, they are likely to be protected by patents.

    Sun does not have the same room for manoeuvre as MS since the JCP has other powerful participants. In practice, there have been few ownership/legal issues in developing Open Source versions of the JVM - see the Kawa web site for a list of these. Their complaints revolve around issues such as access to the test suites - ultimately Sun just owns the Java name, not all the implementations.

  61. A very simple analogy. by Kaypro · · Score: 4, Insightful
    I've been a hard core Linux user for many years and do most of my development on Linux (usually GTK/Gnome) but I must admit that the whole .NET thing is quite impressive. I'm actually quite surprised by it. Microsoft has never been know to make huge leaps but .NET is a MAJOR one. It is similar to the leap Apple made when jumping to OSX from MacOS. OSX fixed many of the things wrong with MacOS and similarly .NET fixes almost all of the prior things wrong with not only web development, but development in general. I strongly urge Linux developers to push there pride aside and learn about one of the first true inovations coming from Redmond since the wheel mouse :-) Whether or not it is accepted is yet to be seen (though personally I think it will, especially with the MONO project developing so rapidly)

    Cheers!

    1. Re:A very simple analogy. by Anonymous Coward · · Score: 3, Interesting

      I second that whole heartedly. And holy crap, the Visual Studio.NET is one kickass IDE. You can do development in 4 different languages within one project, can call routines between languages, and the debugger can step through the different code like nobody's business! I'm pretty sure no IDE even comes close (although Netbeans is pretty cool).

    2. Re:A very simple analogy. by NotoriousQ · · Score: 4, Insightful

      Your analogy is a good one, but for the wrong reason. OS X is really good because Apple merged UNIX OS with their GUI, thus giving their previously full of crap os a nice boost.

      What MSFT did is they took java concepts and mirrored them, keeping only the IDE. The result is that previously sucky RAD dev languages (talking VB here) and actually making them perform decently, while their IDE keeps kicking ass.

      A true move for the better, but no real new innovation, just a new product.

      Few more points....

      .NET fixes almost all of the prior things wrong with not only web development, but development in general.

      I will have to disagree with you here though....Web development is not fixed..and ASP.NET is actually more clumsy than it was before. Sure it is easier for the newbies, but it does not allow easy flexibility...just look at all the newsgroups talking about trying to avoid or at least control rampant postbacks, the horrible performance of webcontrols, and actually doing anything clientside....

      Do not believe me? Just try adding a client side onclick event to the asp:button, and you will see what I mean

      And do not start on the webservices thing...the only thing that is is just transparent to the user soap calls....

      And what about the development in general....well there are two types of development....one where you write small apps that store some data, and you want to develop them fast, and two is where you write some seriously big software, where you want it to work fast and last. .NET is fine for the first one, I will take pure C for the second one

      Furthermore, it seems that no one is seeing the .NET shortcomings....

      First, the gui (win forms) is not generic, which means microsoft never planned, eventual transparent porting to other platforms gui. Everything is in the absolute positioning, and does not even have an option for the layout system like gtk/swing IIRC. Sure it makes it easier for the noobs, but, you have to have the layout, if you want your app to be fully platform / device independent. Second, there are too many windows quirks in the core libs....drive letters?, unc paths?...sure there had to be a way for a more flexible system...so that apps could be ported a bit easier.

      first true inovations coming from Redmond
      I would not consider this an innovation, just a remake of what java is/tries to be...And like java it has design bugs....just look at the ICollection sometimes returning DictionaryEntry, sometimes the actual value...damn it people...it is an interface it is supposed to have common behavior....i do not want to check every f***ing time what object the for each loop is returning. BLAH

      since the wheel mouse :-)

      probably not their innovation, but they did recognize it as useful...gotta give them credit for that. I still think that there are some double mouse designs that are more useful...but do not have much time to play with them...but think multi axis mice (hat buttons, jog dials, etc, think the left hand joistick for RTS)

      Whether or not it is accepted is yet to be seen (though personally I think it will, especially with the MONO project developing so rapidly)

      What are you talking about? .NET is quite accepted in the Microsoft shops since it beats the shit out of old VB. However I wonder if mono is going to be accepted. This would be a very good thing for one good reason. This would cause competition within the libs, and if mono is going to play the lets stick to the standards and only the standards game...it will force microsoft to play to the same standards or risk losing control, and suffer a split in the .NET world. I would think they would take option 1, which is a win for us developers.

      So I say yay for mono, and hope that one day I can do my job for the (unfortunately all Microsoft) company from my linux box at home, and not having to shell out for WIN and VS and fear the BSA.

      --
      badness 10000
  62. Bait and switch? by alext · · Score: 2

    They already have extended 'it', if we mean Dotnet rather than C Sharp. Fussing about the language is a red herring.

  63. java everywhere? by drxyzzy · · Score: 1
    I think Java has a good record for working everywhere consistantly.
    Except any of the BSDs.

    Never liked the performance and resource-consumption price of Java anyway, so no big deal.

  64. Rundown: why this GPL programmer didn't choose NET by afflatus_com · · Score: 5, Interesting

    Look at the toolsets, the final contenders I looked at for a cross-platform GUI toolkit were: .NET
    Trolltech Qt
    GTK
    Delphi/Kylix
    wxWindows .NET:
    -Poor history of MSW undocumented APIs.
    -Poor history of MSW trying to break other toolsets not blessed by the company.
    -Poor history of MSW once actually finishing a piece of software's features (eg Office) trying to find other ways to pinch money off people.
    -Poor history towards GPL software.

    Qt:
    -A strong contender: good documentation, tools.
    -Lost out because they say the Windows version requires a purchased copy of Visual C++ to do any compiling with it.
    -Emulates widgets instead of using native.

    GTK (1.2 back then, I can't comment on 2.0):
    -Very free.
    -A lot of component scattered libraries makes documentation difficult.
    -Sometimes higher level widgets don't exist: need to make them from scratch using the window primitives.
    -MSW port is a bit rough.

    Delphi/Kylix:
    -Easy to use, a company respected by me that makes good software.
    -No Mac available.
    -Proprietary, liable to not be maintained if company goes under.
    -Free version is nagware under Linux, I believe their documentation said.

    wxWindows:
    -Works out of the box, now.
    -A single project can be compiled for MSW, GTK, OSX and less commons like X11 embedded.
    -Good documentation, sample code, etc.
    -Core team is *very* accepting to new features and sharper code.
    -Native widgets always used, where they exist makes a proper look and feel for an application.
    -The open library in unencumbered by a company that needs to ship new versions of tools or the library.
    -Fast: native compiles so no runtimes needed.
    -The C++ is designed to by truly compatible with almost any compiler, toolset, not ones blessed by one certain company.
    -Well tested (10 years).
    -Tools and library are no cost, (or nagware). Free compilers exist on all supported platforms.

    wxWindows was the one that was selected, and now 10 months into the project, I am very satisfied with the results from that toolkit choice.

    --

    -----
    Cast a Cold Eye
    On Life, on Death
    Horseman, pass by
    --W.B. Yeats' gravestone
  65. Sorta.... by CarrionBird · · Score: 1
    In section 3.1(b) it says if you use the distributables (i.e runtimes or sample code), it cannot be OSS.

    In 3.1(a), it seems to say that you cannot use redistributables if your program will operate on a non-Windows platform.

    (a) If you are authorized and choose to redistribute Sample Code, Redistributable Code, VC Redistributables, or Limited Use Redistributable Code (collectively, the "Redistributables") as described in Section 2, you agree: (i) except as otherwise noted in Section 2.1 (Sample Code), to distribute the Redistributables only in object code form and in conjunction with and as a part of a software application product developed by you that adds significant and primary functionality to the Redistributables ("Licensed Product"); (ii) that the Redistributables only operate in conjunction with Microsoft Windows platforms; (iii) not to use Microsoft's name, logo, or trademarks to market the Licensed Product; (iv) to display your own valid copyright notice which shall be sufficient to protect Microsoft's copyright in the Product; (v) not to remove or obscure any copyright, trademark or patent notices that appear on the Product as delivered to you; (vi) to indemnify, hold harmless, and defend Microsoft from and against any claims or lawsuits, including attorney's fees, that arise or result from the use or distribution of the Licensed Product; (vii) otherwise comply with the terms of this EULA; and (h) agree that Microsoft reserves all rights not expressly granted.
    You also agree not to permit further distribution of the Redistributables by your end users except: (1) you may permit further redistribution of the Redistributables by your distributors to your end-user customers if your distributors only distribute the Redistributables in conjunction with, and as part of, the Licensed Product and you and your distributors comply with all other terms of this EULA; and (2) in the manner described in Section 3.2.
    (b) If you use the Redistributables, or the "Sample Code" or "Redistributable Code" portions of the SDK Software (as described in Section 4.2(b) (all of the foregoing referred to in this paragraph as the "Licensed Software"), then in addition to your compliance with the applicable distribution requirements described for the Licensed Software, the following also applies. Your license rights to the Licensed Software are conditioned upon your (i) not incorporating Identified Software into or combining Identified Software with the Licensed Software or a derivative work thereof; (ii) not distributing Identified Software in conjunction with the Licensed Software or a derivative work thereof; and (iii) not using Identified Software in the development of a derivative work of the Licensed Software. "Identified Software" means software which is licensed pursuant to terms that directly or indirectly (A) create, or purport to create, obligations for Microsoft with respect to the Licensed Software or derivative work thereof or (B) grant, or purport to grant, to any third party any rights or immunities under Microsoft's intellectual property or proprietary rights in the Licensed Software or derivative work thereof. Identified Software includes, without limitation, any software that requires as a condition of use, modification and/or distribution of such software that other software incorporated into, derived from or distributed with such software be (1) disclosed or distributed in source code form; (2) be licensed for the purpose of making derivative works; or (3) be redistributable at no charge.
    --
    Free Mac Mini Yeah, it's
    1. Re:Sorta.... by korielgraculus · · Score: 1

      But the whole point of Mono is that is doesn't contain any MS runtimes or sample code, that is why the big fuss about their implementation of C# being able to compile itself without using MS libraries.

    2. Re:Sorta.... by CarrionBird · · Score: 1
      In that case, it should be legal under the EULA. The above sections were all about preventing MS code from being "caught" in a OSS license. On the Windows side, to run a .net app you need the framework on the system. One could simply release thier software without distrubting the framework, and rely on users to DL it from MS. Since Mono seems to serve that purpose, there shouldn't be any problem.

      Hmmmmm, VB/C#/J# code running on Linux, wierd.

      --
      Free Mac Mini Yeah, it's
  66. WTF? by Anonymous Coward · · Score: 0

    If Linux didn't suck so god awful bad on the desktop maybe it would have some market share.

    Just fucking once I would like to see one of you dirty, filthy, LinSux lusers spend some time working on your broke ass OS instead of posting to /. about how much MS sucks.

    Worthless bastards ahoy!

  67. MOD UP! by alext · · Score: 1

    Worth at least one point, surely?

  68. But .NET runs on *all* platforms, right . . . .? by binford2k · · Score: 1
    from the Phonic homepage:
    With the Microsoft runtime

    Gtk# doesn't currently work on Windows as the Microsoft runtime is incompatible with Gtk+ libraries that aren't linked with MSVC's lib.exe tool. Tor Lillqvist's Gtk+ for Windows won't work.
  69. What color is your pacifier? Olive-Green? by Anonymous Coward · · Score: 0

    You sound much like a Microsoft hoar trying to improve .NET's acceptibility by moving into the Unix world and saying .NET's framework must be supported. .NET is YetAnotherProgrammingLanguageSystem.

    Programms writting in Java, JavaScript, Python, Perl, C, C++, and Unix Shell yield higher performance, more efficiency, and require little disk-space for their usage. .NET is the most inefficient system in the history of computing. MONO is .NET on Unix and shares the same disadvantages of Microsoft's .NET. The only goals .NET and MONO will accomplish are:

    1)split development resources from where development should be concentrated,

    2)obfuscate ethics for implemting ideas in applications,

    3)reduce application portability to platforms that are completly unable to support .NET and MONO due to the inherent instability that .NET and MONO poses,

    4)uphold a union of security-risk and virus-like software to inter-operate with little effort to induce a higher-payload of damage to any platform,

    5)reduce development efficiency,

    6)supports Microsoft's MONOpoly.

    In my experience as a a programmer, which my skills include extensive knowledge and deployment of applications written within openGL, Java, JavaScript, Perl, Python, HTML, C, C++, i386, Z80, Alpha PAL, and HPRisc, I have come to the conclusion based on the technical merits of the .NET and MONO to be the occurence of massive ammounts of speculation that any person could write applications using either the .NET and MONO project with verry little training, verry little skill, and verry little effort.

    Microsoft's marketing team (yes, every employee is realy a marketer), and the activists within the MONO project, have effectivly LIED to the programming world to invest time in learnet the .NET framework to deplot applications.

    What is worse than the .NET framwork? Nobody believes there is a difference between right and wrong; you are all no different than wild animals that enjoy rape, disease, and thievery in a god-less society.

  70. It's simple, use FreeBSD! by Anonymous Coward · · Score: 0

    MONO and .NET is trying to destroy our community, but I've got the cure! Switch to FreeBSD! We don't have that problem.

    1. Re:It's simple, use FreeBSD! by Omega1045 · · Score: 1

      You couldn't be more wrong: MSDN Article on the .NET framework on FreeBSD.

      --

      Great ideas often receive violent opposition from mediocre minds. - Albert Einstein

  71. Microsoft, are you there? by pmz · · Score: 1, Troll

    Why do I feel like many of the highly-moderated posts on this thread were written by people on Microsoft's payroll? Has Slashdot been highjacked?

    1. Re:Microsoft, are you there? by Anonymous Coward · · Score: 0

      It does seem like that.

    2. Re:Microsoft, are you there? by Chris+Johnson · · Score: 2
      "Why do I feel like many of the highly-moderated posts on this thread were written by people on Microsoft's payroll? Has Slashdot been highjacked?"

      (quoted, because the same kind of people seem to have at least one 'Troll' moderation on this guy- starting from 2 I can make it a bit more difficult for 'em to suppress this meme)

      Slashdot has not been hijacked. Slashdot is, and has always been, open to astroturfing just as it is to genuine feedback. Nothing is stopping anyone from astroturfing Slashdot: they can do it on company time for all _I_ care, and welcome to it. We know Microsoft has people do this: they've been caught doing it before. It's not even some evil plot from Bill Gates: the company culture so strongly reinforces that type of behavior that it's like a negative value system- what would seem bad to you (astroturfing, putting up fake positive posts professing to be not Microsoft PR but real users and fellow slashdotters) would be seen as totally good and loyal and clever and virtuous, within Microsoft.

      Besides, everybody knows Microsoft ARE geeks, so why wouldn't they be reading Slashdot?

      You just have to learn to identify when they are doing their thing, that's all. Just because someone is a geek, or smart, doesn't mean they are honest. Some of the MS slashdotters are very open about where they're from. Because, WITHIN Microsoft, that is not as good as laying down some astroturf to compete harder, some of the MS slashdotters are taking nicks and astroturfing their little hearts out, probably to show their bosses in hopes of looking more Microsoftish to the boss. This is just the way the world works.

      Get used to not believing everything you see, hear or read- even on Slashdot. ESPECIALLY on Slashdot. Half the time if you see a 'voice of reason', especially if it's pushing for things like leniency towards Microsoft, acceptance of non-YRO-friendly stuff and so on... it's probably a plant.

      Yes, Virginia, people on Microsoft's payroll and people of Microsoft's corporate culture ARE still permitted to post things to Slashdot. Even if it's propaganda. Even if it's flat-out lies.

      Welcome to freedom, hold on to your wallet :D

  72. I've always wondered ... by Bazouel · · Score: 1

    ... why in the nine hells is so difficult to elaborate a STANDARD library (or whatever you want to call it) that will :

    - define common packages and their functions/methods/properties
    - and then implements them according to platform/language specification ?

    As a very stupid example, take sorting/filter functions : is it so difficult to sit down and make all those common and boring tasks a no-brainer by defining a common function header for them, whatever the language is ? I know that depending on language, the header declaration will change, but hell, if at least the same arguments are in the same order and have the same effects, that would be heaven on Earth !

    When I design a new class/function, I always try to be as close as possible to standards I find in related works. My job would be SO much simplified if a standard function or even a data structure would be the same whatever we use as a development platform/language.

    For this, I applaud Microsoft for the .NET initiative, even if Microsoft products ares as far as standard as one could imagine (MFC ... sigh).

    --
    Intelligence shared is intelligence squared.
  73. Yes I would - maybe by joshsnow · · Score: 1

    For better or worse, .NET is seeing a huge take up. Any developers using VB, ASP or Visual C++ are likely to be migrating to the .NET framework on Windows platforms. For that reason, I'd like to see a full and free implementation of .NET on linux - especially the webservice APIS and the Windows.Forms namespace stuff.
    GTK# seems to exist in it's own namespace at present, which means that GUI apps written using c# on Linux won't work natively on .NET for Windows. If the Windows.Forms stuff is implemented as GTK widgets in MONO or whatever, then that level of compatability would be achieved.
    For the interested, the .NET framework is free(beer) for windows and there's a free(speech) alternative to VisualStudio shaping up already.

  74. Re:Rundown: why this GPL programmer didn't choose by nagora · · Score: 2
    Qt: -A strong contender: good documentation, tools.

    The documentation alone is enough for me!

    -Lost out because they say the Windows version requires a purchased copy of Visual C++ to do any compiling with it.

    Well, I don't really care that much about supporting a legacy OS but TrollTech claim that Borland works too. Haven't tried it myself.

    -Emulates widgets instead of using native.

    But this allows some control over the style (I don't believe in repeating MS's mistakes: a good UI is better than one that has familiar screw-ups like having shutdown under "Start").

    TWW

    --
    "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
  75. chicken.... egg..... chicken.... dah! by Transcendent · · Score: 2

    "While the C# compiler, itself written in C#..." ....umm.... wha.... uhh........ how the.......... ummmmmm.....

    1. Re:chicken.... egg..... chicken.... dah! by Anonymous Coward · · Score: 0

      You use other available tools to develop the initial "bootstrap" compiler, then write the new language in itself. Since Microsoft already had a C# compiler that Ximian could work with, it could write C# in itself for the get-go.

    2. Re:chicken.... egg..... chicken.... dah! by kma · · Score: 1

      What language do you think your C compiler is written in?

    3. Re:chicken.... egg..... chicken.... dah! by damiam · · Score: 1

      I believe it was originally compiled with Microsoft's C# compiler. It can now compile itself.

      --
      It's hard to be religious when certain people are never incinerated by bolts of lightning.
    4. Re:chicken.... egg..... chicken.... dah! by Transcendent · · Score: 1

      ummm... something written in a language that already had a compiler?

    5. Re:chicken.... egg..... chicken.... dah! by slim · · Score: 2
      I can't find anything on the Web right now that describes the compiler bootstrapping process, so I'll summarise here. When building a compiler it's nice to be able to say that there are no external influences that might cause it not to work (like, using someone else's compiler to compile your compiler) -- so you avoid doing so using a process like this:
      • Define your language
      • Define the smallest subset possible S[0] of your language, sufficient to write a basic compiler
      • Implement compiler for S[0] in hand crafted machine code
      • Implement compiler for S[0] in your language
      • Compile compiler for S[0]
      • n=1
      • while(you haven't implemented the whole language)
        • Define larger subset S[n]
        • Implement compiler for S[n] using only language features supported in S[n-1]
        • Compile
        • n++
      • end while
    6. Re:chicken.... egg..... chicken.... dah! by Anonymous Coward · · Score: 0

      The first C compiler was written in Assembly language.

  76. SWT is not more advanced. by Steveftoth · · Score: 1

    If you think that SWT is more advanced then the AWT, think again. The SWT is far far behind the AWT in what it can do and where it will run. The difference is that SWT has a faster design, and after another year of cooking, may be much better the AWT.
    I don't think that programming with SWT will ever be easier then with the AWT, thanks to the AWT's event system. AWT is almost like magic the way that it handles events, while with the SWT you have to run your own event loop. This is why I think that the SWT has a faster design, since it requires the programmer to do more. That and it is designed to use less memory, AWT has a way of not letting objects die.
    I think that they should be spending more time creating a superfast java with new graphics APIS. Since more people use Java and you won't get the stigma that goes with everything MS on Linux.

    1. Re:SWT is not more advanced. by Tralfamadorian · · Score: 1

      To clarify, I've never actually coded with SWT, but from what I understand, it implements more widgets than AWT. I was only refering to the widget availability, not how the toolkit works.

      I should have been more clear in my post.

  77. .NET Framework, Comments and FreeBSD by Omega1045 · · Score: 3, Insightful

    First, I would like to post a link to an MSDN article on Microsoft's attempt to build a .NET implementation on FreeBSD.

    Second, I am a C# and VB.NET programmer. I have really enjoyed using the new VS.NET, and love ASP.NET. The way it treats web pages with an event model is very, very cool. As I am also a PHP programmer, I consider ASP.NET, concept wise, a giant leap ahead of PHP. VS.NET runs a bit slow on my 400 MHz machine, but cruises along smoothly on my 1.6 GHz laptop. Plus, it handles much better than Sun's Forte, a comparable product that would let me build comparable software solutions.

    Third, I am VERY excited to be made aware of MONO! I have done quite a bit of Java programming in my past, and am glad to have a better alternative to it for building enterprise level applications on Linux. I have not had the level of "undocumented features" bite me in my .NET programs as I have in VC++, VB6 or Java. Say what you will about the evil empire, but the .NET framework is a very well thought through, nice behaving programming platform. I wish the MONO team the best of luck, and am thinking of volunteering!

    Fourth (and finally) I have been teaching some VB.NET and C# classes. I have found all of my students walking away from the classes wanting to use .NET, including Linux programmers. I would tell you hardcore MS haters out there to at least try out .NET, especially if it is going to be implemented on Linux. I think you will find that it could be a great tool for you to build software with, if you take of the blinders. After all, why not take what is Microsoft's big marketing push and turn it against them on Linux?

    --

    Great ideas often receive violent opposition from mediocre minds. - Albert Einstein

    1. Re:.NET Framework, Comments and FreeBSD by FuzzyBad-Mofo · · Score: 1
      So you like how ASP.NET allows web pages to have an event model?

      How do you feel about the IE-centric code the server generates? How about the fact that you have to go back to the server for practically everything, especially if the user has a non-IE browser?

      Personally I prefer to have more granular control over the code that is generated, but I must admit that .NET allows more rapid development.

    2. Re:.NET Framework, Comments and FreeBSD by miguel · · Score: 2

      I am not aware of the IE-isms in ASP.NET, but maybe they are there.

      That being said, I would like the Mono version of ASP.NET to eventually use the SOAP functionality from JavaScript in IE and Mozilla to avoid reloading the entire page whenever possible (only some controls allow this).

      Also, you could make things different if you contribute to the ASP.NET effort in Mono, we are rendering quite a few pages already.

      Miguel

    3. Re:.NET Framework, Comments and FreeBSD by Omega1045 · · Score: 1

      As far as the ASP.NET framework goes, I have learned the good, bad and ugly. If you don't use server side controls for most things, you actually determine that vast portion of the code going out to the browser. Also, you can leave ASP.NET in flow-layout mode and at HTML3.2, which seems to work fairly well with Nutscrape. With traditional ASP, I have to learn to NEVER use session and application objects. I am learning some similar idiosyncrasies exist in ASP.NET. The most annoying thing in using ASP.NET, VB.NET, C# or ADO.NET, is having to say ".NET" all of the f@#%ing time (sorry goes out to all cartoons out there for the curse). I am now just calling the technoliges "VB 7", etc. C# is a cool little name, though.

      --

      Great ideas often receive violent opposition from mediocre minds. - Albert Einstein

    4. Re:.NET Framework, Comments and FreeBSD by Chris+Johnson · · Score: 2
      Patents?

      Or are you saying you can be certain they do not have submarine patents they can use against that situation, despite years of evidence that MS does appraise threats, and despite the fact MS is well stocked with crazed piranha lawyers?

  78. wah! by s4m7 · · Score: 1

    Everyone knows Miguel has become a Micro$oft shill.

    But seriously, MS stands to gain a lot from MONO's efforts. They are not a "server os" company, and why should they be? would you rather have 100,000 clients, or millions?

    People who use Unices on their backend will still be able to host .NET apps, but the apps will still only work with MS clients. This is exactly what they want.

    --
    This comment is fully compliant with RFC 527.
    1. Re:wah! by s4m7 · · Score: 1

      missing my point. look at the state of the linux browser, sure, they're good for the most part, and totally compliant with open standards. but the web works on closed ms standards. that's why they will never get the market share that IE has. the same will happen with .NET, and if you don't believe me, just sit back and watch.

      --
      This comment is fully compliant with RFC 527.
    2. Re:wah! by s4m7 · · Score: 1

      The only reason that some (a select few Sites) are IE only is that IE has the large market share.

      No. there are other reasons. take MS developer support for one, and MS's penchant for adding "features" requested by every jackass web developer out there.

      As NS/Mozilla pick up users, sites will once again have incentive to create nice standards compliant sites. Its already happening.

      Really? because i thought that what was happening was that developers were playing catch-up with MS which is a losing battle, and that NS/moz/opera users were crying for their favorite sites to not depend on IE.

      I bet you if we come back in 1 yr, 2 yrs, 3yrs and 5 yrs we will see .NET defacto standard, we will see a good amount of cross platform programming by people/companies who never thought of it before, and both Windows and Linux will be going strong. Although i respect your optimisim, i can't say i share in it. once the public adopts an MS standard, MS "extends"(read 'breaks') it. ever try running old VB code with new VB runtime dll's?

      --
      This comment is fully compliant with RFC 527.
  79. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  80. Micro$oft infiltrator on Slashdot by Anonymous Coward · · Score: 0

    Wow! Great marketing speech! You work for Micro$oft, right? It seems so.

    1. Re:Micro$oft infiltrator on Slashdot by Anonymous Coward · · Score: 0

      Yes, I'm sure MS has an army of workers that spend all day promoting MS products on slashdot and other sites that hate them.

    2. Re:Micro$oft infiltrator on Slashdot by Omega1045 · · Score: 1

      First, I would like to comment to the Anonymous Coward suggesting I am an MS infiltrator. That gave me a really good laugh! I should state that I program about 80% of my stuff for Windows 2000 servers. That is just where my career has led me. Second, I think that open minded and intelligent people would hope that MS employees would hang out at Slashdot. Perhaps intelligent and well thought out comments might have an impact on those you would consider your enemies.

      --

      Great ideas often receive violent opposition from mediocre minds. - Albert Einstein

    3. Re:Micro$oft infiltrator on Slashdot by Anonymous Coward · · Score: 0

      At least he works! 90% of the other comments in this forum have been nothing but childish, uneducated drivel! Including yours. I always figured that slashdot would some day grow up but I think it's actually going backwards and becoming more infantile every year. Thank you for contributing to that. Next time you have nothing to say. Don't say it!

  81. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  82. How many times do you NEED kicked in the balls? by nagora · · Score: 2
    .NET is a trap and MONO is walking straight into it.

    MS don't give a toss about the ECMA or any other standards body. They treat HTML as if they were the standards body (remember all of two days ago we had this story about the effect MS has on "standards" and that was one they didn't even invent!) they just want some stamp of approval that they're playing nice at the start of the game. After that the ECMA can pack up and go home, Bill won't be needing them anymore.

    MONO simply gives more credence to .NET by allowing MS to honestly (not that that's ever bothered them!) say that .NET is a cross-platform technology. Of course, they'll add, the non-Windows versions aren't very good. And they'll be telling the truth.

    The reason they'll be telling the truth is that they will make it their business to make it true. Every point upgrade (and there'll be lots of them) will come out just as MONO catches up with the changes since the one before last, making MONO a permanent 'old version' of .NET. And if the point update breaks old code or ignores the "standard" guess what? MS couldn't care less. Their customers will be locked in, they won't be able to change to MONO because it will be two points back and not able to do what the customers' software needs. So it'll be out with the chequebook again to add another wing to Bill mansion.

    I mean, for Christ's sake, it's not like Microsoft haven't done this all before! What are you people? BLIND???

    TWW

    --
    "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
    1. Re:How many times do you NEED kicked in the balls? by bolthole · · Score: 2
      What are you people? BLIND???

      "None so blind as they who wont see" [refuse to see]

    2. Re:How many times do you NEED kicked in the balls? by thirdrock · · Score: 1

      Strange, I don't remember anything interesting happening on the ninth of November.

      Actually, it was the 13th of November that the Indian Parliment was shot up by rebel gunmen.

      --
      >>
      I am the director, and this is my movie ...
    3. Re:How many times do you NEED kicked in the balls? by Anonymous Coward · · Score: 0

      Microsoft helps companies make MONEY with their product..open source is only interested in promoting the self interest of the developers. This is a capitalist society, get used to it. Make lot of money like gates and you can push any thing you want but before than stop whinning

    4. Re:How many times do you NEED kicked in the balls? by nagora · · Score: 2
      Microsoft helps companies make MONEY with their product.

      No, Microsoft helps companies make Microsoft money. If the companies manage to make some too that's just their good luck. If they manage to make a lot of money then Microsoft will copy their product, give it away for "free" and it's hello bankruptcy for the poor sod that thought Bill was his friend.

      Microsoft is not a capitalist company, it is an oligarchic/plutocratic one; it regards the area of software as belonging to it alone and mearly suffers the little people to make money so long as it is not inconvenienced. This is not surprising when you look at Gate's background: he's never had to work a day in his life if he didn't want to, from the day he was born into a million dollar trust fund from Grandpa he's been surrounded by the privileged stratophere of American aristocracy and it's clear that he'll do anything, including breaking the law, to defend that privilege from threats from the lower classes.

      In a capitalist society MS would be broken up by the government to preserve the balance of the market - the only legitimate role for a government in the capatalist model - to allow the maximum number of companies to compete.

      TWW

      --
      "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"
  83. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  84. Comment removed by account_deleted · · Score: 1, Troll

    Comment removed based on user account deletion

  85. Mono bad news for Liberty Alliance? by MtViewGuy · · Score: 2

    I think Ximian's Mono project may do something unintentially pro-Microsoft: it could turn the entire Microsoft .NET initiative into a de facto standard before Sun figures out what hit them.

    In fact, why do you think Microsoft has actually not stood in the way of Mono? Because Mono validates much of what .NET is trying to achieve. Between Microsoft implementing .NET Framework with its own tools and Ximian implementing .NET Framework with Open Source tools, Sun has its work seriously cut out to convince the majority of developers to write code for the competing Liberty Alliance (as if Sun's wishy-washy attitude towards the Linux crowd in regards to Java hasn't offended a lot of Linux/FreeBSD/OpenBSD programmers already).

    1. Re:Mono bad news for Liberty Alliance? by oPless · · Score: 2
      I think Ximian's Mono project may do something unintentially pro-Microsoft: it could turn the entire Microsoft .NET initiative into a de facto standard before Sun figures out what hit them.

      I don't think you know what "de facto standard" means.

    2. Re:Mono bad news for Liberty Alliance? by kyras · · Score: 1

      I think Ximian's Mono project may do something unintentially pro-Microsoft: it could turn the entire Microsoft .NET initiative into a de facto standard before Sun figures out what hit them.

      I don't think you know what "de facto standard" [webopedia.com] means.


      Actually, I don't think you understand the handy definition to which you linked. He was trying to say that by supporting .NET with Mono, this will encourage industry adoption of .NET thereby making it a de facto standard, as opposed to a de jure standard which would be mandated by a standards body/organization.

      --
      Tastes like burning! - Ralph Wiggum
    3. Re:Mono bad news for Liberty Alliance? by Anonymous Coward · · Score: 0
      Hi. I'm Wilford Brimley, and I've had diabetes for about 20 years. I stay active and I feel pretty good most of the time. See, I do things differently now. I'm not perfect, but I try to watch my diet and exercise. And I check my blood sugar, and I get all my diabetic testing supplies from Liberty Medical.

      Like I said, I'm not perfect. I guess.. some of the things I told you just now are downright fibs. Like the diet and exercise thing. When I said I watch my diet, I guess I mean I watch the minivan from Buddy's Barbecue pull up and unload about $200 worth of pork ribs onto my driveway while I stand in the doorway hiding my food boulder in my Bermuda shorts.

      When it comes to exercise, well that's just a boldfaced lie. I've never moved fast enough to sweat, except when I was making a baby. Even then, I took some much-needed breaks. My doctor isn't even sure I've got diabetes. He just says I look like somebody who would have it. I do check my blood-sugar every day, though, just in case. And Liberty Medical brings all the testing supplies right to my door, so it's easy to track my health.

      [ sprays whipped cream into his mouth ]

      Who am I kidding? That's bull hockey! I don't keep track of my health at all! People just assume I eat a lot of Quaker Oats, so I must be okay. Hell, I wouldn't eat oatmeal if it was the filling in a Dove bar. I can't stand that gobbledly gook! It always seems like somebody else ate it first. Sorry, Quaker, but I'm Wilford Brimley, I say it how I feel it.

      You know what I do like, are them S'Mores. And old-fashioned wedding cake frosting - the kind that's still got lard in it. And meringue made out of egg yolks instead of egg whites. Some people call it cholesterol, I just call it good.

      If you have diabetes, you check your blood sugar, and you check it often. There's no reason not to. Call Liberty. They can help you have a better life.

      Now, I'm gonna go get off my horse by getting onto a smaller horse, and then onto a large dog, until I'm near enough to the ground to roll off.

      You take care now.

    4. Re:Mono bad news for Liberty Alliance? by oPless · · Score: 2

      depends what the original poster means with ".NET initiative" - I took it to mean "C# and CLR" which is of course what the original post was about. AFAIK de jure supercedes de facto ...

      Your comment is fair though :-)

  86. Embrace and extend by Anonymous Coward · · Score: 0

    Can OpenSource embrace and extend .NET?

    1. Re:Embrace and extend by miguel · · Score: 2

      Yes ;-)

      But we are planning on staying compatible with their class libraries and not make changes, for the sake of users, developers and customers.

      That being said, we also encourage people to create new technologies and new classes and innovative things in their own class libraries. For instance Vorbis# (mostly done by Mark) and Gtk# (mostly done by Mike and Rachel) are extensions that originated in the Mono world.

      You really want your new classes/assemblies to work on both Windows and Unix, because that gives you a larger user base.

      Miguel

  87. Re:We're talking about the platform not the langua by dglo · · Score: 1

    Sun does not have the same room for manoeuvre as MS since the JCP has other powerful participants. In practice, there have been few ownership/legal issues in developing Open Source versions of the JVM - see the Kawa web site for a list of these. Their complaints revolve around issues such as access to the test suites - ultimately Sun just owns the Java name, not all the implementations.

    The Apache Foundation is working on freeing up access to the test suites, according to this press release

  88. tow tow tow the line... by Anonymous Coward · · Score: 0

    well, I guess thats another way of saying they made something so good and innovative you would be an idiot not to use it; since I dont have the *nix party line to tow, I can just call a cigar a cigar.

  89. The one strength of .NET by FuzzyBad-Mofo · · Score: 1
    In Wrox's Professional ASP.NET I saw the following statement (paraphrased):

    Even though .NET does not reach the performance of compiled languages, it does excel in some areas, for example memory allocation.

    In other words, it's a typical Microsoft product.. :)
    1. Re:The one strength of .NET by The+Bungi · · Score: 1
      In other words, it's a typical Microsoft product.. :)

      HAHAHAHAHAHAHA! You so funny! HAHAHAHAHAHAHA! You so original! You make me laugh! HAHAHAHAHAHAHAHA! You funny man! I like you jokes! HAHAHAHAHAHAHA! Wow...my sides are hurting with that funny, funny quip you just threw down on us like some clever maniacal funny man! You so funny! HAHAHAHAHAHAHAHAHA! Someone will even probably mod you up as funny to show how funny you really are to the rest of us! Quip, quip says you! Everyone! Over here! Look at the funny man! He made a funny about memory allocation! Get it...memory...allocation...HAHAHAHAHA! It's a reference to Microsoft products...yes, and the way they consume memory...HAHAHAHAHA! Yes, I am not sure where this guy is from but boy is he funny! Who invited him to the party? We gotta have this guy over more often! Honey? Come down here a second and listen to this guy 'tell it like it is' in a really funny way. HAHAHAHAHAHAHAH! Paraphrased from a Wrox book, that's priceless. "It's a typical Microsoft product." Gold. Just pure gold. And the smiley at the end? How did you come up with *that*!? How do you do it? I mean, so many people post on Slashdot but then you see a funny gem like this. HAHAHAHAHAHAHA! Pure hilarity. When's the last time you actually studied the CLR managed heap and so wittily remarked about it? Had you understood how .Net allocates, manages and frees memory then this wouldn't apply and hence your joke would 'have no teeth' as it were. But the brilliance of you tying in .NET memory allocation with other Microsoft products had me splitting my sides. HAHAHAHAHAHAHAHA! You funny man. So clever, so very very clever. I'll bet you were the funny man in high school too. Wow. You still got it!

  90. Comment removed by account_deleted · · Score: 3, Insightful

    Comment removed based on user account deletion

  91. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  92. Are you kidding? by AmateurCoder · · Score: 1

    The hardest part of learning a new framework is typically learning a new language. With .NET you can continue to code in C++.

    I disagree completly. Programmers who are well grounded in the basics of one language can usually pick up the syntax of another language quite quickly. Especially for someone like yourself who has already invested the time learn a rich language like C++.

    For example if you haven't done so already pick up a book on PHP and give yourself a weekend to sit in the sun and read.

    By lunch time on Sunday you will have had enough time to learn the basic data types of the language, how it handles arrays, building functions, file handling. . .etc . In other words you can easily learn all the syntax of the language in quite short order.

    But if you want to do something more interesting that reading and writing text files you are going to have to learn some new APIs and that is where the real time is spent.

    1. Re:Are you kidding? by Jason+Earl · · Score: 2

      Syntax is a cinch to learn, it's the new APIs that are a pain in the keister. In fact, that is one of the reasons that the Mono hackers are interested in .NET. They think that it would be cool to write modules in C# and use them in Perl, or write modules in Lisp and import them into Python.

      Personally I don't know if it will work better than the writing libraries in C and creating language interfaces, but it is possible that the Mono hackers are onto something.

  93. No to Linux by Anonymous Coward · · Score: 0

    Would you use an open-source implementation of the .NET Framework? Ximian's Mono project enables you to build .NET apps that run on Linux

    No way, I know better than that. I would use Unix however, in the form of FreeBSD, because it's a more stable higher performance cleaner written OS.

  94. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  95. Sounds like MSft by Anonymous Coward · · Score: 0

    from their site:

    "The Mono C# compiler was able to compile itself on December 28th, 2002."

    Is this a pre-announcement. :>

  96. This Mono crap will suck by johann909 · · Score: 0

    Remember, we have a team of five or six people led by Miguel the hack cracking this thing out, not distinguished engineer James Gosling and a team of hundreds. This thing will be a piece of shit, and I looked at the API Todo list, and they still haven't got shit. About 10% of the classes are complete. It is a waste of everyone's time for them to put this out, they should just stick to customizing desktop systems and writing buggy e-mail clients. This miguel freak doesn't know CRAP! hahah

  97. Ahhhh.... disapearing System.Eventhandler by Anonymous Coward · · Score: 0

    Visual Studio.NET/Asp.NET bite:
    1. The IDE often removes eventhandlers generated by the IDE. I just code them up in the code behind the page now so that VS.NET doesn't break my app.

    2. The delegate/eventhandler system makes messy code. Compare to anonymous inner classes in java.

    3. Try to create a new a new xslt document in visual studio. The namespace is instead of . Nice standard compliance.

    4. int is a value type object. The is/as operators don't like value types. This makes for interesting methods that take System.Object as a parameter.

    5. Why is it a WebForms page when it can only contain one html form object?

  98. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  99. Re:But .NET runs on *all* platforms, right . . . . by wadetemp · · Score: 2

    Actually, no audio player at this time can be cross platform in .NET, because even MS's FCL doesn't include facilities for sound playback. You have to make system calls directly of the system's APIs, which obviously differ from platform to platform.

    I don't know what Phonic's using GTK for. I suspect it's even one step further removed from being a true .NET app... maybe the Ogg decoding's written in .NET, but the audio playback's definitely not and the UI may not be either?

  100. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  101. DotGNU source of general related information.. by 3seas · · Score: 2

    dotgnu is another effort to develope a .net clone under GPL and here is a FAQ

  102. One word... by NorthDude · · Score: 1

    Jython... Nothings stops you from porting a language to run on a java platform.

    --


    I'd rather be sailing...
  103. .NET and SunONE? by SynthKing · · Score: 1

    Microsoft is pushing .NET and Sun has SunOne No, Sun has J2EE. SunONE is the crappy app server which used to be called iPlanet.

  104. More information ECMA links by 3seas · · Score: 2

    About the CLI - common language Infrastructure and part 2 of CLI information

    To really understand what is going on here, consider the CTS - Common Type System and the CIL - Common Intermediate Language as a midway translation point for any programming language.

    With this other programing languages or other programming mehodology interfaces can more easily be created.

    It's like taking all popular programming languages and putting them into a pot and boiling them down to common and non-conflicting data types and programming concepts. And from here, using the summed vocabulary set of data types and concepts as a translation base to use in converting a program written in your convient programming language choice into CIL or Common Intermediate Language bytecode. From which you can run on any systemj that has a VES or Virtual Execution System type of system installed.

    This of course allows both intrepreted and compiled types of languages to potentially be used.

  105. But this is MS' favorite game! by Jugalator · · Score: 2

    Chasing others technologies and implementing their own successful variants are one of MS' specialities. First, they catch up, then they use their huge influence to make it the new standard. Doesn't need to be better or even on par with the technology they've chased, either.

    I guess that's partly what MS has been in trial for. Often, MS can be seen as hurting the evolution of software for their own profit.

    --
    Beware: In C++, your friends can see your privates!
  106. Re:You've got your wires crossed... by Bamafan77 · · Score: 1

    You're confusing the platform independence of Java (write once, run anywhere) with the platform independence of .NET ( which is more like write once in any language, call anywhere in any language). This is a result of people not really understanding what .NET is. Even in Java, if you were to call MFC components, you'd lose portability. Same things go for application written with GTK, Motiff, or whatever.

  107. Yes, they can change that by Anonymous Coward · · Score: 0

    Look up the word p-a-t-e-n-t.

    Then read the Halloween memos.

    What? You really think that Microsoft would stoop so low? Of course they won't - until they think that they have enough people locked in to make for a really nasty FUD demonstration of the problems of trusting open source implementations.

  108. Doesn't this remind you of��� by The+Faywood+Assassin · · Score: 1

    that quote from "Porky's"? "Right now he's just playing with you, but one of these times he's going to get tired of you©©© and he's going to hurt you©"

    --

    "I'm a humble person really,

    I'm actually much greater than I think I am"

  109. Re:NEED PR0N! by Anonymous Coward · · Score: 0

    Horny Smurf, glad to lend a hand, [or cock for all you ladies out there :)]

    I am a 50 yrs old housewife. I have a23 yrs old nephew who has just graduated and was preparing to start a career. One day he came to visit me. My husband was away so I asked him to spend the night in my place. I have a habit of sleeping while watching TV so he kept watching it while I went into deep sleep. As he told me later, my dress went up so he was able to see my voluptuous thighs. My underpants shifted so he was able to see the slit of my cunt. This made his cock hard and he could not control himself any longer so he took his shirt off, took his cock out, went to me and in one push plunged it in my cunt and pumped hard. I took few seconds before realizing what was being done to me. I resisted, saying "No you should not do that" but this excited him further so he held me down kissing my lips and neck, sucking my ear, telling me how sexy I was while fucking me like wild animal. My resistance subsided and I let him have his way with me till he exploded in a powerful orgasm. I tried to push him off me saying that he should not have done what he did. Some tears ran down my face. He held me tightly telling me that he loved me, and that I am so sexy that he could not control himself. He begged me to forgive him. He kept kissing my lips, neck and sucking my ear. This pleased me and I told him that my husband has lost interest in me years ago.
    Then I asked did he really think I am sexy and he said yes kissing me passionately. Then he turned me around; my tears have been replaced by a little smile so he kissed me again inserting his tongue into my mouth. I moaned so he took off my clothes till I became naked. I did not resist so he kissed me again guiding my hand to his cock, which I milked to hardness, while he fingered my cunt. When he became ready he inserted his cock again into my cunt and began long deep strokes, which eventually turned into quick thrusts. I orgasmed which was my first since quite a long time. He continued pounding my cunt till he filled me with cum.
    He went to the bathroom, washed his cock then came back to me. I did not even try to cover myself so he offered me his cock to suck. I hesitated a bit since I have never sucked a cock but with a little encouragement I put it in my mouth sucking its head while rubbing it. That was enough to get him going again so he turned me around filling my cunt with his cock while playing with my clit using one hand while the other hand played my her tits. This combined assault made me moan with pleasure and after few minutes we both came noisily. He turned me again to my back and went onto my clit like a hungry animal holding both my hands so that I could not move away. I moaned loudly begging him to stop which he did not since I was grinding my cunt at his face enjoying what he was doing. Few minutes of suck made me erupt like a volcano. I was panting heavily begging him to stop but he had one more hole to fill so he turned me around "again", lubricated his cock with spit and went deep into my virgin ass. I was too exhausted to resist so he pumped hard till he filled my ass with cum. Then we went to sleep tired but satisfied.
    The next day I was in the kitchen preparing breakfast but he wanted me for desert first. As he approached me I said that we should not do it again and that it was wrong but he insisted on having his way with me. He held me tightly, kissing my lips and neck, sucking my ear and when I moaned he raised my dress squeezed my ass cheeks then pulled my underpants down. He went onto my clit sucking then as I rocked with his attack on my clit he brought a chair so I put my foot on it allowing him better access to my clit. Few minutes of sucking made me shudder in a powerful orgasm. He turned me to face away from him and made me put my foot on the chair, took his hard cock out and plunged into my cunt. As he fucked me I asked him to spare my ass for a while since it was hurting from last night initiation. This excited him further so he pumped faster and harder playing with my clit and twisting my nipples simultaneously till we reached our earth shattering orgasms. Afterwards he smiled and asked me for a breakfast then he picked up my underpants saying that they are not sexy and asked for scissors. I handed them to him and he turned my ordinary dull looking underpants into g-strings on both sides so when I put it on they hide almost nothing. Being a bit overweight they almost disappeared completely within my flesh which made him look at me with such lust I have never seen at anyone before. I begged him to wait till after breakfast so he left the kitchen. After preparing the breakfast I called him but he said we will have it on the floor in the living room. That was odd but I brought it to the living room. We sat facing each other. My dress rose up showing large part of my thighs. He looked at them with lust then pushed the dress further till he was able to see my almost naked shaved pussy. He could not hold himself any longer and asked me to back away a bit then he laid me and had me on the floor there and then. Afterwards we finished our breakfast and he went out promising that he will come for supper.
    I slept for a while then after waking up I adjusted my pants the way my lover wanted. As I was preparing supper my husband came. I told him that my nephew would come for supper and may spend the night. He did not comment. When my nephew came they gave each other the cold shoulder. But something came over my nephew and me. I felt that he wanted to assert himself as my man and, funny enough, I liked it and wanted to be his woman. He came to the kitchen, while my husband waited for supper, saying that he will give me a hand. Instead he held me firmly kissing me passionately feeling me up then inserting a finger in my aching ass. I whispered to him that my hobby was in the living room and that I have to prepare the meal so he let me go but kept feeling me up and whenever possible he rubbed his hard cock at my almost naked pussy. I prepared supper with his precum flowing down my thighs. After supper my husband went out and as he closed the door my nephew went on me like a wild animal putting my legs on his shoulders pushing his cock so deep I thought it might come out of my mouth. After few minutes of high quality fuck he came noisily then sucked my clit till I came all over his face. I spent the rest of the evening in his arms trading kisses and touching each other. When my husband came I went to sleep beside him while my nephew slept in the guest room. My husband slept soundly while I dozed for a while but woke a bit later when I felt a hand feeling me up. It was my nephew's. I got up quitely and my nephew took me to his room keeping his finger in my cunt. Once in his room he went on me wildely telling me that I am his woman and asking me to say it so I said to him I am yours do what you want. He put me on my hands and knees and fucked me like there is no tomorrow. After satisfying both our needs I went to sleep beside my snorting husband. My young lover left next morning but came back few days later saying he could not stay away from me which made me happy since I knew how much I wanted him to satisfy me. This night he suggested that I put a sleeping pill in my husband's drink for fun. I did, so after hobby went into his snorting symphony my lover came to me and we fuck while my husband was inches away from us which excited us further. After our first orgasm he told me to tease my sleeping husband (in contrast to the sleeping beauty) as we fuck describing what was being done to me. So I whispered to the sleeping non-beauty: oh husband my lover is pushing his cock in me, oh he is fucking me hard, come on save your wife, oh he has turned me on my hands and knees, oh he is rubbing my clit playing with my nipple while his cock is thrusting hard in me, cannot you stop him? oh I submit to him, oh we are coming.
    Few days have passed without seeing my young lover so I was worried and phoned him. He told me that he was busy applying for a loan but it seemed that the manager would refuse. Then he looked at me saying that the manager is known to have a week spot for women and that I may be able to help. I understood what he ment but surprisingly I obliged. It knew that I was willing to do almost anything to keep him. So on the day to meet the manager I had a shower, shaved my pussy, lubricated my ass, wore one of the panties that cover almost nothing then put on a light dress. When we met the manager he looked at me with lust. My lover summarized his application for the loan and when he sensed the manager's refusal he stood up, took me by the arm to the manager then told him my aunt was so concerned about this loan that she accompanied me despite her thigh was giving her great pain. As he said that he bent me over the desk, raised my dress exposing my thighs and most of my cunt to the manager. My lover asked the manager to see for himself and to feel the part giving me pain(which did not exist). The manager felt me up pushing his finger in my cunt then stood behind me, took his cock out and plunged it in me and pounded me with his thin stiff cock. I moaned my approval till he exploded in me. I took a tissue, cleaned myself up thinking that it was all over but my lover told the manager that I would like to suck his cock. I looked at him angerily but I knew I have to oblige so the manger sat on a couch and I knelt before him, took his cock out and sucked. My dress moved up exposing my bottom so my nephew took his cock out and filled up my cunt This made it easier for me to suck the manager's cock and after sprutting his cum over my face and chest he signed his approval of the loan.
    My lover has asked me to attend the opening party which consisted only of him and his three partners. After some drinks someone has played some music. My lover danced with me for a while then he put my hands around his neck while his hands went down my dress then pulled it up. I tried to stop him but he brought my hand back to his neck. He pushed both his hands under my dress then pulled it up a little exposing my ass and cunt to his partners. I knew they have were looking since the room became silent apart from the music. He pushed my underpants aside pushing a finger deep in my ass. I whisperd "No please do not" but he pushed it deeper bringing me closer to him . As he kissed me passionatley I felt a hand taking off my dress so here I was almost naked in front of four men. Within seconds I was on the floor riding the cock of one of the partners like a wild cowboy while another partner lubricated his cock and went into my ass in on go. Once the two fuckers adjusted their thrusts which relaxed me the third one offered his cock to me which I sucked hesitantly. Sucking was not my strong point. They took turns on me till we were all satisfied and exhausted. Afterwards my nephew told me that he made me one of the partners. I asked him what was my duty and he said to keep the partners satisfied.
    It is nice to offer my nephew a helping hand, cunt ,ass and mouth.

  110. Portability isn't everything. by Lab_rat0 · · Score: 1

    The great thing about .NET is that it is language independant.

    That is the big deal.

    You have your .NET Framework which is free (although not open source).
    The framework contains all the functions.
    Then languages C#, Perl, VBScript, Java etc are modules that fit ontop of the framework.

    If you have some functions written in Java, and there are some functions which do just what you need but are only written in Cobol, you can use them.

    You can have a single program written using 25+ languages (thats roughly the number of language modules for the framework last time I checked).

    You can learn the location of the functions once and the will be in the same place no matter which language you use.

    This means that no longer does it matter what language you choose.
    Because the language is no longer the important factor to writing an application.
    The only hassles you might encounter using other languages is comprehending the code contributed to your application by other programmers.

    Mono sounds great, as applications written using .NET will also be able to run on non-win32 platforms.

    This is a great achievement.
    The most impressive componet of .NET in my mind is the IDE.

    I would really like to see the features provided by Visual Studio .NET in an Open Source implementation.

    Lab_rat
    http://www.elitegeek.org/
    Join us, share your knowledge.

    --
    If we aren't meant to eat animals, then why are they made of meat?
    1. Re:Portability isn't everything. by Anonymous Coward · · Score: 0

      Umm, so all this .NET crap is just about some kind of abstraction layer? WTF is the big deal? No one ever thought of that before Microsoft? Amazing.

  111. You swallowed that crap, hook line and sinker? by Anonymous Coward · · Score: 3, Informative

    Suppose that I decided to use .NET on Windows. I look around, and find that they support Perl. Cool, so I go and use some Perl libraries in various places. Perl is as cross-platform as it gets, I am fine. Right?

    No. I am utterly fscked.

    Perl uses a dynamic programming model. .NET sucks goat d*ck on handling dynamic languages. Since Perl on .NET was too slow, even by .NET standards, its "integration" is through a custom modification that exports a COM interface, that is imported into .NET. Works fine on Windows. But on Linux, what then?

    And once people get going, how many real applications are going to use Windows forms, or link in some other library, or link in a COM interface from a legacy app, or otherwise become unportable?

    Care to guess whether future tools from Microsoft will "encourage" you to introduce such dependencies?

    Thanks, but no thanks. I have had to work with Microsoft APIs too much for my taste. That is why I try not to now.

  112. Rundown: So this was an emotional decision? by sheldon · · Score: 2, Insightful

    It appears that the reason you didn't choose .NET was based entirely on emotional, rather than technical reasons.

    Is this normally how you make decisions?

    1. Re:Rundown: So this was an emotional decision? by mandolin · · Score: 2
      Is this normally how you make decisions?

      Would you buy from a crook?

      The poster neglected to mention it, but .NET also appears to lose on the maturity, platform portability, and "required support tools" fronts. Particularly at the time the poster appears to have done the evaluation (GTK 1.2 era). Thus, there are plenty of technical reasons it might be considered lacking.

    2. Re:Rundown: So this was an emotional decision? by Elwood+P+Dowd · · Score: 2

      The real strange item was including .NET in a list of cross-platform gui toolkits. It's not. A cross-platform gui toolkit. Once Mono is done, then his complaints may or may not be valid. 'Till then, .NET isn't even close to being in the running. Right? All I know about .NET I learned from this interview.

      Aside from that, no. His reasoning is not emotional. It is possible that MS does *not* have such an ugly history, and MS is incredibly unlikely to sue Mono into oblivion. If this is the truth, then grandparent is just incorrect. He weighs certain facts differently than you do. Not emotional. There are intelligent people with both opinions. If he was correct, it doesn't matter whether he throws darts at a picture of BillG. It still would have been a bad business decision to go with .NET.

      --

      There are no trails. There are no trees out here.
    3. Re:Rundown: So this was an emotional decision? by Anonymous Coward · · Score: 0

      Emotional decision? Did you even read his post? Oh, you got me you troll.

    4. Re:Rundown: So this was an emotional decision? by arjennienhuis · · Score: 1

      If .NET isn't a GUI tookit, Delphi isn't either.

    5. Re:Rundown: So this was an emotional decision? by Anonymous Coward · · Score: 0

      If folks wouldn't let their emotions get in the way, we could throw all the
      Jews into the gas chambers, and then burn their corpses in the ovens.

    6. Re:Rundown: So this was an emotional decision? by Anonymous Coward · · Score: 0

      I assume that's just a troll. But it got +3 and no replies, so it's my duty as a true anonymous coward to belatedly point out the obvious.

      Sure the reasons given have emotional content, but they also have easily deduced practical consequences. We are looking for a cross-platform solution. In that context, the fact that MS has shown a tendancy to go out of its way to sabotage compatibility with other platforms is relevant to the future viability of .NET as a cross-platform solution.

      If .NET were given further consideration, it would still lose badly: it isn't yet anywhere near as easily portable as the chosen wxwindows.

    7. Re:Rundown: So this was an emotional decision? by Elwood+P+Dowd · · Score: 2

      It's a GUI toolkit, but that portion of the toolkit is exactly the part that isn't cross platform.

      --

      There are no trails. There are no trees out here.
  113. I use C#, ASP.NET and VS.NET at home! by sheldon · · Score: 2

    VS.NET is slower than frozen mud

    Buy a new machine. One that handles VS.NET well will set you back about $500.

    Give me a good text editor and command line tools any day.

    They are there, in all their glory. If you want to do everything by hand you can. Save yourself some money and just download the .Net SDK.

    Microsoft is going to integrate and complicate .NET with Windows to the point that Mono will never work.

    The point of Mono is not to be 100% cross-platform compatible. The purpose is to provide a similar development environment for Linux/Gnome. If you read Miguel's commentary what impresses him most about .Net is the problems they solved for developers.

    Now at a very base level, there is some compatibility. You have the same language syntax with C#, and it sounds like they are using the same IL assembly calls. But you are going to be missing many of the custom Windows libraries. But is that important? Wouldn't you expect custom libraries evolve for Linux specific features?

    MS will release new .NET crap every year and Mono will play catch up for a year so it finally works again just as MS is releasing a new incompatible version.

    Why is this important to you?

    In the past, Microsoft has either presented an "open" standard, or pushed someone else's open standard, only to hijack it in the end, to the detriment of non-Windows users and developers.

    But then so have non-Windows developers. Netscape, Sun, there are many examples. Even GNU is guilty of this, as I can no longer compile many open source programs with the tools that come with commercial unix because of extensions added to GNU make and GNU cc.

    I think the Open Source community would be better off backing a web technology like J2EE and not .NET.

    Why? J2EE is technically inferior to .NET, and Sun has certainly been less supportive to developers with their Java than Microsoft is being with .NET.

    I think Java has a good record for working everywhere consistantly.

    One of our foreign development shops just looked into running their web app they wrote with BEA's Weblogic on a different J2EE implementation. They can't do it without extensive recoding because each Java implementation contains custom stuff to differentiate themselves. In this case it had something to do with database connection caching, or something, which wasn't added by Sun in the J2EE specs but offers signifigant performance gains.

  114. Closed Source and Open Source by King+of+the+World · · Score: 1
    Traditionally, once a type of software becomes popular and then common there's an open-source version that eats the proprietary version.

    How closed-source keeps alive is by moving to new places so the open-source (and any competitor) is always playing catch-up. It doesn't matter if this is a good technology so long as they get the name out there, and their competitors can't claim to have 'X' feature.

    But you don't just add any feature. You choose something that makes the differences irrelevant.

    DOS has different characters for line-breaks than Unix, or Mac. Rather than standardising line-breaks the platforms move to XML.

    Software for Windows can't run on Linux or Mac. The operating system matters. Rather than making abstraction and platform-specific libraries they place a layer that makes the operating system irrelevant. Sun did it with Java, MS did it with .NET.

    It's all about placing layers ontop that makes quibbles irrelevant. I believe that's the plan.

  115. That's typical /. rhetoric for you... by Anonymous Coward · · Score: 0

    Windows NT on the Alpha was discontinued because Compaq but DEC and then pulled their support of Windows-on-Alpha. At one point DEC engineers worked on Microsoft's campus - Compaq removed 'em. Microsoft didn't have much choice after that.

    1. Re:That's typical /. rhetoric for you... by Anonymous Coward · · Score: 0

      So you're saying that if other people give up on a Microsoft product, then that doesn't count as a failure?

  116. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  117. what the hell is .net by Sabalon · · Score: 2

    I'm still trying to figure it out. At first I head all about using .net and web application service providers - kinda what CORBA or DCOM does - run this procedure over there and give me the results.

    It also sounds like you can write something in a language as long as it does nothing other than pure .net and run it on anyplace that supports .NET - much live Java does.

    So, is it basically Java with DCOM/RPC stuff built in using XML to pass data back and forth?

    1. Re:what the hell is .net by Anonymous Coward · · Score: 0

      Go read about it and you will figure it out. Not understanding it but giving us your high level overview anyway is a waste of time.

    2. Re:what the hell is .net by asobala · · Score: 1

      There are elemtns of .net that allow "Web services" to be written, but actually the main idea of .net is the same as Java. .net is a misnomer; the main idea of .net is to have a selection of languages (microsoft make C# and VB.NET) that compile into common machine-independant code (CLR). This is exactly like Java compiles to Java bytecode, but with .net multiple languages compile to the same CLR that can be run on any machine. .net is object orientated. There are ".net classes" which should be implemented to make any .net implementation usable; these include ASP.NET, ADO.NET, and Windows.Forms :-) When mono gets there, it should be able to run most CLR code. It is unlikely to ever be able to run code that interfaces with windows-specific technologies such as DirectX.

      The scary bit about .net is that C# appears to be in some respects an extremely advanced language. It treats XML data as objects and database information as objects. Combined with the language-independance, you can see how using .net is ideally suited for web services.

      I have barely used .net so there may be mistakes in the above.

    3. Re:what the hell is .net by Sabalon · · Score: 1

      Thanks for the info.

  118. +5 joke?!?! by Anonymous Coward · · Score: 0

    More like -1, Unfunny.

    We need a "-1, Wrong" moderation...

    1. Re:+5 joke?!?! by Anonymous Coward · · Score: 0
      More like -1, Unfunny.

      We need a "-1, Wrong" moderation...

      I take you are the aforementioned GF?

  119. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  120. I can hardly wait! by Eric+Damron · · Score: 3, Funny

    Yes! Give me .Net! I can hardly wait to run all of the windows apps including the lates viri!

    I really think that Linux is missing out on the fun. I mean sure, it's stable and secure but what adventure is there in that? I want to wonder every time I boot up if I'll see: "You have been hacked by the Windoz Nukum Worm! Hard drive formatting now...."!

    Oh yes! Why should Windows users have all of the fun?

    --
    The race isn't always to the swift... but that's the way to bet!
    1. Re:I can hardly wait! by Anonymous Coward · · Score: 0

      Well, too late - and its nothing to do with Microsoft, but the increasing popularity of Linux.

      Check out this article:
      http://news.com.com/2100-1001-943911.htm l?tag=cd_m h

      (summary: first 6 months of this year, there were 7600 successful linux hacks v 9400 on Windows. Windows hacks are falling, Linux is rising).

    2. Re:I can hardly wait! by Anonymous Coward · · Score: 0

      "Viri" is the Latin plural of "man". "Viruses" is the term you may be looking for.

      Shrimping dumbass.

  121. Just more lies from Miguel... by Anonymous Coward · · Score: 0

    He flat out lies. Every time he says something about Mono, he contradicts himself. In this article, he says, "our main interest is Windows Forms." But in several recent postings to the lists, he claims that Ximian have no interest in Windows.Forms because Microsoft is rumored to be abandoning it in favor of something better which is in developement now. He claims they will only use GTK# for development. If they do that, they have pretty much ruled out Windows users as targets for their products. This big mouth needs to get his shit together.

    1. Re:Just more lies from Miguel... by miguel · · Score: 2

      The interview was done long before I posted those messages to the mono-list. After the interview I looked at the problem in more depth, and focused on the current strategy.

      I fail to have my entire life planned in advance, so I have to make changes as I go, sorry if this annoys you ;-)

    2. Re:Just more lies from Miguel... by Anonymous Coward · · Score: 0

      Damn right it's annoying. Most of us have to look before we leap. People make choices. Corporations do. Small businesses do. Because you are a leader in the community, people, right or wrong, listen to you. If you say you will support Windows.Forms, people hear that and think that in the future, if they do their development using C# & .NET, they will be able to move to Linux. Now you say that it is not likely. Think before you speak. You, whether you like it or not, are a leader and need to take more care and use a little maturity in what you say. Your whims cost people money.

    3. Re:Just more lies from Miguel... by extrasolar · · Score: 2

      You make a good point but I believe Miguel deserves quite a bit of credit for all the work he has done and his optimism.

      In other words, give him a break. If you know someone specifically who has had this problem, let him speak for himself.

      Oh, and Miguel if you get around to reading this, thanks.

    4. Re:Just more lies from Miguel... by korielgraculus · · Score: 1

      Yep, absolutely true, and most of us manage to be wrong at least once in our lives (apart from yourself obviously). Miguel had a bad day, leave it at that, find something else to whine about (sure you can find it somewhere in the /. headlines) and let him get on with his project to which it doesn't sound like you have contributed.

    5. Re:Just more lies from Miguel... by Anonymous Coward · · Score: 0

      Um, you are wrong. I have contributed quite a lot to GNOME and general and a small amount to Mono. It's not about being wrong once in a while, it's about having some consistancy in his "public" vision. Yes, Miguel has done a lot. He deserves credit for that, but I have clients that specifically chose .NET over Java because of what Miguel has said in the past. That's my point. People listen to him and it costs them money.

    6. Re:Just more lies from Miguel... by korielgraculus · · Score: 1
      About being wrong, point proven, I heartily apologise ;)

      I agree in principle with what you are saying, but to my mind this illustrates a problem (NOT a weakness) with Open Source. It is unfortunate that Miguel stated that he may release a certain set of functionality, and the for whatever reason found out that he would not.

      Where the problem appears is in using a list of proposed features as the basis of a business decision. To be fair, it is not only Mono that suffers from this problem, many projects do (and not all Open Source).

      After one or two of these situations happening at work where I recommended Open Source software on the basis of "next release" only to find out that I was wrong, I was forced to take the position that I could and would, only rely on features contained within currently released code.

      I personally feel that this has a detrimental effect on the software, many of the coders employed within industry who may be able to contribute code as the basis of their work would be forced into released bug fixes for current code as that is what the customer would be taking at the end of the day, rather than attempting to add new features.

      Many small companies simply don't have the resource to add new features on the basis of "a customer may want it in the future" and so that job is left (in many cases) to individual coders who would add features on the basis of what they would like to see rather than on what is the most "commercial" product.

      At I said at the start of this (too long) response, I believe the best advice that can be given at the moment is to base decisions on the released code that is available, as there are no guarantees on what will or won't make it to the final version of any software.

    7. Re:Just more lies from Miguel... by Anonymous Coward · · Score: 0

      I agree. Choose based on released features. They chose based on the released features of .NET with the expectations that, as Miguel stated, Mono would be a near feature-for-feature duplication of .NET, including Windows.Forms. Now it is not, it is too late to go back to java for some. The issue though is much larger than Windows.Forms. If leaders like Miguel say things, they need to back them up. Think before you speak. He is not only a leader in the GNOME community, but the founder of both GNOME and Ximian. As a rep for Ximian, I would think he would need to have a little more corporate accountability. I like the fact that he is a visionary, but he needs to make sure that his visions are realistic and not ideas spouted that are not possible. :-)

    8. Re:Just more lies from Miguel... by croanon · · Score: 0

      I think first he should stop being a MONOpolist wannabee.

      --
      Dear Bill, do you have a .net tatoo on your ass for marketing?
  122. 100% Too expensive by spells · · Score: 1

    The problem is that reaching the final 5% of the market typically requires more than 5% additional work; so, all other things being equal, the return on your investment is lower for the company trying to attain 100% of the potential market. I would probably invest in the 95% company, but that's just me...

    1. Re:100% Too expensive by Anonymous Coward · · Score: 0

      Not to mention that if that extra 5% just happens to be the "software wants to be free" type of people, it's really a waste of money to target them anyway.

  123. .nyet by tstock · · Score: 1

    The talking paperclip was also supposed to change the way we do work in offices all around the world. Fool me once, shame on you, fool me twice, shame on me. Fool me 300 times, sink an industry, hurt an economy and what do we do ? We re-invent the Microsoft square wheel and call it MONO.

    . Surely they will not shift standards on us;
    . surely they will not hide APIs on their implementations;
    . surely they will not "extend" their product and introduce imcompatibilities;

    Yea, I see a future of no pain for adopters of MONO...

  124. That's a good point.... but... by Eric+Damron · · Score: 2

    ".NET could be the biggest blunder of Microsoft's history, taking away the only advantage they really got (a huge software library)."

    I use to think that way too but with Microsoft's DRM push how many .NET apps do you think will be allowed to run on "untrusted OSes?"

    So, like you said. At least we won't be any worse off then we already are... or are we overlooking something?

    --
    The race isn't always to the swift... but that's the way to bet!
  125. use your brain and think by Anonymous Coward · · Score: 0

    Netscape
    Javascript
    Kerberos
    Java
    OpenGL
    Pall adium

    And you still look at .Net?
    look the other way

    apache
    xml
    perl
    python
    zope
    sendmail
    linux
    xfree
    mozilla
    staroffice
    vim
    emacs

    isnt this much better?

  126. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  127. KDE DOESNT HAVE MONO by Anonymous Coward · · Score: 0

    ... i think you have kde confused with gnome

  128. Saruman would say: by Anonymous Coward · · Score: 0

    Fools! Don't you understand the secret to Microsoft's success? They dont' allow themselves to be successfully cloned, but when they clone something someone else invented, they eventually do it better. Take the lead and don't never back!

  129. Re:Rundown: Careful consideration, not emotion by afflatus_com · · Score: 3, Informative

    There is very little emotion in either my post or my decision.

    The question posed by the article was "Would you use an open-source implementation of the .NET Framework?"

    I listed the reasons why .NET was not taken as the platform of choice and the reasons were not technical. I think .NET will certainly be competent, as the technical lead was the guy behind Delphi.

    I am a GPL software author. C# is an unproven new language to assess in my choices. I am absolutely going to judge the likely future of a language by looking at the past history of the company who will be managing its development.

    Microsoft has quite openly stated that they think GPL is a virus, and there has been rumblings of making it illegal to use their development tools in the creation/conjunction of GPL software or libraries (which is their right to do).

    However, a major software project is a large commitment of time--porting to another language down the road is unlikely to be trivial. if Microsoft takes their familar road with C#, and my code becomes illegal to compile, or I now everyone who wants to work on the software now has to fork over $500 a year for a MS-blessed C# compiler to be able to contribute to the GPL project, I will have regretted my choice of .NET. The possibilty of that occurring moves .NET to the back of the pack as their counterparts can already do what I need without that extra weight looming over the project.

    But the results also matter. Here are some development snapshot screenshots, fresh off a clean compile on Linux and MSW, built with wxWindows with no MFCs, Microsoft dlls or anything else that can be made illegal or prohibitively expensive later on:

    http://www.clinicalexam.com/pluckerdesktop/tour

    --

    -----
    Cast a Cold Eye
    On Life, on Death
    Horseman, pass by
    --W.B. Yeats' gravestone
  130. Isn't that normally how people make decisions? by Inoshiro · · Score: 2

    If you don't feel right killing someone, you don't do it, do you?

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
  131. AWT is broken and will always be. by Steveftoth · · Score: 1

    The 'real' problem with AWT is that is was implemented too damn fast. I read that the AWT was originally implemented in about a month. Notice that they changed the event model from 1.0 to 1.1? Radical change, if you look at the old model. Basically the design is bad but you can't change it, you have to start over.

    Swing is great on paper, but only if you consider that it will never be fast. Since all you're stuff is drawn to a virtual screen and then to the real screen. This ensures true cross platform compatability,but again you lose any hope of speed.

    I agree that there should be some comprimise inbetween pure java and java with JNI extensions, as there should be a way to compile java ahead of time, and disregard the whole class loading and security features for an application that is precompiled. Maybe an open source project is needed, like gjc, but to the next level.

    Course I believe in making the wheel rounder and not reinventing it everytime the old one gives you a crappy ride.

    1. Re:AWT is broken and will always be. by oPless · · Score: 2

      I never said AWT wasn't broken. I said I preferred it to the bloat of swing.

      Since all you're stuff is drawn to a virtual screen
      You mean YOUR, what next? Spelling colour "color" ?!!! ;-)

      I'm still waiting for gjc to support mingw32 and sql, fantastic product in all other cercumstances though :)

      Course I believe in making the wheel rounder and not reinventing it everytime the old one gives you a crappy ride.
      Of course, but you know that the java virtual machine was designed over 10 years ago (when java was oak) is showing its age. JVM has some life in it yet, don't get me wrong ... It just might be time for a change ... maybe when mono is more mature I'll make a permament switch.

  132. Re:What color is your pacifier? Olive-Green? by Anonymous Coward · · Score: 0

    A resonably skillfull troll you are. Not

  133. Sad by Otis_INF · · Score: 2

    Looking at most of the postings here, allthough most of them are posted by non-developers and brainless collegekids, I can only think: what a sad bunch of people. .NET is one hell of a platform with a very well thought out API, documentation and complete functionality. Now there is this Linux developer and his team at Ximian who ports that platform to Linux and all the fools at /. are able to do is cry out what a crap .NET is, how Miquel is a slave of MS, oh sorry, M$, and that Mono will suck as .NET already does.

    *RRRRT*

    If Mono fails on Linux, Linux is dead. Be aware of that.

    --
    Never underestimate the relief of true separation of Religion and State.
    1. Re:Sad by GrassyKnowl · · Score: 1

      More FUD from the Microsoft crowd. We don't need not stinkin .net

    2. Re:Sad by PigleT · · Score: 2

      ".NET is one hell of a platform with a very well thought out API, documentation and complete functionality."

      In the real universe, it's M$loth's excuse to port the .exe PE file format to other platforms, with 2 reference implementations' sources available so they can get let off by the DoJ.

      There's also nothing new under the sun. Running other language environments ("hosting", my ass) has been done ever since emacs was written in lisp running on a C-based machine.
      .

      --
      ~Tim
      --
      .|` Clouds cross the black moonlight,
      Rushing on down to the circle of the turn
    3. Re:Sad by Diabolical · · Score: 2

      I can only agree with you about .NET being well thought out etc. However, it is the company behind it which causes the problems. And understandably so. MircroSoft has a history of shutting out competitors on the same market as they are in. Now tell me, would you like to be owned by MicroSoft? Every little piece of software coming from MicroSoft and locking you in to prevent you from switching platforms? Because that's what this is all about. If you have invested thousands of hours and dollars into a project you will most likely not switch the platform. Making you a milk cow for MicroSoft to pay even more dollars to them.

      Yes, it should be the best tool for the job. But think of future implications as well. When you create an enterprise wide application which is consisiting of thousands of lines of code. Would you be willing to rewrite them? Maybe someday MS will stop support for your version of the framework forcing you to buy a new, and more expensive one. Just to prevent you from switching platforms they make sure their code isn't portable. Which is pretty easy to do as their history of embrace and extend has shown allready. These implications should be considered as well before choosing a platform like this. If you don't mind coughing up all those dollars each year for MS related material while other (perhaps less thought out but functioning nevertheless) tools are easy to come by and cheap to boot then hey, it's your personal choice.

      Mono will by the way always be lagging behind as SAMBA does. A fact allready known by alot of developers. If you need the greatest and the latest of those implementations you better stick to MS. And just that is what most people resent.... having no choice (as waiting for the rest to play catchup isn't an option..)

      If Mono fails on Linux, Linux is dead. Be aware of that.

      Hmmm... where have i heard this one before...

      Linux won't die because of MONO not succeeding. It would have been dead allready if that's the case. MS wouldn't even think twice to sink the MONO effort if this would hold any thruth in it.

      There will always be an alternative which does support Linux. So stop pretending MS is the only player in the IT field.. their not, and never will be..

    4. Re:Sad by liloldme · · Score: 1
      If Mono fails on Linux, Linux is dead. Be aware of that.

      yeah right... what fucking planet do you live on?

      There's no need for .NET on Linux, .NET is a client side technology, Linux works best on the servers and free J2EE is available on the server side.

      Mono not needed here.

  134. Support Java and KDE by MiniChaz · · Score: 1

    Java is always going to be more portable than anything involving C# and .NET. Microsoft are not creating these technologies for the good of the community. While Sun may well not be in it for the good of the community either, their intentions seem less evil and they are pro Unix (and pro Linux to some extent).

    While I am a GNOME user at present I will be moving back to KDE when this stuff makes its way into GNOME proper. I imagine many people will do the same.

    1. Re:Support Java and KDE by Anonymous Coward · · Score: 0

      Why the hell would anyone want shitty bloatware like KDE or GNOME? FVWM2 ALL THE WAY!

  135. Microsoft always loses . . . then they cheat by Anonymous Coward · · Score: 0

    Microsoft is as inept as they come. Unfortunately, Microsoft's control of the OS, and their willingness to break the law, has allowed them to knock out their superior competitors.

    Let's look back...

    Microsoft was losing against DR-DOS. So Microsoft added a phony error message, and started a smear campaign to undermine people's trust in DR-DOS. They also added secret calls to Win95 to make it incompatible with DR-DOS.

    Microsoft was losing to Geoworks, until they made changes to DOS to cause Geoworks to break.

    Microsoft couldn't beat WordPerfect, so they supplied faulty API calls to make WordPerfect unreliable and slow, while using secret API calls in MS Word.

    Word and WordPerfect were fast losing marketshare to Ami Pro, until Microsoft changed the function-key API in Win95 to cause the best feature of Ami Pro to break.

    Microsoft couldn't beat Java, so they decided to break the law, and sabotage it, as well as committing fraud:

    http://java.sun.com/lawsuit/051498.unfair.html

    > the "strategic objective" is to "kill cross-platform Java by grow[ing] the polluted Java market."

    > "at this point its [sic] not good to create MORE noise around our win32 java classes. Instead we should just quietly grow j++ share and assume that people will take advantage of our classes without ever realizing they are building win32-only java apps."

    Microsoft's own people admitted that they couldn't beat Netscape:

    http://www.usdoj.gov/atr/cases/f3800/msjudgex.htm

    > "I don't understand how IE is going to win. The current path is simply to copy everything that Netscape does packaging and product wise. Let's [suppose] IE is as good as Navigator/Communicator. Who wins? The one with 80% market share."

    > "Pitting browser against browser is hard since Netscape has 80% marketshare and we have 20%. . . . I am convinced we have to use Windows -- this is the one thing they don't have. . . . We have to be competitive with features, but we need something more -- Windows integration. If you agree that Windows is a huge asset, then it follows quickly that we are not investing sufficiently in finding ways to tie IE and Windows together."

    So, Microsoft resorted to sabotaging the Netscape product, as well as interfering in Netscape's contracts, including what could be classed as extortion:

    > "We will bind the shell to the Internet Explorer, so that running any other browser is a jolting experience."

    > "Apple let us down on the browser by making Netscape the standard install." Gates then reported that he had already called Apple's CEO [Gil Amelio] to ask "how we should announce the cancellation of Mac Office...."

    > "Though the language of the agreement uses the word "encourage," I think that the spirit is that Apple should be using [IE] everywhere and if they don't do it, then we can use Office as a club."

    But Microsoft has a problem now, because direct sabotage only works against products that run on Windows, and some other forms of cheating only work when not under the watchful eye of the courts, or when people aren't watching out for them.

    Thus, much of Microsoft's recent propaganda has failed miserably.

    And Microsoft still hasn't managed to defeat Java, Unix, or now Linux. Even Netscape has managed to survive and is coming back for a rematch (this time backed by Linux, Sony Playstation, and a dozen other non-MS platforms).

    Microsoft may have to resort to competing.

    And Microsoft has never won a fair competition.

  136. Re:What color is your pacifier? Olive-Green? by Anonymous Coward · · Score: 0

    > The only goals .NET and MONO will accomplish are:

    Hmmm, messy. I think I'll split that up, so I can respond properly.

    > The only goals .NET will accomplish are:
    > 6)supports Microsoft's MONOpoly.

    Correct. Microsoft's intention is to use their current Windows monopoly to gain a new monopoly on the development of Internet applications and services.

    > The only goals MONO will accomplish are:
    > 6)supports Microsoft's MONOpoly.

    Wrong. In fact, the opposite is true. The existance of Mono -- an Open Source *alternative* to .Net -- is going to *prevent* Microsoft from gaining the new monopoly that they seek.

    Do you really think that the disappearance of Mono would slow down the progress of .Net, considering how Microsoft has been tying .Net into their OS, and all of their development tools? Have you seen the shelves of books on .Net development at the bookstore?

    Mono allows developers who use .Net to move their applications to a platform (i.e. Mono) that does not tie them to Windows, does not tie them to any Microsoft services or security protocols, and does not require any payments to Microsoft. Do you really think that's what Microsoft wants???

    Come on. Think it through.

  137. Depends... by grahamtriggs · · Score: 1

    Would I use an open source implementation of .Net? Well, if I want to host on Linux, then it is my only choice, so yes... But why would I want to use an open source version (particularly in it's current state of development) on Windows? I can download all the SDK etc from Microsoft for free - it's only the IDE that I would have to pay for, and there are free alternatives to that... For as long as I use Windows, and I can download a free cli-based SDK from MS, an open source version would have to offer compelling reasons (in terms of less bugs, fixing bug/security issues, performance) otherwise there is no point.

    1. Re:Depends... by GrassyKnowl · · Score: 1

      Would I use .net at all? Why should I? I can use Java/J2EE today and be portable across numerous platforms. J2EE is mature. I can do web services with it via the JAX-RPC API. J2EE is more secure than anyting that Microsoft has. I don't trust Microsoft and neither should the Linux and open source community. Why should we support .Net, a closed Microsoft proprietary architecture, proposed by a company known for its shady business dealings?

  138. Thanks for proving my point. by Otis_INF · · Score: 2


    In the real universe, it's M$loth's excuse to port the .exe PE file format to other platforms, with 2 reference implementations' sources available so they can get let off by the DoJ.

    What's 'M$loth' ? And what does the DoJ crap has to do with the quality of .NET? Nothing. Still you find it useful to flame the living crap out of it. Which was my point exactly.


    There's also nothing new under the sun. Running other language environments ("hosting", my ass) has been done ever since emacs was written in lisp running on a C-based machine.

    Fyi: Lisp is interpreted, C# and the other 20 or so languages for .NET are not.

    --
    Never underestimate the relief of true separation of Religion and State.
    1. Re:Thanks for proving my point. by PigleT · · Score: 1

      "Still you find it useful to flame the living crap out of it. Which was my point exactly."

      No, I just speak the truth. You obviously have a problem with looking at it out of anything other than billyg's ass.

      "Fyi: Lisp is interpreted, C# and the other 20 or so languages for .NET are not."

      No, they're mangled around into a Windoze executable and then interpreted. You know? Big Furry Deal(TM). My point remains, and you still suck up to Bill.

      --
      ~Tim
      --
      .|` Clouds cross the black moonlight,
      Rushing on down to the circle of the turn
    2. Re:Thanks for proving my point. by Anonymous Coward · · Score: 0

      Brainless College Kids did you say.....

      (he's read about the PE format though, give him something, though he's wrong about .net using it)

    3. Re:Thanks for proving my point. by LoonXTall · · Score: 2
      Fyi: Lisp is interpreted, C# and the other 20 or so languages for .NET are not.
      "20 or so other languages" are really just C# in syntactic disguise. For instance, they stripped multiple-inheritance from the .NET version of Eiffel, because .NET doesn't support it. But now that it's a ".NET version" it's no longer compatible with normal Eiffel, so it's not Eiffel anymore, ne?
      --

      ~~~LXT~~~
      Life is like a computer program: anything that can't happen, will.

  139. I also switched from Gnome to KDE because of Mono. by croanon · · Score: 0

    The first day I learned that Ximian is financing the .NET project, I and my 28 friends moved to KDE.

    --
    Dear Bill, do you have a .net tatoo on your ass for marketing?
  140. Miguel says GNOME 3 will support Mono, AND by croanon · · Score: 0

    GNOME 4 will be written with MONO's C#. Read his interviews at the register etc. I do not like .NET. Even it will help Linux for couple of things, I believe it will help more M$. Look how Miguel is talking about Microsoft etc on Mono site. He is being extremely careful to not to put a grain of dust on M$. This is not something I like. I will use my right to protest and will NEVER use any MONO supported software, or GNOME. If it becomes a big hit on Linux, ok, it is time to move to Free BSD. Its all. :)

    --
    Dear Bill, do you have a .net tatoo on your ass for marketing?
    1. Re:Miguel says GNOME 3 will support Mono, AND by hvatum · · Score: 0

      >If it becomes a big hit on Linux, ok, it is time to move to Free BSD Dont you think this would be the goal of MS? They love the BSD liscence and hate the GPL because they cannot take advantage of the GPL.

      --
      Netbooks, they come with Linux or a $3 copy of Windows. Either way, Microsoft loses.
    2. Re:Miguel says GNOME 3 will support Mono, AND by Anonymous Coward · · Score: 0
      Dear Bill, do you have a .net tatoo on your ass for marketing?

      The ".net" is right between the Windows 95 logo and the "Where do you want to go today".

      Ballmer tattoos my ass pretty regularly.

  141. And what standards do for C#? by croanon · · Score: 0

    Standards is nothing. Totally useless. AND, MS did not give important parts of the .NET to the ECMA. ALSO, Ximian is FINANCING MONO. Thus, there is no Ximian in my future life.
    Its all.

    --
    Dear Bill, do you have a .net tatoo on your ass for marketing?
  142. Standards my ass. Icaza is helping M$. by croanon · · Score: 0

    Every .NET implementation helps M$ more than it helps that platform. MONO is helping MONOpolist more than it is helping to M$. I will never use it.
    Icaza can keep licking Billy's balls. I definately won't.

    --
    Dear Bill, do you have a .net tatoo on your ass for marketing?
  143. tools by g4dget · · Score: 2
    It was the fact that they could write code faster and worry less about the crap that tipped the scales.

    I have yet to see a Microsoft tool (or any other tool) that lets me write code faster. Tools require time and effort to use. It's much better to just to get it right the first time.

  144. let me second that by g4dget · · Score: 2

    I also think wxWindows is by far the best cross platform C/C++ toolkit around right now: it's free for both non-commercial and commercial use, runs on lots of platforms, can use native widgets, is mature, and has tons of functionality. Many more open source projects should use it.

    1. Re:let me second that by TheAwfulTruth · · Score: 2

      I'll third that, (Well the best FREE one anyway) But that is actually a rather sad statement. After spending about a year coding with it, wxWindows is actually an abomination of a framwork. A patched and hacked set of code that makes MFC look clean and elegant. They stomp on all kinds of windows library keywords and windows is it's primary platform! It's not really a cross platform framework. It's a generic wrapper for native frameworks so it's full of funky cross platform parity issues. It's plenty useable. But it's not great, it's not even good. It's barely acceptable for small to med sized applications and that's the best it is. And it IS the best (free) there is as you pointed out!

      I hope MONO does succeed, though probably MOST of the .NET API is still unwritten or in the process of being written so it'll be a long way off before that can be tested for real. It remains to be seen if they gain actuall funtion parity or if writing to two platforms requires numerous #ifdef workarounds for differing behavior like all other cross platform frameworks do.

      --
      Contrary to popular belief, coding is not all free blow-jobs and beer. Those things cost MONEY!
  145. it's good, but it's not innovation by g4dget · · Score: 2
    I do hope that people will use either Java or .NET, or both, more on Linux. It really fixes a lot of problems with Linux applications development, just like it does on Windows.

    But calling this a "true innovation" is ridiculous. Both .NET and Java are decades old technology. Neither Microsoft nor Sun "innovated" there. Except for the snazzier graphics, people were building the same kind of VM systems and object-oriented languages in the 1970s and early 1980s.

  146. My company already tried it! And abandoned .NET... by croanon · · Score: 0

    at once, after the big performance hit they got. They tried to call some ActiveX components from .NET runtime.
    .NET my ass!!!!

    --
    Dear Bill, do you have a .net tatoo on your ass for marketing?
  147. it doesn't matter by g4dget · · Score: 2
    Linux needs an application development platform that is more robust and simpler than C or C++. Cross platform or Microsoft-compatibility is irrelevant for that purpose. Mono may or may not end up delivering, but it is clear that Java does not fit the bill--Sun's policies and the way Java has evolved make it unsuitable for much open source applications development.

    Not only are these libraries not standardized, they are likely to be protected by patents.

    That's FUD. You can't protect "libraries" by patents, only inventions. And there are unlikely to be many patentable inventions in the APIs of common GUI and OS libraries.

    ultimately Sun just owns the Java name, not all the implementations.

    There is effectively only one Java implementation: Sun's and its derivatives. And since there is no standard for even the core language and libraries, there aren't going to be any others, only some tinkering with things vaguely like Java.

    1. Re:it doesn't matter by liloldme · · Score: 1
      Java has evolved make it unsuitable for much open source applications development

      Why don't you give some specific examples rather than useless blah blah bullshit? Why is Java unsuitable for much of Open Source application development? Please explain. It seems Sourceforge is filled with Open Source Java apps.

    2. Re:it doesn't matter by g4dget · · Score: 2
      Why don't you give some specific examples rather than useless blah blah bullshit?

      That's very simple: there is no open source implementation of the Java platform (Kaffe, gjc, etc. are not implementations of the Java platform, and they have lots of problems even as they are). It makes no sense for people to develop, say, a Linux desktop in Java and depend on a proprietary runtime.

      It seems Sourceforge is filled with Open Source Java apps.

      Sure, and there are also open source VisualBasic, open source Windows, and open source Delphi applications: people share source for all sorts of reasons under all sorts of licenses. But most open source software is developed on open source platforms with open source tools, and for good reason.

    3. Re:it doesn't matter by liloldme · · Score: 1
      It seems Sourceforge is filled with Open Source Java apps.

      Sure

      So in fact your claim that "Java is unsuitable for Open Source application development" has no grounds. There's an extensive collection of Open Source applications written in Java.

      But wait, you say real Open Source application development can only occur on an open platform using open tools -- that itself rules out the majority of operating systems in use today, and in fact large part of existing Open Source applications.

      But wait wait, even that Open Source Linux with all its Open Source tools runs on proprietary hardware -- we never know when those pesky Intel engineers decide to fuck up the op-codes in their processors. So, according to you, Open Source application development does not exist.

      Excuse me for saying but you're full of shit.

    4. Re:it doesn't matter by g4dget · · Score: 2
      So in fact your claim that "Java is unsuitable for Open Source application development" has no grounds.

      I didn't make that claim.

      But wait, you say real Open Source application development can only occur on an open platform using open tools

      I didn't say that.

      Excuse me for saying but you're full of shit.

      Excuse me, but you are responding to things I didn't say.

  148. Where's the .NET by jav1231 · · Score: 1

    Uh..has anyone seen a .NET app? I for one, think it's vaporware. ".NET App Hunter heh, suching for the aylusive .Net App! 'ays a wiley bugger! And ye' 'ave to be very careful when ye' approach 'im! 'Ee might jest disappear! POOF! Before ye' can even get a glimpse of 'im!"

    1. Re:Where's the .NET by liloldme · · Score: 1
      well I suppose any old VB app recompiled with the latest VisualStudio counts as a .NET app.

      It's nothing but slapping a bunch of hyped up market jargon on top of old technology. And half the industry goes ooh and aah.

      I guess it says alot in itself.

    2. Re:Where's the .NET by Anonymous Coward · · Score: 0

      Bo, but that wholey ignorant comment of yours says a whole lot about you!

    3. Re:Where's the .NET by Anonymous Coward · · Score: 0

      well I suppose any old VB app recompiled with the latest VisualStudio counts as a .NET app
      in case you're still wondering: no, it doesn't. .net is a nod towards Java and an open VM instruction set designed for multi-language support.
      btw, "alot" are two different words. sorry hat to do that :)

    4. Re:Where's the .NET by liloldme · · Score: 1
      .net is a nod towards Java and an open VM instruction set designed for multi-language support.

      Uhmm, so? If I transform my old VB app to new VB.NET with my spanking new VS.NET it's not a .NET app?

      I don't see how byte codes are relevant here. That's like saying Java bytecodes have some relevance to what constitutes a J2EE application.

    5. Re:Where's the .NET by liloldme · · Score: 1
      btw, "alot" are two different words. sorry hat to do that :)

      By the way, my hats never do that.

    6. Re:Where's the .NET by Anonymous Coward · · Score: 0

      you're getting sleepy...sleeeeeeepyy. lol.

    7. Re:Where's the .NET by Anonymous Coward · · Score: 0

      well, you said "that i suppose that if i compile my old vb app with VS then is is a .NET app", which would be technically true if it were possible to do that without having to rewrite most of it. If you had actually tried this or looked at the new VB language spec changes, you would know that.
      But after making those changes, then it would obviously be a so-called ".NET app" since it would use the .NET runtime and framework libraries.
      I don't see your point.

  149. Do you know the story of "TOWER OF BABYLON"? by croanon · · Score: 0

    You are a complete idiot Iamthefallen. You can also learn 100 languages more if you want to. Idiot. :)

    --
    Dear Bill, do you have a .net tatoo on your ass for marketing?
  150. I thought the name MONO is related with MONOPOLY. by croanon · · Score: 0

    For some reason. :)

    --
    Dear Bill, do you have a .net tatoo on your ass for marketing?
  151. No, thank you by mwood · · Score: 1

    I'm still waiting for someone to explain why I should want this .Net stuff at all.

  152. Framework by Hellraisr · · Score: 0

    I'd like to shed a bit of light regarding the .NET Framework.

    Firstly, the .NET Framework is a free download for Windows users, and MS plans on implementing it on other platforms as well. This has always been their plan, so that you can write a program in Windows and have it work on Linux, Mac, etc.

    Secondly, I wouldn't trust an open source version. It's not that I don't like open source, and that they wouldn't do a good job. But I'm sure MS is not going to let you know every little nook and cranny of the framework which is basically a bunch of libraries and compilers.

    What may end up happening is a year down the road the open source .net framework is shown to not be living up to the requirements of the original framework.. which would be very bad from a development point of view.

    Imagine writing a program in c# and it doesn't work properly. But the coding is all correct.. What a nightmare..

    Just like to point out, MS is not making cash off of the framework, but off the visual studio section. Anyone with windows can get the .net framework and sdk for free with windows update.

  153. Good, now I don't use Gnome. : ) Be happy traitor. by croanon · · Score: 0

    Miguel is a traitor. :) He only thinks about his fame and fortune. :) He likes licking Billy's balls. :) Lay lay loooom. :)

    --
    Dear Bill, do you have a .net tatoo on your ass for marketing?
  154. Big Requirement to Run .NET by Jack+Admiral · · Score: 1

    Do you know what it takes to run .NET applications? A 20 mb download of the runtime!! Crap!! This isn't the SDK folks. It is only the runtime. Take a look at it here:

    http://msdn.microsoft.com/downloads/default.asp? ur l=/downloads/sample.asp?url=/msdn-files/027/001/82 9/msdncompositedoc.xml

    I was ready to download this and try it out but I'm not gonna install another piece of bloated crapware on my machine. Sheesh! 20 mb. That'll take forever to download. At least the Java runtime is only 9 mb. I think the Java SDK is 30 mb.

    1. Re:Big Requirement to Run .NET by NightEyez · · Score: 0

      Remember the dotnet framework classes are much more extensive than Java, they include several OS functions that Java doesn't even touch (Java is platform neutral).

  155. Re:You've got your wires crossed... by Anonymous Coward · · Score: 0

    The idea behind the .NET framework is also write once, run anywhere. The Mono people just haven't implemented the System.Windows.Forms namespace yet. Once they get that working, a properly written .NET component will use Windows controls or GTK# widgets depending on the platform.

    RTR

  156. +5, mods are morons by Anonymous Coward · · Score: 0

    Stupid mods LOL!

  157. Excuse me? by HiThere · · Score: 2

    I know I can (or will be able to) under the CLR.

    Could you tell me what definition you are using for the word know? Does it mean anything more than "A salesman promissed me"?

    I'm not definitely saying that you are wrong. I've seen attempts to port Basic, so there are, indeed, those who thing it a reasonable thing to do. But all of the VB code that I've ever seen depends so heavily on platform specific libraries, that I have strong doubts. And it will take a lot more than a salesman's promisses before I believe that MS will actually port their libraries to Linux.

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
  158. Re:blah by Grizzlysmit · · Score: 1

    .net is crap so is java I hate the whole interpreted byte code thing, but if you want to use it thats your problem

    --
    in my life God comes first.... but Linux is pretty high after that :-D
    Francis Smit
  159. Don't apologize by GCP · · Score: 2

    I'm a huge fan of .Net. I don't mind using Windows clients, but I want to use Unix/Linux servers. What you're doing is going to make that possible, and I think it's great. Thank you.

    As for the scope of your project, feel free figure it out as you go along like all the rest of us do. The guy mouthing off about your "lies" is an idiot. If you have to choose a technology for an upcoming project and you can't afford to be wrong, you'd better choose from among technologies that already exist. What you are offering is technolgies that *might* exist, that so many of us *want* to exist, but might not if things don't work out, and even if they eventually do exist nobody knows for sure when they'll be ready for production use. That's the way it works for big companies, small startups, OSS projects, pretty much everyone creating new tools. That's what "in development" means to project planners with any sense.

    --
    "Those who have never entered upon scientific pursuits know not a tithe of the poetry by which they are surrounded."
  160. Re:Rundown: Careful consideration, not emotion by Anonymous Coward · · Score: 0

    Ok, uh. The GPL is a virus and virtually everyone in O.S. land now refers to it as that. Just because MS coined the phrase does not mean they were wrong or mean or evil. They saw the truth and spoke it. Now eveyone else sees the truth and are wearing it as a badge of honor.

  161. Wait for C# "unsafe" code by javajoe99 · · Score: 1

    You gota love this one, a little nugget in the C# runtime, the use of COM/dlls with an unsafe keyword. Wonder how many M$ apps will use this for com libs, that will ummm not show up on mono (i.e. remain closed and guarded), so your linux app may run on .NET but I don't see Word .NET running on your linux box any time soon.

  162. Did you ever see M$ helping anything about Linux? by croanon · · Score: 0

    Come to your senses. Also, all the major players in Application Server market, IBM, HP, Fujitsu, JBoss, Sun, BEA, etc., ALL OF THEM SUPPORT J2EE. .NET is supported only by Microsoft. .NET on Linux may become reliable maybe in 3 years. If you check out Gnome 2, you can easily see that it is a failure. The guys are not capable to create a robust system anyways. Even if they are, creating application server is not easy thing. Even JBoss is there for more than 3 years, and this year, they reached production quality. All the giants in the market have Java based application servers. IBM WebSphere is in its 8th version or something like that, and you say, everyone, will leave this robust, already sold to thousands of customers products and start .NET on Linux, which is new, and untested. How many times that we should say that .NET's important parts are not given to the standards? Even if they were, what standards would do? Absolutely nothing. Standards my ass. If MS change .NET out of the standards, what will they loose? Now, monopolist wannabe Icaza changed his mind, started to say, we will not support WinForms at all. Pheewwww. Big deal. I never believed that they can anyway. Even if they did, M$ wouldn't let them. Please utter some intelligent sentences or don't write at all and spend my precious time.

    --
    Dear Bill, do you have a .net tatoo on your ass for marketing?
  163. NO, HE IS JUST MONOPOLIST WANNABEE. by croanon · · Score: 0

    Aren't you Mig?

    --
    Dear Bill, do you have a .net tatoo on your ass for marketing?
  164. YOU SEE MIGUEL HOW ARE YOU HELPING MS SHANIGANS?? by croanon · · Score: 0

    As I told you before, MONO is helping M$, more than it is helping to Linux.
    "GNOME" Leader my ass. You are just an idiot. Gnome 2 sucks anyway. :)

    --
    Dear Bill, do you have a .net tatoo on your ass for marketing?
  165. Thanks man! Funniest post I read for a long time. by croanon · · Score: 0

    :) Thanks. :)

    --
    Dear Bill, do you have a .net tatoo on your ass for marketing?
  166. .NET is great! by datrus · · Score: 1

    The .NET framework is excellent stuff!
    Go mono!

    datrus

  167. C# is a flawed language by petilon · · Score: 1
    Take for example the much touted Type System Unification. It is broken. According to Microsoft, "boxing and unboxing" bridges the gap between reference types and value types. But it doesn't. Reference types have the concept of identity and equality, while value types only have equality. Boxing and unboxing does not change this fundamental difference. Autoboxing in C# allows value types to go back and forth between being objects, but each time a value type becomes an object it acquires a new identity. This is very dangerous as it can lead to bugs that ar hard to track down. For more information, including sample code see www.geocities.com/csharpfaq/box.html

    For another example see structs in C#. Structs look just like classes when they are declared and used. But they work very differently. Using structs can result in very unexpected results, as you can see in this example: www.geocities.com/csharpfaq/test1.html. For more information about structs in C# see: www.geocities.com/csharpfaq/structs.html

    Java caught on among programmers because of two reasons: WORA and simplicity. Is C# WORA? Microsoft has been telling us for many years now that WORA will never work, so it is safe to assume C# will never support WORA. Is C# simple? To answer this last question, consider the fact that the C# statement x.y += a[b]; can contain upto 10 hidden function calls, including properties, indexers, operator overloading, user-defined implicity type conversion operators, etc. For more information visit www.geocities.com/csharpfaq/test2.html

    C# has neither of the features that attracted programmers to Java: No WORA and no simplicity. This language is no threat to Java.

  168. Re:A linux user goes back by poopbot by _damnit_ · · Score: 1

    Are you really Katz in disguise? 'Cause you take just as long to make a simple point.
    It's a really good write-up of your experience. I agree with most of your points. There is a need for a network transparent display system, however. The question in my mind is does it have to suck just as bad at the console as at the end of a 10mbit ethernet connection? Why is my desktop on a fucking 8xAGP card if I get just as good performance remote hosted to a machine in the lab? wtf?
    Oh, well. I don't use linux anymore either. I put it back on the laptop or a machine at work or home a couple times a year to play; I just use Solaris and rarely M$Windows. I seem to live just fine without a lot of the crap most people I know swear they can't live without. (Who really cares about 95% of the crap MS Word can do? It's excel that I miss the most.)

    Just leave my HDTV and Tivo alone and we'll all be fine. And now for something completely different....

    A fine hefewiezen...

    --


    _damnit_

    It's my job to freeze you. -- Logan's Run