[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: kde-devel Digest, Vol 69, Issue 4
From:       Jaime Seuma <jaime.seuma () telefonica ! net>
Date:       2008-12-02 12:59:41
Message-ID: 4935313D.3000306 () telefonica ! net
[Download RAW message or body]

kde-devel-request@kde.org wrote:
> Send kde-devel mailing list submissions to
> 	kde-devel@kde.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://mail.kde.org/mailman/listinfo/kde-devel
> or, via email, send a message with subject or body 'help' to
> 	kde-devel-request@kde.org
>
> You can reach the person managing the list at
> 	kde-devel-owner@kde.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of kde-devel digest..."
>
>
>   
>>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
>>>       
>  
>
>
> Today's Topics:
>
>    1. Re: [PATCH] kdirwatch can not detect link change quite well
>       (Flavio Castelli)
>    2. Re: KDE Development with Mono/C# (Arno Rehn)
>    3. Re: KDE Development with Mono/C# (Friedrich W. H. Kossebau)
>    4. Re: Plasma taking 30% of CPU (Tom Albers)
>    5. Re: Completion of error handling (Markus Elfring)
>    6. Re: KDE Development with Mono/C# (Matias Valdenegro T.)
>    7. Re: KDE Development with Mono/C# (Benoit Jacob)
>    8. Re: How should I fix this KJots bug/wish (Matthew Woehlke)
>    9. Re: How should I fix this KJots bug/wish (Stephen Kelly)
>   10. Re: KDE Development with Mono/C# (Michael Howell)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 1 Dec 2008 15:56:58 +0100
> From: Flavio Castelli <flavio@castelli.name>
> Subject: Re: [PATCH] kdirwatch can not detect link change quite well
> To: kde-devel@kde.org
> Message-ID: <200812011556.58851.flavio@castelli.name>
> Content-Type: text/plain;  charset="us-ascii"
>
> On Sunday 30 November 2008 18:35:43 sycao wrote:
>   
>> Hi, all, I sent a patch a few days ago, I wonder if anyone is taking
>> care of KDirWatch,
>> or is it out of maintainment?
>>     
> I don't know if I can call myself the official KDirWatch maintainer, but in 
> the last time I've done some work on it (reviewing patches, bugs,...)
>
> Thanks for your patch, I'll review it asap.
>
> Flavio
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 1 Dec 2008 18:07:52 +0100
> From: Arno Rehn <kde-devel@arnorehn.de>
> Subject: Re: KDE Development with Mono/C#
> To: kde-devel@kde.org
> Message-ID: <200812011807.53034.kde-devel@arnorehn.de>
> Content-Type: text/plain;  charset="iso-8859-1"
>
>   
>> Well, but the original question was why C# isn't used in KDE, and I
>> think I gave my answer: because most programmer do not see the point
>> in that.
>>
>> What is the C# feature KDE can't do without?
>>     
> Getting Plasmoids with Get Hot New Stuff. Each C++ plasmoid you download, you 
> have to compile on your specific distribution or hope someone built a package 
> for it. C# (and all the scripting languages) are platform independent, so it's 
> possible to get them with Get Hot New Stuff (which will make most of the users 
> that aren't familiar with compiling stuff happy :))
>
>   
KDE , Linux and open source are not just about technology. Equally
importantly, they are about ideas. The main idea would be 'to release
the source code so that others can work on it if they want, make changes
on it if needed, and collaborate'.
But besides, the freedom of opensource also is, for a lot of people,
about things like the absurd of software patents. Can anyone be
completely sure that putting mono inside KDE is not going to bring
patents-related issues in the future?
I don't think so. I think that it'd never be an issue, but I can't be
completely sure.

There is people complaining about how Gnome is getting sorta interweaved
with mono. So far, there'd be no problem getting a mono-free Gnome
desktop in your computer... but the situation could be moving on fast
towards a Gnome mono-ized desktop,  helped by Novell and de Icaza.

And that's sad because you can't be sure that mono wont be a patent
issue next year, or the other. And, if I'm right, Novell and M$ signed
an agreement which would allow Novell to use a mono-'enhanced' system,
but not every other distro.
What is the point on even worry about mono and c# being binded on kde?.

Don't get me wrong, I do use c# and .Net (at my job) and I like them. I
do like technology. But also, I don't like bad people and bad bully-like
strategies (which is what microsoft is about lately).

I like .net, but I want opensource to be free. Even if I can't use mono
on it. No problem. I like c++, ruby, python, or whatever else I'd need
to use.

Please note that this is no place to defend points of view like 'in my
opinion, c# has been standardized via ecma and is pretty safe of patent
issues'. There is a lot of different opinions on the subject, which
means there is a lot of uncertainty... And you can't build KDE based on
uncertainty. You can't develop any open source software when you can't
be sure whether one day you'll have to throw it all away because it
turned out that it wasn't patent free stuff.

And BTW, this is, in my opinion, the bad thing about Novell, Icaza,
Gnome, Novell's efforts to OOXML and bad standard organizations like
ISO. The whole thing is messing up the open source ecosystems.
Reason enough to keep KDE mono-free.

Cheers




 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]