Slashdot Mirror
Mono Project Releases Version 1.0
theblackdeer writes "Just poking around the go-mono.com Mono website; it's now the multi-colored mono-project.com. Even better, it updated before my eyes to include the 1.0 release. Screenshots are (slightly) updated, too. Mono 1.0 includes the Mono Develop IDE (based on SharpDevelop, I believe). Download now and start your GTK# engines!"
Alliante adds "You can download the Release Notes and the Packages on their website."
From the FAQ:
The Mono project has also sparked a lot of interest in developing C#-based components, libraries and frameworks
Yes it has. In our company's roadmap, we considered C# and Mono, but the controversial elements of their licensing (ASP.NET, ADO.NET, and Windows Forms subsets) gave us pause until we researched it further. Most of it is covered under the ECMA/ISO and the other technologies developed on top of it.
Looks like the Mono strategy is to work around the patent issues by using a different technique that retains the API but changes the mechanism.
Sigs cause cancer.
As long as you don't use P/Invoke or too many of the Windows.Forms items, it should do fine. That's part of the whole point.
:)
The other thing you can do is run Gtk# on Windows for your xplatform GUI.
Wonder if that can be run in mono..
.NET terriarium is damn coolb Index= 6&tabId=42
installing to find out.
I have been playing in GTK getting sprites and such working, but would like to use this for more portability..
http://www.windowsforms.net/default.aspx?ta
Check it
anime+manga together at last.. in real time.
As long as you either use GTK# ( download ), wxNet or console mode you won't even have to recompile it under mono on linux/MacOs/whatever. You will be able to just run it.
For those looking for an IDE, try out MonoDevelop 0.5. It doesn't have a gui builder, but has code-completion(intellisense), class browser, project management, etc... It's a port of Sharpdevelop.
There are other reasons, I do not claim these are all of the possibilities, but here are some more:
to be supported without hacks.
issue solved completely by the availability of it
on
ints will be a list of ints, and not syntactic sugar for a list of objects of Integer. Importan
for performance.
for the framework: its trivial to call back into the old code base, without using JNI of any kind.
(yes, that means that someone else can build something new now, and fix the
But feel free to use Java for doing Gnome applications, I have nothing against it, we are
only an equal opportunity platform provider. Let the big boys fight it over.
Miguel
Ive been a big critic of Eclipse in the past but 3.0 is huge improvement over their previous efforts and its not actually bad. IDEA IntelliJ is probably the best IDE out there but will cost you a few bucks. NetBeans is passable or you can download JBuilder Foundation which is quite limited, the decent versions will set you back a fair whack. I'm not sure if Oracle JDeveloper is free, it's a JBuilder spin off and from what I hear not bad. Eclipse is the pick of the freebies but I prefer to pay for the quality of IntelliJ.
Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
What truth?
There is no dupe
The greatest risk of the Mono project is Microsoft stepping in and filing suit against the project for using its API w/o a license. Doesn't anyone else see this? Why was Mono ever started to begin with? All you Mono developers are doing is putting $$$ into microsoft's pocket!!!
Actually, the majority of the API is covered by the public EMCA specifications. Microsoft specifically made it impossible (very very difficult) to sue someone for that when they made the standards public. See the mono and microsoft faq for details. The fact that mono is perfectly legal doesn't change the fact that they may be putting $$$ into microsoft's pocket though.
No. You're the one who doesn't get it.
Just exactly how is Mono+Linux any better than .NET+Windows?
Runs on Linux.
Does the Mono team have ANY plans to innovate beyond what Microsoft is doing
Yes. See GTK-sharp, Qt-sharp, Mono.Posix, Mono.Data, etc. (in fact, try reading the FAQ before posting) The Mono and portable.Net projects are both interested in supporting the Microsoft APIs, but support for Linux APIs is also important.
...no distribution ships Sun's JVM...
WRONG! SuSE does.
"The linux landscape is changing, its going mainstream, and there are a lot linux users who don't like that. I must humbly suggest to such people that you cannot do anything about it, and you should therefore either accept the reality or start moving to another system where you can feel more "l33t"."
You call others narrowminded but I don't think you yourself understand the reasons people are afraid of the side-effects of Linux growth. Maybe you're just hearing a vocal minority.
I personally cannot stand to use Windows these days, for many reasons... but one of the biggest is the environment. Under Linux searching for help, files or other content is particularly easy: the signal to noise ratio is quite good. Under Windows, it's "Sign up to download, we sell your email, now you can wait in a queue to get your file, but here are some ads to keep you busy". Pop-ups, spam, misdirection, just junk in general.
The bottom line for this reasoning is that Linux it's just easier to find what you want (or at least a definitive 'It doesn't exit') in a shorter time. When the community starts growing, we'll see lots of wannabe applications attempting to sell themselves to you, registration keys and website registrations, hassles downloading files or getting help, etc. This is a Bad Thing.
That all said, I'm in favor of Linux's growth and I think most people are. There aren't many true Linux users who do it just to be "leet" and I think its pretty silly to suggest that. Most Linux hobbiests do it because they are in control, in one way or another -- application choices, configurations, power, etc.
Slapping a dogma on someone and calling them an idiot isn't helping anyone. I think the Linux community is ready to expand and wants to expand, it's just afraid of how severe the consequences might be when the 'unwashed masses' start using this stuff.
Cheers
~Dalcius
Rome wasn't burnt in a day.
Check out the The Mono Handbook for tutorials and general getting started instructions. It's still a work in progress, so many sections are still quite empty. Another resource you should familiarize yourself with is the MSDN developer documentation for most of the core .NET API, it includes a lot of examples.
I also recommend you check out the standard GTK+ tutorial. A lot of it is still directly applicable to GTK# and it's more complete than most GTK# only tutorials. If you're already familiar with GTK+, Glade# for Rapid Development will help you get up to speed with Mono.
It's like deja vu all over again.
No they can't. read the FAQ
I now have to use C# at work as our company has decided that this is what Microsoft's future is invested in. I've had a love-hate relationship with it, and my opinion of .NET is possibly clouded by my use of C#, rather than a criticism of .NET, but anyway:
- Multi-language support by design is a hack. It's not real. C++, for example is not C++ as I, as a C/C++ hack, know it. It's a thing that is something like, but not quite C++.
- structs as ValueTypes are a pain in the arse. They have the same syntactic semantics as classes but have no similarities. Because of this
- Generics are not yet a standard feature of of
.NET CLR. This is the reason given by Microsoft for not including generics as part of C#.
- EMCA standardisation is a joke if the libraries can be butchered. The language is the least of the problems when portability is concerned. The precise way in which the libraries work and interoperate is the big problem.
- .NET - as far as I can see - was simply a way of touting a "write once, run anywhere" platform, without actually proving the case. C# takes some things out of Java, and some out of C++, but never asks the question "why are these here". Operator overloads without templates, and without a good distinction between references are pointers spring to mind. (what does 'foo == bar' do?)
- Some prefer C#, but I can't see why...
Sorry Miguel. Mono is a worthy project, and I have it running on OS/X - it's impressive from that point. But asflibble foo = new flibble();
flibble bar = new flibble();
foo==bar"
means two completely different things depending upon whether flibble is a struct or a class. Which has given me endless problems with DateTime.
The ways of gods are mysteriously indistinguishable from chance.
Give an example of where this is needed.
.NET is performance and your solution is to wrap them with JNI which has its own overhead? Maybe you're still stuck on the idea that the only reason they exist is to gived pinned memory which can be used to interoperate with older C API calls. False. If that were the case NONE of the native types would be value. The value type would be something esoteric that was only dragged out when you needed to P/Invoke.
.NET has. This was added on top of JSR-14. You are probably looking at the original generics design for Java 1.5 on googled pages. Its been updated.
Um, anywhere that a method gets called continuously that has a large number small local variables (int, double, etc) that are used in calculations. My choices are to either pass in a re-usable object (which sucks when you have a method with 10+ local doubles) or to make the thing class level (if the method happens to be in the calling class) or to stash it in some static class that both of my classes now need to know how to interact with. Pretty much every option sucks, save defining the thing where you need it. Hell, if I was programming Java performance would have to suffer and I would not think twice about it (unless I *had* to) simply to avoid the maintenance headeaches of the alternatives.
Also note that structs can be created, manipulated, and destroyed with Java with JNI and CNI.
The entire point of using structs in
Java 1.5 has auto unboxing. Same thing
It's quite possible that my general ignorance about most things Java is showing. I'll dig into this and see how it compares to the (admitadly date) materials I have read.
You can implement scheme on the JVM too - read this paper comapring the compilation of Scheme to C, the JVM, and the CLR! It was put on 6/16/2004 so is pretty recent - the link came from here
.Net executables yielded no perforamnce gain over just leaving the executable in IL!
.Net VM was found at this time to be generally slower than the JVM.
.Net - Scheme.Net is still pretty new, and Hotdog is not really done yet either.
One interesting result is that precompiling
Also, the
I couldn't really find a complete Scheme for
"There is more worth loving than we have strength to love." - Brian Jay Stanley
debian-unstable's had the packages for a while. Works for everything I've tried... have to admit I haven't tried that much yet, but so far so good. Works nicely with apache2 last I tried.