Mono's WinForms 2.0 Implementation Completed
adrian.henke writes "After four years of development, 115K lines of source code, and 6,434 commits, Jonathan Pobst announces that Mono's WinForms 2.0 implementation is now complete. This announcement has been long awaited by any .NET WinForms developer who has ever tried to get an applications to work on Linux using Mono."
..and still nothing on whether WinForms is legally safe to use.
I am not a number - I am a free man!
What platforms? .NET is very clunky, but it still seems very popular.
I'm also very interested to hear what these platforms are.
Where did he say that cross-platform support was required? There's a big difference between something that's required and something that's nice.
IronPython already works fine on Mono, but it doesn't have IDE support. PyDev in Eclipse is pretty nice for pure Python and Jython.
.NET. Maybe Anjuta could stop sucking and support Python, or Eclipse could have Glade integration.
Personally I'd rather work directly in Python/Ruby on GTK/Qt than go through an extra layer that is
And while Mono's not horrible, but it's not nearly as fast as the Sun JVM, so if I want fast bytecode I'd rather use Java than C#.
Sam ty sig.
If you don't want to be compatible with Win32, use GTK#.
Java is fast? Go try to run Azureus and weep.
Oh, you do? And you think it is fast? Try utorrent on Windows or Transmission on OSX or KTorrent on Linux some time.
People can write slow programs in any language. The question is, can moderately competent programmers write fast, efficient, maintainable programs in them? Pointing to one example is pointless. Back on topic, a quick check on Alioth will show you that overall, Java is faster than C#/Mono but uses more memory (although on some benchmarks the opposite is the case). It's also worth pointing out that although Java is not faster than C++ on any benchmark, it's substantially slower on only three. In general the performance of a program has much more to do with good design and good algorithms than it has to do with choice of language.
I'm old enough to remember when discussions on Slashdot were well informed.
When you already have a dynamic language, type inference, anonymous types and extension methods are implicit. I'm not arguing every language should be dynamic, but the additions to C# are just solving problems specific to static languages. That's fine - static languages are still much faster than dynamic ones. Just saying, as far as languages go, C# is the one playing catchup, and with about a 20 year gap for many features.
Sam ty sig.