Home Messages Index
[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index

[News] K Desktop Environment Over 4 Million LOCs Just for Core

  • Subject: [News] K Desktop Environment Over 4 Million LOCs Just for Core
  • From: Roy Schestowitz <newsgroups@xxxxxxxxxxxxxxx>
  • Date: Mon, 12 Oct 2009 20:32:55 +0100
  • Followup-to: comp.os.linux.advocacy
  • Newsgroups: comp.os.linux.advocacy
  • User-agent: KNode/4.3.1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

4,273,291 lines of code

,----[  ]
| 4,273,291 lines of code, that's the size of 
| the KDE core modules, which are released as 
| the official KDE software distribution, as 
| of today, the numbers generated using David 
| A. Wheeler's SLOCCount. 
`----

http://blog.cornelius-schumacher.de/2009/10/4273291-lines-of-code.html

The Two Elephant Problem

,----[ Quote ]
| There are a number of strategies to 
| approaching the two elephant problem. The 
| "push the new elephant in, in one go" 
| approach is the most radical and 
| disruptive. A new version of the project is 
| presented to the community, complete and 
| ready to roll, and it is up to the 
| community to accept the changes. The danger 
| for the project though is that the first 
| elephant may decide to leave. This was the 
| approach taken by the KDE developers when 
| they committed to creating KDE 4.0. The 
| backlash saw many users sit back on older 
| versions of KDE or look for alternative 
| desktops. It is only now, after a number of 
| subsequent releases, that KDE is winning 
| back friends.
| 
| Another approach is to mitigate the 
| disruption by disassembling the new 
| elephant and introduce it bit by bit into 
| the room, with the hope that the community 
| will adopt the new elephant parts as their 
| own. The problem with this approach is that 
| it is very hard to disassemble elephants, 
| let alone reassemble them, and any vision 
| for the new version may not survive the 
| rebuilding process. A Frankenstein elephant 
| may work, but the elegance of the original 
| plans could well be lost and new parts may 
| well be rejected. This is partly the 
| approach of the GNOME developers, who have 
| delivered a preview version of the GNOME 
| Shell, a highlight of the proposed GNOME 
| 3.0, in version 2.28. According to some 
| reports, this is a hard to get working 
| preview and as such the effort to get it 
| running may outweigh the benefits of the 
| early preview. 
`----

http://www.h-online.com/open/The-Two-Elephant-Problem--/features/114441


Recent:

KDE 4.3: Boom baby!

,----[ Quote ]
| Stability has gradually improved to the point where
| I no longer have any problems at all. KDE boots
| fast and without issue. Applications donât crash,
| except for the printer applet after one update,
| which was immediately remedied in the next. Kwin
| effects are fast and leave no artifacts. KDE 4 is
| stable.
|
| Configuration-wise, things have improved too.
| Config options have treacled back into KDE 4, and
| while it still might not be up to the standard set
| by its predecessor, itâs getting there.
`----

http://celettu.wordpress.com/2009/10/10/kde-4-3-boom-baby/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkrThGgACgkQU4xAY3RXLo6cawCfZMFc8rz0cwb9+atWNPbLCdCd
QZUAnAlP2ZQokfjwO7K+KefU/bW7Al6T
=eta9
-----END PGP SIGNATURE-----

[Date Prev][Date Next][Thread Prev][Thread Next]
Author IndexDate IndexThread Index