It's not inconsistent to complain about the evils of the MPAA or RIAA then go buy a DVD or a CD. Saying you think a group is evil doesn't oblige you to boycott that group.
Boycott isn't the only effective means of attack, and boycott itself isn't effective unless enough people are doing it. So, the first step is to educate the public about what the MPAA or RIAA is doing wrong. For example, I'd told my father many times about the region locking of DVDs, but it only hit home with him and really annoyed him when I demonstrated for him that he couldn't play my Region 2 Majo no Takkyuubin (Kiki's Delivery Service), showing him that the manufactuers decided that this DVD that I bought was not allowed to be played where I wanted, and that laws had been passed making it illegal to take the steps I took to work around that.
Then, once there are enough people who know and get mad, *then* call for a boycott when it'll make a difference, and limited enough that people will have the willpower to hold up to it (remember, after all, that the people who care enough to take part, and the people whose taking part will be noticed, are those who regularly by DVDs!). Perhaps boycott DVDs for the period from Thanksgiving to December 26 (by far the biggest retail sales period in the US), or pick one company's releases to boycott (AOL maybe?).
Just boycotting every corporation that has an association with something you don't like would just deprive yourself, usually.
Patrick won't use bzip2 because it's too resource-hungry for the very low-end that slackware still supports, and also he claims that the difference at gzip -9 vs bzip2 -9 isn't enough to make it worthwhile anyway.
Konqueror relies on all sorts of KDE services. Konqueror uses every part of kdelibs if you have the audio previewing on. Konqueror simply won't work unless you have the rest of KDE installed.
KDE 3 is be faster than KDE 2. Qt has been optimized, KDE has been optimized. Memory use has ben reduced where possible, bottlenecks have been traced and improved. And of course you should compile correctly:
For Qt, get the objprelink patch if necessary, edit mkspecs/(your platform)/qmake.conf to change the line QMAKE_CFLAGS_RELEASE.
Perhaps the Brahms developers should ask for the kmusic package to be added to the released packages for KDE 3.1. Brahms is in cvs, in kmusic. kmusic just needs to be released.
The *first step* was to port to Qt 3, *then* the new features began. This was said all along. It'd be idiotic not to add features during a rare decision to break binary compatibility.
KDE also validated its C++ so that gcc 3 will work. However, gcc 3.0.x has bugs that sometimes cause parts of KDE (especially aRts) to fail to compile correctly. KDE can't fix that.
* Yup, plenty of people do get annoyed with me. But is that in itself a bad thing? I'm reminded of the Peter Principle, in the part where it's shown how bad processes get reinforced when those who make waves are tossed out.
* Yup, I criticize things. I also beg for my work to get tested and criticized. What I *don't* like are vague criticisms with no hint about what to *do* about them. My criticisms on the matter of KDE 3.0 have not been vague, and certainly have included suggestions on what to *do* about them, even including my volunteering to handle it myself the next time around.
* Microsoft is irrelevant to KDE.
* Sabotage? I botched one import, which briefly cluttered kdemultimedia with an extra dir before Dirk fixed it. Yes, the same Dirk. Yes, I apologized for the error. Sabotage usually implies that something breaks. I broke nothing.
* Lead KDE? Well, yes I said leader. When it's used in this manner, maybe leader was the wrong word. You need the context - when the RC proposes a schedule, anyone and everyone comments on how it can be improved, and it's the developers collectively who make the decisions. The RC just enforces the decisions that everyone else made.
* Agenda to cripple KDE? I'm sorry, I just can't answer that one. I don't know where to begin.
I just compiled kgamma ( a KDE 2 kcontrol module ) for KDE 3, and it took no source changes, just a switch to the KDE 3 admin directory.
The biggest change needed to port this time are
perl -pi -e "s,QList,QPtrList,g" *.cpp *.h
KDE 3 isn't the radical jump that KDE 2 was. Porting isn't hard. And there's a nice large doc in the kdelibs sources describing the changes from 2 to 3 in kdelibs.
Now I'm going to have to start looking through your past posts to figure out just who you are. From the name I have to guess you're one of the dot.kde.org editors, but I'm not sure.
bzzzzzzzzzzzzzt. KDE 3.0 is *not* in beta. It has passed the beta stage, at least officially. It is a release candidate, which is something that is supposed to be release worthy.
Don't believe me? Before the Nuernberg meeting, the schedule had KDE 3.0 final coming out just a few days after RC 1. That's how bad a failure RC 1 was.
No, GNOME really hasn't improved KDE much, except for where certain formats got standardized for cooperationg with GNOME. I doubt KDE has influenced GNOME much either, especially since they're using Gecko now instead of the khtmlw-based html renderer.
KDE developers, and probably GNOME developers, don't care about the other environment usually. It's not a positive influence, it's not a negative one. It's not an influence *at all*.
If you send GNOME-related stuff to kde-devel you're just going to get told to go elsewhere, or ignored.
What irks me is that previous versions of LSB kept assuring us that rpm was an interim standard, until a vendor-neutral LSB binary package format could be designed. A new format that would learn from Red Hat, Debian, FreeBSD, and everyone else.
Now they took the cheap route and just used rpm.
I guess this is good, though. I never liked the LSB, and the LSB isn't going anywhere without Debian, and Debian's not going anywhere without their packages.
College, hard? Explain to me then how so many manage to squeak by drunk then?
It *can* be hard, but it doesn't have to be hard. The only way to actually know the value of a particular degree is to know the school and to see the transcript. The piece of paper, the letters after the name, mean nothing in themselves. That's the problem.
The GPL is not the embodiment of Free, it is the canonical example of Copyleft.
Many people miss this point. Free software is software without restrictions. Copylefted software is software that requires derived works to be free software.
RMS will tell you that the Free in FreeBSD is accurate, but he'll probably follow it up by mentioning his view that Copylefted software protects the community.
The concept of free software is simple. It's only the copyleft that makes the GPL so complicated.
...the use of the word 'free' has been unfortunate...
It's apropriate that you should write this on the very day freekde.org launches. This illustrates just how wide a range of viewpoints there is in the KDE community, and proves the need for my new site.:-)
Slashdot Mirror
It's not inconsistent to complain about the evils of the MPAA or RIAA then go buy a DVD or a CD. Saying you think a group is evil doesn't oblige you to boycott that group.
Boycott isn't the only effective means of attack, and boycott itself isn't effective unless enough people are doing it. So, the first step is to educate the public about what the MPAA or RIAA is doing wrong. For example, I'd told my father many times about the region locking of DVDs, but it only hit home with him and really annoyed him when I demonstrated for him that he couldn't play my Region 2 Majo no Takkyuubin (Kiki's Delivery Service), showing him that the manufactuers decided that this DVD that I bought was not allowed to be played where I wanted, and that laws had been passed making it illegal to take the steps I took to work around that.
Then, once there are enough people who know and get mad, *then* call for a boycott when it'll make a difference, and limited enough that people will have the willpower to hold up to it (remember, after all, that the people who care enough to take part, and the people whose taking part will be noticed, are those who regularly by DVDs!). Perhaps boycott DVDs for the period from Thanksgiving to December 26 (by far the biggest retail sales period in the US), or pick one company's releases to boycott (AOL maybe?).
Just boycotting every corporation that has an association with something you don't like would just deprive yourself, usually.
This is a slackware FAQ.
Patrick won't use bzip2 because it's too resource-hungry for the very low-end that slackware still supports, and also he claims that the difference at gzip -9 vs bzip2 -9 isn't enough to make it worthwhile anyway.
Konqueror has given the ability to add fake protocols for a year and a half now. I can enter gg:blah to search google for blah, for example.
No you can't.
Konqueror relies on all sorts of KDE services. Konqueror uses every part of kdelibs if you have the audio previewing on. Konqueror simply won't work unless you have the rest of KDE installed.
In case you weren't aware: http://www.kde.org/packagepolicy.html
KDE 3 is be faster than KDE 2. Qt has been optimized, KDE has been optimized. Memory use has ben reduced where possible, bottlenecks have been traced and improved. And of course you should compile correctly:
For Qt, get the objprelink patch if necessary, edit mkspecs/(your platform)/qmake.conf to change the line QMAKE_CFLAGS_RELEASE.
For KDE, configure correctly:
CXX="g++ -fstrict-aliasing -mpentiumpro -O3 -malign-functions=4" CC="gcc -fstrict-aliasing -mpentiumpro -O3 -malign-functions=4" configure --disable-debug --enable-final --enable-fast-malloc=full --enable-objprelink
(remove --enable-objprelink if you're using the latest GNU binutils)
KDE 3.0 will not include Brahms.
Perhaps the Brahms developers should ask for the kmusic package to be added to the released packages for KDE 3.1. Brahms is in cvs, in kmusic. kmusic just needs to be released.
You don't know what you're talking about, do you?
The *first step* was to port to Qt 3, *then* the new features began. This was said all along. It'd be idiotic not to add features during a rare decision to break binary compatibility.
KDE also validated its C++ so that gcc 3 will work. However, gcc 3.0.x has bugs that sometimes cause parts of KDE (especially aRts) to fail to compile correctly. KDE can't fix that.
*raise the scimitar*
* Yup, plenty of people do get annoyed with me. But is that in itself a bad thing? I'm reminded of the Peter Principle, in the part where it's shown how bad processes get reinforced when those who make waves are tossed out.
* Yup, I criticize things. I also beg for my work to get tested and criticized. What I *don't* like are vague criticisms with no hint about what to *do* about them. My criticisms on the matter of KDE 3.0 have not been vague, and certainly have included suggestions on what to *do* about them, even including my volunteering to handle it myself the next time around.
* Microsoft is irrelevant to KDE.
* Sabotage? I botched one import, which briefly cluttered kdemultimedia with an extra dir before Dirk fixed it. Yes, the same Dirk. Yes, I apologized for the error. Sabotage usually implies that something breaks. I broke nothing.
* Lead KDE? Well, yes I said leader. When it's used in this manner, maybe leader was the wrong word. You need the context - when the RC proposes a schedule, anyone and everyone comments on how it can be improved, and it's the developers collectively who make the decisions. The RC just enforces the decisions that everyone else made.
* Agenda to cripple KDE? I'm sorry, I just can't answer that one. I don't know where to begin.
Well, I was close. He runs a website, just not dot.kde.org.
:-)
Maybe I owe an apology to Dre, Navindra, and the rest.
I just compiled kgamma ( a KDE 2 kcontrol module ) for KDE 3, and it took no source changes, just a switch to the KDE 3 admin directory.
The biggest change needed to port this time are
perl -pi -e "s,QList,QPtrList,g" *.cpp *.h
KDE 3 isn't the radical jump that KDE 2 was. Porting isn't hard. And there's a nice large doc in the kdelibs sources describing the changes from 2 to 3 in kdelibs.
Neil here,
What post are you talking about?
Now I'm going to have to start looking through your past posts to figure out just who you are. From the name I have to guess you're one of the dot.kde.org editors, but I'm not sure.
Neil here,
bzzzzzzzzzzzzzt. KDE 3.0 is *not* in beta. It has passed the beta stage, at least officially. It is a release candidate, which is something that is supposed to be release worthy.
Don't believe me? Before the Nuernberg meeting, the schedule had KDE 3.0 final coming out just a few days after RC 1. That's how bad a failure RC 1 was.
Neil here,
:-)
Well, the vote of no confidence won't come on Dirk until after 3.0 is out, for better or worse.
Question is, which one of Ryan, Charles, and myself is Padme?
Sure you can.
It has a NIC. It has a Hard Drive. What more do you neeD?
No, GNOME really hasn't improved KDE much, except for where certain formats got standardized for cooperationg with GNOME. I doubt KDE has influenced GNOME much either, especially since they're using Gecko now instead of the khtmlw-based html renderer.
KDE developers, and probably GNOME developers, don't care about the other environment usually. It's not a positive influence, it's not a negative one. It's not an influence *at all*.
If you send GNOME-related stuff to kde-devel you're just going to get told to go elsewhere, or ignored.
What next, UCLA is rally the University of Central Louisiana? MIT is the Michigan Institute of Technology? CMU is Collge of Medicine of Utah? :-)
So what do we need FHS for if we can just do "which filename"?
What irks me is that previous versions of LSB kept assuring us that rpm was an interim standard, until a vendor-neutral LSB binary package format could be designed. A new format that would learn from Red Hat, Debian, FreeBSD, and everyone else.
Now they took the cheap route and just used rpm.
I guess this is good, though. I never liked the LSB, and the LSB isn't going anywhere without Debian, and Debian's not going anywhere without their packages.
College, hard? Explain to me then how so many manage to squeak by drunk then?
It *can* be hard, but it doesn't have to be hard. The only way to actually know the value of a particular degree is to know the school and to see the transcript. The piece of paper, the letters after the name, mean nothing in themselves. That's the problem.
The GPL is not the embodiment of Free, it is the canonical example of Copyleft.
Many people miss this point. Free software is software without restrictions. Copylefted software is software that requires derived works to be free software.
RMS will tell you that the Free in FreeBSD is accurate, but he'll probably follow it up by mentioning his view that Copylefted software protects the community.
The concept of free software is simple. It's only the copyleft that makes the GPL so complicated.
It's apropriate that you should write this on the very day freekde.org launches. This illustrates just how wide a range of viewpoints there is in the KDE community, and proves the need for my new site. :-)
User Agent configurability exists in KDE 2.1 as well.
Thank you for playing.
1) TT has hired several KDE developers, who continue to do much for KDE.
:-)
2) TT entered into the Free Qt foundation, before the FSF had convinced their lawyers that the GPL was safe for them.
3) TT employees have given tons of free support to KDE developers.
4) Hosting www.kde.org
About the only thing they haven't done for KDE is clone David Faure.
Wrong subject in the earlier post, but you figured that out.