Slashdot Mirror
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."
It is interesting that now that Mono is getting to a more complete (and possibly usable state), most developers have moved beyond the .NET hype and onto more elegant development platforms...
.NET. Mono supports .NET, but that's not its primary API.
Please stop conflating Mono and
In fact, the primary API is the same API lots of open source software uses: Gnome, Gtk+, and many standard open source libraries. All Gnome apps using Mono use the Gtk+ APIs.
I wish there were better alternatives, but C# + Gtk# + MonoDevelop is probably the most elegant development platform right now. Nothing else really comes close. Python is a more elegant language but doesn't have a comparable IDE. Objective-C and Cocoa are messily intertwined with C and C APIs. And Java is a bloated pig.
Say what you will about Mono, I think Microsoft's implementation of .NET is actually a pretty strong contender. If you need to solve a problem in Windows really fast, it can be pretty insanely convenient. I think Powershell in Windows Server basically uses a .NET machine for its shell interface. If you ever need Windows machines and Unix machines to talk to eachother, a Mono compatible implementation could be even more convenient than having Python talk to .NET, which isn't too hard to begin with.
I can kind of see the point you were trying to make, but .NET doesn't just refer to the bytecode interpreter - it also refers to the runtime libraries etc, which is I think the point that the GP was trying to make.
.NET confuses the issue a bit too... but I think most of us can get our heads around it :)
The fact that python can run under
Info for you: .NET 3.0 is 4 additional dlls, otherwise it IS .NET 2.0. Same runtime/etc. It adds:
.NET 3.5 is enhancements and bugfixes of 3.0 PLUS LINQ. LINQ is either the best thing ever, or the worst thing ever, depending on who you ask. I think "both." LINQ allows you to apply "sql-esque" syntax to any IEnumerable provider. So if you have an in memory collection of animals you can do:
.... do stuff
-WCF: GREAT new tech. You write a module, and then expose it remotely via config. So if you want to change from Remoting to Compliant Web Services you simply change a config setting. Or you can expose simple services via REST. It abstracts "transport" from "functionality".
-Cardspace: dud. Single sign on/identity mgmt which is being replaced by openID it seems. Cool idea though.
-WPF: Cool new xml based description language to fully abstract process from gui much in the way ASP.NET does. It also lets UI designers "skin" apps seperately from the app code itself. VERY nice tech, especially the bindings.
-WF: Nice tech, not quite mature but neat to use. It allows for program logic to be described in an xml format (XAML) and shown in a gui designer. I really like workflow tech NOT because it lets business users program (it DOESN'T) but because it gives you an artifact that users can understand AND CONFIRM.
var monkeys = from animal in myAnimalsCollection
where animal.Type == monkey
select new {animal.ID, animal.Name, animal.BirthDay};
foreach(var monkey in monkeys)
LINQ is nice, except it's decades too late. Of the languages in common use today, Python and Ruby have much better alternatives to linq built in (and have had them for many years), and even new languages like Scala support similar functionality.
Your example in Python with a list comprehension, broken down into multiple lines for clarity:
monkeys = [
(animal.id, animal.name, animal.birthDay)
for animal in myAnimalsCollection
if animal.type is monkey
]
And a comprehension of multiple lists is similar:
pairs = [
(a, b)
for a in range(10)
for b in range(10)
if b == a * 2
]
You have been able to do that for many years in Python, and yet Microsoft fanatics act like it's something new and innovative.
Sam ty sig.
Python containers can read from whatever source they are designed as they are iterated. LINQ seems to be syntactical sugar not unlike list comprehensions.
Ctrl-A, Ctrl-K, Ctrl-F
The python version reads from an iterable, so it can be a request from a DB or an XML file sending its result one by one. In the case of the Db, the filtering will however be done by python and not in the DB.
However, there are alternative ORM python syntax to DB mappings, such as django syntax
AnimalCollection.filter(type='monkey')[:10].order_by('age')
(talking about simple orms, not full sqlalchemy table declaraions)
Being able to customize filtering of container classes for iterators definition would be cool anyway.
Sorry.
It's a pretty thin layer compared to an entire extra base library + bytecode runtime + OS abstraction.
PyGTK layers:
Your code (python)
PyGTK code (python)
Python runtime (C)
PyGTK->GTK binding (C)
GTK+libc code (C)
kernel (C)
IronPython + Gtk# layers:
Your code (python)
IronPython code (python)
IronPython runtime (CLI)
Gtk# code (CLI)
Mono base (CLI)
Mono runtime (C)
Gtk# -> GTK binding (C)
GTK+libc code (C)
kernel (C)
That's a fun one to deploy, let me tell you.
Sam ty sig.
All the usernames on a Unix system:
Dates from an SQL table:
Search Google for "list comprehensions" and print the text of every "<a href" tag on the page:
Basically, anything Python can loop across works inside a list comprehension. It's a basic construct of the language.
Dewey, what part of this looks like authorities should be involved?