Slashdot Mirror
DotGNU and Mono Continue
saurik writes "After what has been a strange few weeks of converse between the DotGNU and Mono teams (including a small PR SNAFU that involved the banning of a member from the DotGNU mailing list), DotGNU has now announced that they will be forming a partnership with Portable.NET." Frankly I like that there are 2 efforts going on. Maybe one will succeed.
I know this is a trite argument, but it is appropriate (and no, I'm not trying to flame anybody, or even single you out or anything):
If you really think another way is the way to go, please start doing it. You don't even need to be a programmer yourself; write up a paper detailing the failings of the current efforts and propose a better way. Disseminate this text, and persuade other coders to join in and implement it. Even if you do not succeed in getting your project started, your work will not be wasted as your analysis will be helpful in guiding the current projects.
The people working on Mono, DotGNU and Portable.NET are all doing it because they believe their project is the right way to go about it. Any productive feedback - in the form of a design document or a competing project - is very helpful for all involved. A random 'I don't like this', on the other hand, is likely to be ignored.
/Janne
Trust the Computer. The Computer is your friend.
Except that the JVM currently runs on most platforms. Gnome, to my knowledge, is Unixen-only, with some parts of GTK ported to Windows. As such, the JVM can be viewed as something that breaks a desktop dependancy.
--Be human.
Yes, my friends, fight against each other. If you don't agree the way a project is running, leave the project and make another one by your self!
That's the spirit of Variety. That what keep our Freedom of Choices. I like to choose Window Maker, and I also like that my pal prefers Gnome. That's the variety that I love to see!
Imagine a world where there are no differences, where all window managers look the same! This sux! I prefer to see a good fight, I prefer to see people getting out of a project and building their own. But I'm sad about that horrible happening about baning (too sad...)
Of course, freedom is hard to manage. Ditatorial government are much easier than a real democracy. Be fair is much more difficult, look all around is much more difficult, but IMHO is much much much better!
Let's fight and build several .NET projects. Can I see a third project in the horizon? Maybe I'm right, maybe it's just a dream, maybe everybody fits into dotGNU and Mono. That's ok too, the point is, we still have a choice!
FREEEEEEDOOOMM!!!
-=-=-=-=
I know life isn't fair, but why can't it ever be un-fair in MY favor!?
Yes, but Microsoft's strategy here was perfect, because they know it's too much of a gamble for the open source community NOT to make an open source version of .net technology.
Certainly if we did nothing Microsoft would have to work that much harder to gain universal acceptance of .NET, but if we have an open source alternative at least nobody has to be under the iron grip of MS. That's not too high a price to pay to avoid MS dominance even if it plays into their hands to an extent.
Unfortunately Microsoft has all the leverage in this particular case because they control the client. We could come up with something a hundred times better than .NET and .NET would still win because the client bits of .NET will be on every new PC firmly embedded into Windows.
The Samba developers really have the right idea. Instead of creating a network file system and then trying to create a Windows client (which Microsoft could break at every .dll update) they instead took the route of emulating Windows servers. Even with a crufty protocol like SMB this turned out to be the easiest route. Microsoft doesn't want to break their own clients, and so they are limited in what they can really change.
One of these days Linux (or some other open system) might very well have enough client side market share that the Free Software folks could create a client side standard and actually have some weight behind it. The closest we have ever come was with browser based applications, and even that was marred by Netscape-isms and the even more overwhelming IE-isms that are cropping up more recently.
Free Software is getting closer, however. My guess is that it is only a matter of time.
Make the community disperse its efforts on copying what is little more than vaporware
Make the community look like a bunch of childish "I can do that too" people.
The only thing that comes to my mind when I look at the mono and dotGNU projects is "monkey see, monkey do". One of the projects can't even come up with an innovative name for itself. Well, I'm sorry but copying .NET is just dumb and it plays in favor of Microsoft, who looks like the real innovators that legions of unimaginative free-software geeks always try to copy.
In short, the community has to stop copying and being toyed with by Microsoft, and begin innovating and proving that there are much better things than what Microsoft comes up with.
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
Ah, the irony So Swing now runs at acceptable speed because it uses non-java code.
...it's hard for people in business to Open Source seriously.
.NET-clone projects get off their high horse and just merge the projects together? All this stupid in-fighting just goes to show that Microsoft has nothing to fear from Open Source.
This is no different than the Gnome vs. KDE debate, or Debian vs. RedHat, or hell, even Linux vs. BSD. We fight amongst ourselves so much that we can't present a unified front against (much more organized) Closed Source efforts.
Will somebody at one of these
NO CARRIER
Mono is a GNU port of C# and the CLI runtime. What people think this has to do with authentication, I have no idea.
Porting a language means making it available to another platform. With mono, you can develop C# on gnu/linux. Why is this such a terrible and confusing thing to so many slashdotters? Is the availability of another development platform a bad thing? The only thing that would really bug me is if the KDE team decides to write their own separate implementation. The fact that Mono will be tied to Gnome is iffy, but what are you gonna do? Gnome has to make strides of some kind or another to stand out.
When Gnome says they have customers, I believe them.
I don't give a shit if my Mono applications don't even work on Windows. I'd like an alternative to Java that doesn't feel like a toy.
I don't know if dotGNU is needed. I guess if it means I only need one username and password to log into any sites that have accepted their standard, then that's just super.
But wether or not I am going to be able to go to Amazon.com and identify myself with a dotGNU login, I don't know. Frankly, I don't care.
Mono interests me, dotGNU doesn't.
This has a lot of potential, and I see "internet services" as a small part of it, at least in the way it effects me.
Then again, I'll probably never bother using it, unless there's Smalltalk and CL implementations as good as or better than the ones I use now. :)
Working toward a usable PDA environment in the spirit of Newton OS: Dynapad
"Frankly I like that there are 2 efforts going on. Maybe one will succeed." Well in a sense it is good that the projects have comed together specially when the outcome seems so young. Later on when the technology does become usable there will be other similar projects even based on the original.
The JVM is as much of a "needless desktop dependency" as Gnome is.
got drum'n'bass?
http://mp3.com/vitriolix
Actually, as I stated before, Sun has their own environment they're developing, Sun ONE, and I belive it was announced before .NET. .NET is a reactive strike against Sun just as its key language, C#, is a reactive strike against Java.
"But remember, most lynch mobs aren't this nice." (H.Simpson)
-- Joe
Mouse wheel support? It's in there. Check v1.4 of the JDK.
Accessibility (support for the disabled, but in a PC way)? It's in there. Check out the Java Accessibility API.
I'm afraid I don't have any information on how one can utilize the native OS theme for colors and such. Do you have a reference to a bug/feature request in Sun's bug tracker on this one? It may be in v1.4, but I simply don't know. I'd bet it's not, though.
My point is just that you should really give v1.4 a chance. It's quite nice, despite changing a few of the APIs such that many v1.3 programs must be ported (very few changed, but just enough that it's not a simple copy-and-run for programs like Forte).
--Be human.