| 1 |
Apparently, though unproven, at 17:06 on Wednesday 11 May 2011, Indi did opine |
| 2 |
thusly: |
| 3 |
|
| 4 |
> On Wed, May 11, 2011 at 04:50:02PM +0200, Alan McKinnon wrote: |
| 5 |
> > It uses hardly any cpu at all, regardless of what the naysayers say. |
| 6 |
> |
| 7 |
> Well, add me to the "naysayers" list then, because my experience directly |
| 8 |
> contradicts that statement. Much happier with fluxbox, completely finished |
| 9 |
> fooling with the kde. |
| 10 |
|
| 11 |
semantic desktop equates to nepomuk |
| 12 |
|
| 13 |
If you do something really thick with the backend (virtuoso currently) it will |
| 14 |
go beserk. Full strigi indexing will keep your disk busy all day - what else |
| 15 |
could it do if you want a full text indexed search of 300GB of file in ~ like |
| 16 |
many users have these days? |
| 17 |
|
| 18 |
> I still don't understand why the kde folks went from something that |
| 19 |
> worked extremely well to their current state. Baffling. |
| 20 |
|
| 21 |
KDE3 and KDE4 are not the same thing. |
| 22 |
KDE4 is not the next version of KDE3. |
| 23 |
|
| 24 |
You must consider KDE4 to be a completely new product, unrelated to KDE3 in |
| 25 |
any meaningful way except that many KDE4 devs used to work on a different |
| 26 |
project called KDE3. |
| 27 |
|
| 28 |
Like all software, KDE4 is not for everyone - like you for example. But |
| 29 |
there's nothing stopping you from maintaining KDE3 yourself. |
| 30 |
|
| 31 |
Why did the devs switch? Market pressures really. If you don't spot emerging |
| 32 |
trends and follow them early, you run the risk of becoming redundant very |
| 33 |
quickly. Ask Microsoft, they know all about this. |
| 34 |
|
| 35 |
They went from the undisputed behemoth market leader to staring the very real |
| 36 |
threat of total obsolescence in three very short years. |
| 37 |
|
| 38 |
KDE devs decided to take the risk and make the jump ahead of the curve. |
| 39 |
|
| 40 |
-- |
| 41 |
alan dot mckinnon at gmail dot com |
Archives