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."
A open source RAD evironment sounds like it could have a huge impact on the number of apps that could be rolled out.
Not so much for the enterprise market, but also for the 'shareware' class applications. Most of my Windows specific applications are programs that are from very small development houses or shareware products. (I love to support a small shareware author!) . I use open source when prudent, but I also love to use a nice simple tool that even if it costs $15-$20 bucks to a pay-pal account, is money well spent in my opinion. Maybe Linux will start to attract this development base with Mono.
Another question, I have a pro version of C# I picked up at staples last year. Anyone know how realistic is it for me to build an application in Windows using my copy of C# and compile it and run it on mono?
As has been pointed out ad tedium in various Java-related discussions on /. - Java's early reputation for poor performance may have been
justified in the 1.0 and 1.1 days, but modern Java VMs employ
sophisticated JIT compilers which gives it comparable performance to
natively compiled languages like C++, and easily matches .NET's CLR
performance. Java's bytecode and .NET's bytecode are not that different, the main differences are in the APIs.
Which brings us on to the second justification for .NET over Java, native GUIs, which is even weaker. Java-Gnome does the same thing as
Mono's GTK bindings, offering exactly the same GUI abilities, and SWT offers a truely
cross-platform GUI API with a native look and feel on each platform it
runs on.
I've been looking for a good way to write a crossplatform GUI for an app I'm working on. Java is not a good choice for a variety of reasons, so Mono is looking pretty tempting right now. Since Mozilla-The-Platform hasn't taken off as well as it could, Mono may wind up being the best option for a totally Free Software approach to cross-platform work. On the other hand, wxWidgits is a great toolset as well, and I wouldn't be surprised if they get C# language bindings for the library.
"I may not have morals, but I have standards."
Given that my main OS is Windows (sorry), is there anything like this for it?
Avantslash - View Slashdot cleanly on your mobile phone.
Look, mono have cloned an enviroment & language whose direction is steered by Microsoft.
.NET.
.NET framework *NOW*, add features and support for things that the Windows .NET does not have. But also bring the extended version to Windows itself.
.NET becomes the real one, not the MS one.
This is a problem, Microsoft is not nice.
Microsoft can take it into a direction where MS holds patents & IP protection (if it doesn't already which is very unlikely). Mono will either have to follow and lock its user in, or go in a separate direction and abandon any pretensions at cloning MS
What I think they should do is embrace and extend the the
That way the MONO implementation of
This Mono 1.0 release seems to be developer-oriented. Will they (or someone else) be creating smaller runtime packages which only include the stuff necessary to run applications?
It would be nice if there were an easy install package for Win32, too. This might seem pointless on the surface, but Microsoft.NET won't install on all Windows systems due to deliberate barriers, plus Microsoft's distribution does not come with GTk# and so forth.
I'm installing the full release on my main system, but it'd be nice to have a smaller runtime package that I can put on my other boxen to run any apps I create. Perhaps in a few hundred years Debian will have a runtime package which can be depended on by mono apps without having to pull in the whole development environment. (mono-runtime vs. mono-devel, both depending on mono-common)
(I see a page about the Mono runtime but it's talking about the runtime portion of the project rather than a specific runtime distribution.)