Announcement

Collapse
No announcement yet.

Mono Project Continues Making Progress

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • johnc
    replied
    Originally posted by Luke_Wolf View Post
    What the difference really amounts to is that .NET and C# are what you'd get if you asked a C++ programmer to design a C-Like managed language with OOP paradigms and the compatibility with C inside the language wasn't a requirement. Java on the other hand is what you get when you have a control freak doing the designing, which I suppose is fine for the guy with OCD, but as someone who feels at home in C++ writing in Java is hell, whereas in C# I feel just at home
    I kind of see it the same way. I was well familiar with C and C++ but I never felt particularly married to them. (I have no real issues with them either, as opposed to something awful like PHP.) So when it came time to learn Java I just thought it was extraordinarily easy and simplistic (or maybe intuitive is the word I want here?). It came off as a "clean-room implementation" of OOP whereas C++ was kind of a hack-it-into-C approach. I see C# more as a continuation of C++ rather than something new and clean.

    Other than Android I suspect my Java days are over. I'll probably never pick up C#.

    Leave a comment:


  • Luke_Wolf
    replied
    Originally posted by bulletxt View Post
    Comparing Java to C# is like comparing Linux to Windows. I personally feel it does not make sense. There are 100 reasons why to use the first and another 100 reasons to use the second. I can personally find more reasons to use Linux but I'm sure someone else will find more reasons to use Windows.

    In other words, use what you need. IT is not a religion.
    well.. they're actually rather comparable because they're the two big competing managed language frameworks, that derive from the same source and are starting out with the same goal: to Write a managed strongly and explicitly typed C-Like language that supports the common OOP paradigms.

    What the difference really amounts to is that .NET and C# are what you'd get if you asked a C++ programmer to design a C-Like managed language with OOP paradigms and the compatibility with C inside the language wasn't a requirement. Java on the other hand is what you get when you have a control freak doing the designing, which I suppose is fine for the guy with OCD, but as someone who feels at home in C++ writing in Java is hell, whereas in C# I feel just at home, but until Qyoto comes properly online I wouldn't really consider writing GUI desktop applications in it (although I might look at Xwt if it gets a Qt backend) mostly because I run KDE and GTK3 themeing is broken if I use one of the theme engines that makes GTK look like the rest of my KDE/Qt applications, but works fine but looks out of place and ugly if I use adiwata or another actual GTK3 theme.

    Leave a comment:


  • bulletxt
    replied
    Comparing Java to C# is like comparing Linux to Windows. I personally feel it does not make sense. There are 100 reasons why to use the first and another 100 reasons to use the second. I can personally find more reasons to use Linux but I'm sure someone else will find more reasons to use Windows.

    In other words, use what you need. IT is not a religion.

    Leave a comment:


  • Zan Lynx
    replied
    Originally posted by plonoma View Post
    Exactly Zan Lynx!!! You had to be careful with what WinForms features you used because WinForms has patents all over it!
    No I had to be careful because it wasn't all implemented and the Microsoft form designer kept trying to add incompatible features to the project.

    As for patents and Mono see http://www.jprl.com/Blog/archive/dev...09/Jan-19.html

    Leave a comment:


  • plonoma
    replied
    Exactly Zan Lynx!!! You had to be careful with what WinForms features you used because WinForms has patents all over it!
    But for porting applications you also need to port the WinForms part!
    Very clear this is some kind of trojan horse. Just like pushing exFAT for embedded devices and pushing FAT file system into SD card standard

    Leave a comment:


  • Zan Lynx
    replied
    Originally posted by Pawlerson View Post
    Yes, user base. As for mono nono, there are just FEW mono apps available on Linux and they're joke compared to non mono counterparts. Who will ever bother with something like this? Furthermore, mono nono isn't .Net compatible. Get lost.
    It has been a while since I ran any desktop file indexers. In 2009 Beagle was fat, slow and used a lot of RAM. It was written in Mono. However, Tracker was slower, indexed fewer formats, and gave me more hassles than Beagle did. Tracker would go into infinite CPU loops, for example. Win for Mono there.

    That desktop post-it note program whose name I can't remember was written in Mono. The anti-Mono zealots cloned it in C, which took them about four times as long to write. The result was indeed faster and used less RAM. But if you look at it in terms of programming time the original was a win for Mono because it was so easy to write.

    I'm not sure what you mean exactly by not .Net compatible. Last time I tried it in 2010, I was able to write a WinForms app that ran on Windows, Linux Mono on amd64 and Linux Mono on Itanium. I did have to be careful with what WinForms features I used but it did work.

    Leave a comment:


  • plonoma
    replied
    Mono is trying to implement .NET with the languages and facilities, libraries, api's that come with it.
    However many things are patented.
    It is a distraction from the fact that .NET only works on windows and to pretend they give a shit about cross-platform to push back against HTML+Javascript/Java/Ruby/Others...

    There are much better ways to improve things.
    If they wanted to improve tools for Linux why not help with other projects or help with porting Linux IDE's and stuff to Windows?
    There are non-Microsoft dialects of basic. Why not do something similar?
    Change some little things and call it something different. It works for Microsoft.

    Leave a comment:


  • jayrulez
    replied
    Originally posted by Pawlerson View Post
    They do, otherwise they wouldn't sent such propaganda boy like you to phoronix forums.



    Yes, user base. As for mono nono, there are just FEW mono apps available on Linux and they're joke compared to non mono counterparts. Who will ever bother with something like this? Furthermore, mono nono isn't .Net compatible. Get lost.


    "Propaganda boy". I must admit that this is a new one.

    Welcome to the fucking Internet where everyone with an opinion is a hater|fanboy|shill|"Propaganda boy" or some other colourful adjective.

    You idiots are going to shun Mono then complain that there are just a few Mono apps available for Linux. I'm alarmed by this paradox.

    Also, there are a lot of apps on Linux and they're a joke compared to the non-Linux counterparts. See how that can work?
    Not inherent to Mono.

    ou're kidding, right? Or perhaps, you just copied this from M$r Icaza's website?
    No, no.
    Last edited by jayrulez; 21 August 2013, 12:22 PM.

    Leave a comment:


  • mike4
    replied
    C# never got widely used and is not an open standard, hence forget about it.

    Leave a comment:


  • Luke_Wolf
    replied
    Originally posted by jayrulez View Post
    Mono has a bright future and may even become the de facto implementation of .NET as Microsoft seems to pay more attention to its Windows RT framework these days (See little innovation/improvements in the last release).
    Well what I read on the matter seemed to indicate that they were focusing mostly on Roslyn as opposed to working on features, Which is supposed to come with the version of visual studio after the 2013 version. What I expect is that Roslyn is going to be the big feature for 2013.next(), and then we're going to start seeing more features beyond that coming in again for 2013.next().next() (Not that Roslyn isn't itself a megafeature).

    Leave a comment:

Working...
X