LWN: Comments on "Did Linus Jump Too Soon? (Linux Journal)" https://lwn.net/Articles/317407/ This is a special feed containing comments posted to the individual LWN article titled "Did Linus Jump Too Soon? (Linux Journal)". en-us Thu, 11 Sep 2025 13:42:41 +0000 Thu, 11 Sep 2025 13:42:41 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/318334/ https://lwn.net/Articles/318334/ mjthayer <div class="FormattedComment"> I have actually looked at GoboLinux before. They certainly take a good shot at structuring a Linux filesystem like OS X or NextStep. It is still not quite good enough for me though :) I think what I would really like would be something that would fit in well to existing Linux systems, rather than trying to start afresh (that always feels nicer, but is usually doomed to remain a niche). Fitting in with existing systems would of course require a lot of thought, much talk, many compromises and a delicate sense for diplomacy. And of course GoboLinux just look at this from a filesystem point of view. Other things, such as process management, system configuration and service management could also do with some restructuring. Unfortunately, we don't have something as nice as OS X's filesystem to copy here :)<br> </div> Fri, 06 Feb 2009 08:31:58 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/318258/ https://lwn.net/Articles/318258/ DarthCthulhu <div class="FormattedComment"> "To tell the truth, what I would love would be a desktop system that is easy to use because it is well structured, not because it hides things from the user."<br> <p> You might want to look at GoboLinux (<a href="http://www.gobolinux.org/">http://www.gobolinux.org/</a>).<br> <p> It's a distro with a completely reorganized file system tree that is MUCH better than the old *NIX way. The best part is, through symlink magic, you can still look at the filesystem in a legacy way if you (or any processes) want to. Everything works really nicely and there's no need for complicated repositories; adding or removing software is done via "recipes" which are simple scripts. If necessary, you can even just manually add or delete things... the recipes are just nice helpful things which make setting and unsetting the various symlink magic easier.<br> </div> Thu, 05 Feb 2009 19:51:58 +0000 decision for community https://lwn.net/Articles/318034/ https://lwn.net/Articles/318034/ Arker <p>I didnt call it 'crap' and I didnt sling any mud. Just straight up observations from an interested party (a KDE user who's been using Free Software and boosting for it since '94.) </p> <p>While your explanation for what happened makes sense, it doesnt make the KDE developer community look any better. What you're saying is that you have to mislabel your development releases to get developers to work on them. I'm very sad to hear that. I can't help but think that your first goal should be to back up a bit and work on the flawed assumptions behind the response. Developers shouldnt have any problem working on alpha/beta releases - another name for them is 'Developers releases' after all. </p> Thu, 05 Feb 2009 05:30:07 +0000 Linus - New Interview More Good Copy https://lwn.net/Articles/317884/ https://lwn.net/Articles/317884/ jospoortvliet <div class="FormattedComment"> Well, fedora has reasons to do what they do - they want to advance the state of FOSS, and by pushing they latest &amp; greatest they hope to do that. You can agree or disagree with that strategy but as long as users make a clear decision to join that or not, I think it's OK.<br> <p> I agree I wouldn't use it either, btw, but that's not the point.<br> </div> Wed, 04 Feb 2009 13:56:13 +0000 Linus - New Interview More Good Copy https://lwn.net/Articles/317835/ https://lwn.net/Articles/317835/ Arker <div class="FormattedComment"> One more good reason to avoid Fedora like the plague. <br> <p> I'll probably never understand why anyone would use it, but meh, his choice. <br> </div> Wed, 04 Feb 2009 00:57:58 +0000 decision for community https://lwn.net/Articles/317734/ https://lwn.net/Articles/317734/ sebas <div class="FormattedComment"> The "borked" versioning you describe has everything to do with the overall<br> quality of KDE at the point of 4.0. Here's my personal, frank analysis of<br> it:<br> <p> - Most of KDE 4 was ready for a sensible .0 release at that time<br> - Plasma was lacking features and stability at that point<br> - The decision to ship KDE 4.0 was a decision for the community and had<br> relatively little to do with users<br> <p> So what happened then? Plasma, being the most visible component in the<br> desktop was of course immediately found to be lacking. Interpolation made<br> that a "KDE 4 is crap" (note how both the state of most applications, the<br> development platform and the fact that 4.0 is the kick-off for the new<br> KDE4) is ignoredin this. This is from a user's point of view.<br> <p> From a community point of view (which almost nobody seems to think about<br> unfortunately), in 2007, one of the biggest problems was to get the<br> community onto KDE4, to start porting apps, to stop tinkering with<br> technology and to make KDE4 releasable, this is commonly called "release<br> mode", and it was one of our biggest challenges from changing the pillars<br> into an integrated whole. We started releasing Alphas, Betas<br> and RCs then, and it indeed worked. Our people understood that KDE4.0 was<br> to be released soon and got on it, started porting apps, worked on fixing<br> bugs and polishing. Our people got into this release mode and have been<br> frantically fixing KDE4 for months. Some modules, for example the KDE games<br> module, but also KDE Edu release-quality well before 4.0, others were<br> slower. Plasma is one of those slower components. It had been started quite<br> late in the process, mostly because we needed some stuff fixed in Qt, and<br> because it would layer on top of almost anything else so technically, it<br> *had* te be done last.<br> At some point though, we would have to release KDE 4.0 (you cannot warn<br> forever, you cannot keep people in frantic release mode forever), and we<br> decided to do it although Plasma wasn't ready for prime time -- it was<br> basically usable though (i.e. I could run an editor, a konsole and some<br> other programs, even if it wasn't the most fancy thing<br> around). It also happened to run stable, so I assume it was at least good<br> enough for some people. It would have been unfair to non-Plasma developers<br> (which there are quite a lot within KDE) to hold everything back until<br> Plasma is good enough for $group_of_users, and it would've held back other<br> processes, such as the move to KDE4 among 3rd party KDE apps, fixing of<br> issues in Xorg, various video drivers, and other components throughout the<br> stack.<br> <p> So did that work? I would say yes. The KDE4 frameworks are quickly<br> maturing, we're seeing KDE3 apps being ported all over (with the more<br> complex ones such as Amarok, KDEnlive having their first KDE4 release and<br> others such as Digikam, and K3b nearing readiness. The number of commits<br> as well as the number of hackers on our codebase is steadily increasing,<br> and many other things in our community making sure we'll scale well in the<br> coming years. So 2008 has been a very good year for KDE, despite all the<br> complaining.<br> <p> How did we deal with the 4.0-backlash? This is in my opinion an important<br> point, because it says a lot about how we deal with feedback. What indeed<br> happened is that many people (especially inside the Plasma team) put aside<br> their grand plans in order to work on things that users were missing in KDE<br> 4.0 compared to KDE 3.5. This is mostly completed with KDE 4.2<br> <p> So the trick users into testing is a quite superficial analysis, and simply<br> not true. It has been a decision that largely underestimated how users<br> would react. We did assume our messaging was fine, reflecting our pride of<br> having gotten something as big as 4.0 out, and even thought users were more<br> sensible and would "get" it. That's obviously at least for a very vocal<br> group not true.<br> <p> <p> While you can have any opinion you want on the 4.0 release, repeating that<br> 4.0 was crap deceiving is only part of the truth, and not the forward-<br> innovation and "balls" are not appreciated, and that you'll burn yourself<br> with those "great plans". I'm personally glad that most KDE developers keep<br> working despite this mudslinging, and I'm confident that the way KDE4 is<br> going shows its promise to more and more users.<br> </div> Tue, 03 Feb 2009 14:48:07 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317730/ https://lwn.net/Articles/317730/ mjthayer <div class="FormattedComment"> As I said, I wasn't making an argument that Apple's AppFolder concept is appropriate for Linux (although I'm not saying it couldn't be either, in a sufficiently rethought-out form :) ). It was just an example of how a user interface can present things simply without dumbing down the user - in effect the complexity is layered, and you can go down a layer if you need to take a deeper look. Whether the same principle of layering the interface and the complexity could be made to work in other situations, like controlling system services or components of the sound system or kded (whatever that is - it has died on me too, but I also never quite understood what that meant...) or whatever, I don't know.<br> </div> Tue, 03 Feb 2009 14:13:32 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317722/ https://lwn.net/Articles/317722/ jospoortvliet <div class="FormattedComment"> Of course my comment was as much targeting the parent of yours than your own comment. I disagree with your statement about cautious versioning (I don't see a big diff between FOSS and proprietary versioning, I even think proprietary software is generally a bit more cautious), and you can't disagree that the parent was pretty - unfriendly.<br> <p> Then again, maybe I shouldn't respond like that. It's just that I've been writing extensive responses to flamy posts like the parent of your comment for what, a year now? Sometimes one gets tired of answering the same uninformed questions again and again.<br> </div> Tue, 03 Feb 2009 12:16:52 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317719/ https://lwn.net/Articles/317719/ dlang <div class="FormattedComment"> a large part of this is the multi-user heritage that Unix has (and Linux inherits)<br> <p> part of this heritage is that a given app should only need to be installed on a system once, and there should be a set of system-wide defaults.<br> <p> while there is defiantly a place for single-user focused setups nowdays, the vast majority of *nix systems out there are still structured for multiple users. so any distro trying to do something different will be faced with a large body of existing code that won't do things the 'new way', and any software trying to package itself in the 'new way' will have to decide how to work on all the existing distros that work the 'old way'. trying to work on a system that had some packages one way and some the other could be far worse than either by itself.<br> <p> And while many geeks have at lest one system per user nowdays, the 'average home system' benefits enough from multiple users that new systems (including windows) are putting more emphasis on supporting multiple users than they have in the recent past<br> <p> I don't use OS-X, so I don't know how it deals with these issues (other than the fact that it doesn't bother with compatibility with anything else)<br> </div> Tue, 03 Feb 2009 11:51:37 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317718/ https://lwn.net/Articles/317718/ dlang <div class="FormattedComment"> to be fair you did make your comment in a thread primarily about the KDE 4.0 release. it would be hard to take your comment as anything other than further criticism about that release in this context.<br> <p> for those who are continueing to bash the KDE 4.0 release a year later, please provide the time machine so thta the KDE developers can go back and fix it, since it seems apparent that nothing else will satisfy many of you.<br> <p> note tht I am not a KDE developer, I'm a user who has been using KDE4 for a fair chunk of the past year and, while I have seen things that were nice when I used 3.5, I still choose 4.x over gnome when forced to use one or the other.<br> </div> Tue, 03 Feb 2009 11:37:50 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317716/ https://lwn.net/Articles/317716/ mjthayer <div class="FormattedComment"> To tell the truth, what I would love would be a desktop system that is easy to use because it is well structured, not because it hides things from the user. A case in point - compare applications on OS X to applications on a Linux distro. The OS X ones are organised as a single directory containing all files needed for the application. The user sees that directory in their file browser, clicks on it and the application starts. They can remove it by deleting the directory. If they need to "look inside", they can open the directory instead of just starting the application. On a Linux system, the applications are scattered through the /usr tree, which most desktops hide as far away from the user as possible. The user is shown an icon in the start menu which represents that collection of scattered files, and can remove the application by searching for it in the package manager. Quite a difference.<br> <p> Disclaimer: that was meant as an illustration of a point, not to say that Linuxes should be using AppFolders (they wouldn't easily fit into the Linux world for a variety of reasons) or that Apple does everything right.<br> </div> Tue, 03 Feb 2009 11:26:45 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317715/ https://lwn.net/Articles/317715/ cantsin <div class="FormattedComment"> I would prefer if you reserved your kind of response to forums like<br> Slashdot. In the posting you replied to, I did not mention KDE at all, but<br> just made a general observation about a tradition and more recent practices<br> of versioning schemes in free software. - Since you are apparently a KDE<br> developer, you are not helping your project, but on the contrary reinforce<br> a perception that it has communication issues. <br> </div> Tue, 03 Feb 2009 11:21:08 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317709/ https://lwn.net/Articles/317709/ jospoortvliet <div class="FormattedComment"> Oeh, yeah, you're so right. All foss software uses numbering schemes like Wine and Google. And KDE 4.0 was only released to trick users into testing it (so we could ignore the bugreports and make fun of them).<br> </div> Tue, 03 Feb 2009 09:12:38 +0000 Linus - New Interview More Good Copy https://lwn.net/Articles/317708/ https://lwn.net/Articles/317708/ jospoortvliet <div class="FormattedComment"> He did say he uses fedora, right? That's the issue, fedora forced KDE 4.0 on its users by not providing 3.5.x packages.<br> </div> Tue, 03 Feb 2009 09:10:46 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317706/ https://lwn.net/Articles/317706/ cantsin It should be added that Free Software traditionally has a quality reputation for cautious version numbering schemes. Fine programs like mutt carried 0. version numbers for years. Even today, mplayer, elinks, aspell and inkscape, for example, haven't reached 1.0 yet. In the world of (proprietary) web applications, Google is setting a high standard by calling perfectly usable service "beta". It would be sad if Free Software traded these quality standards for those that are rather typical for the "Shareware" cultures of Windows and Mac OS. Tue, 03 Feb 2009 08:26:59 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317702/ https://lwn.net/Articles/317702/ b7j0c <div class="FormattedComment"> journalists love crap like this because its easier than writing a real article. just take something noteworthy from the echo-chamber, throw some cheap contrarianism on it (i.e., linus is wrong), and voila, instant pageview fodder.<br> </div> Tue, 03 Feb 2009 05:07:42 +0000 Linus - New Interview More Good Copy https://lwn.net/Articles/317694/ https://lwn.net/Articles/317694/ Arker <div class="FormattedComment"> The GNOME mentality is bloody annoying, I agree. <br> <p> But KDE 3.5.10 is still very usable. Why not just stick with that until KDE 4 is ready? <br> </div> Tue, 03 Feb 2009 01:42:09 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317693/ https://lwn.net/Articles/317693/ Arker <div class="FormattedComment"> The problem is that your versioning system is borked. 4.0 was, at best, a beta release (and by some opinions alpha.) A .0 release, unless you're MicroSoft, is understood to NOT be a beta release. What was released as 4.2 should have been labeled 4.0rc1. By adopting deceptive, MS-like versioning numbers you set yourself up for massive backlash, which materialised on schedule. <br> <p> At the same time, distributors should have caught this and for the most part did not (Slackware being one exception, I think I heard SuSE was another.) In Linus' case, he inexplicably insists on running Fedora. Fedora promptly replaced stable KDE with alpha-beta releases, whether in keeping with their philosophy as a 'test-bed' distro or out of confusion engendered by the deceptive version numbers mentioned above I dont know. Whatever the motivation, the outcome was the same - he found stable usable KDE replaced with mislabeled alpha-beta level new KDE and had to switch to something that worked. That something just happened to be Gnome. <br> <p> This can be addressed at two levels. You (throughout this post I'm using 'you' to refer to you as a KDE developer, and more broadly to you as KDE Developers collectively) can and should reverse this policy of using a marketing versioning scheme and go back to something that accurately describes the release. You can also try to lobby distributions to quit screwing up. I suspect you'll have more luck with the former than the latter. <br> <p> <p> </div> Tue, 03 Feb 2009 01:36:04 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317650/ https://lwn.net/Articles/317650/ dkite <div class="FormattedComment"> You must live somewhere warm.<br> <p> Go outside is the difficult part around here. I want to know if I want to go outside.<br> <p> Derek (who looks that his home thermostat with outdoor sensor to make such decisions)<br> </div> Mon, 02 Feb 2009 21:03:05 +0000 WWLD? (was: Did Linus Jump Too Soon?) https://lwn.net/Articles/317547/ https://lwn.net/Articles/317547/ tnoo <div class="FormattedComment"> Try xmonad.<br> </div> Mon, 02 Feb 2009 11:59:39 +0000 Linus - New Interview More Good Copy https://lwn.net/Articles/317542/ https://lwn.net/Articles/317542/ roblucid <div class="FormattedComment"> <a href="http://distrowatch.com/weekly.php?issue=20090202">http://distrowatch.com/weekly.php?issue=20090202</a><br> <p> LT: Since I'm on Fedora, I got hit by the (bad) transition to KDE4, and as a result I've been using GNOME for the last year or so. It's still somewhat painful, more so when I'm on my laptop, mainly for the same old reason: you cannot fix the mouse buttons in GNOME. (The reason this hits me more on the laptop than anywhere else is that most laptops only have two buttons, making the middle-button press much harder. And middle button is what you need for the 'send to back' window action.)<br> <p> I wrote the patch (including even the graphical configuration management), I sent it in, and it got rejected as "too complicated for users". Frickin' idiots (and I'm not talking about those alleged users).<br> <p> But right now, KDE is worse. I'd like to explore alternatives, but if you've followed my answers this far and are perceptive, you'll probably already have figured out that the programs involved aren't on my list of things I care about that much.<br> <p> I'm well known for disliking GNOME, but it's not the "using it" part that I dislike as much as the apparent mentality of the GNOME people who think that all users are idiots and then limit what I can do with it for that reason.<br> </div> Mon, 02 Feb 2009 10:19:42 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317541/ https://lwn.net/Articles/317541/ janpla <div class="FormattedComment"> Does it lack that kind of things? I personally am glad to hear it.<br> <p> I recently changed away from GNOME for that very reason - what I do mostly on my computer is WORK, and I found that in GNOME, before I could work I'd have to get rid of a load of silly nonsense.<br> <p> What I like about KDE is that the developers don't seem to be bent on taking away features that are useful to people, even if it is only a minority. The GNOME people are too nannyish; they simplify things beyond what makes sense and want to tell users how to do their work.<br> </div> Mon, 02 Feb 2009 09:58:36 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317540/ https://lwn.net/Articles/317540/ janpla <div class="FormattedComment"> <font class="QuotedText">&gt; Presumably those people live in places where the weather is predictable</font><br> <p> Oh, come on, if you want to know about the weather, all you have to do is go outside or find a window. Primitive, I know, but it works.<br> </div> Mon, 02 Feb 2009 09:48:23 +0000 WWLD? (was: Did Linus Jump Too Soon?) https://lwn.net/Articles/317537/ https://lwn.net/Articles/317537/ debacle <div class="FormattedComment"> What would Linus do? I don't know and I don't care. I'm thinking about switching from XFCE4 to LXDE on my netbook. What would you do?<br> </div> Mon, 02 Feb 2009 09:33:04 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317527/ https://lwn.net/Articles/317527/ callegar <div class="FormattedComment"> On an updated Intrepid with latest kde 4.2 I get<br> <p> kbluetooth4<br> kbluetooth4(7927) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "BlueZ"<br> kbluetooth4(7927) Solid::Control::BluetoothManager::buildDeviceList: UBI List ("/org/bluez/hci0")<br> kbluetooth4(7927) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: findRegisteredBluetoothInterface "/org/bluez/hci0"<br> kbluetooth4(7927) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Creating New Interface "/org/bluez/hci0"<br> kbluetooth4(7927) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: Calling Backend to Creating New Interface "/org/bluez/hci0"<br> kbluetooth4(7927) Solid::Control::BluetoothManagerPrivate::findRegisteredBluetoothInterface: BackendIface created<br> kbluetooth4(7927) KBlueTray::onlineMode: online Mode<br> kbluetooth4: symbol lookup error: kbluetooth4: undefined symbol: _ZN5Solid7Control16BluetoothManager8securityERK7QString<br> kbluetooth4(7926): Communication problem with "kbluetooth4" , it probably crashed.<br> Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "<br> <p> Not that nice.<br> <p> Also, KDEPrint shows some printer options twice and the "kprinter" application is gone, so there can be no printer integration for legacy applications (e.g. no way to provide a dialog to change resolution or duplex mode on older X11 apps).<br> <p> My point is that while the desktop look is improving and its speed is reasonable, some hidden core functionality is somehow lacking attention and there is less information to understand what is going on behind the scenes, so it has become almost impossible to "play" with the platform and to understand what is going on when unexpected behavious arise (Kded dying with a "kded has aborted" is not very informative and there is no docs to find out what kded does at startup, what files it looks at, etc.). <br> <p> In latest times, a lot of activity has gone on wrt the desktop: new abstraction layers (solid, DBus), new ways of managing sound (pulseaudio, phonon), new DE paradigms (plasma). In all this there is an expectation that everything shuld just work, so that the user is not expected to know /how/ it does so. But one of the things that made old UNIX fun was the tons of man pages (every single command or config file had one) that let you understand what was going on.<br> <p> All in all you get a feeling that "you are loosing control", you just need to wait for new versions to come in and you cannot anymore adapt your toy to play nice with the legacy stuff that you still have around.<br> </div> Mon, 02 Feb 2009 08:05:13 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317525/ https://lwn.net/Articles/317525/ ekj <div class="FormattedComment"> <a href="http://www.yr.no/place/Norway/Rogaland/Stavanger/Stavanger~506436/hour_by_hour.html">http://www.yr.no/place/Norway/Rogaland/Stavanger/Stavange...</a><br> <p> Amazingly clueful service from the meterological institute of Norway. The data is available as XML, under stable, maintained urls. And under a license which is pretty reasonable. (You have to display "Forecast from yr.no" on publicly visible sites using the data, and you are not allowed to change the content, i.e. add 2 degrees to the temperature at your beach-resort to make the weather appear nicer)<br> <p> Sadly, they only deliver XML-data for the locations they themselves collect data for. For licensing reasons, they don't for locations abroad, so though they cover the world, they're unusable as a data-source for locations outside Norway. Pity.<br> <p> They do have several million locations, certainly a whole lot more than "one per city", and the granularity is hourly forecast for the next 24 hours, "morning", "mid-day", "evening", "night" for the next 72 hours. (I get 549 hits for "London" and 86 hits for "Oslo", for example)<br> <p> </div> Mon, 02 Feb 2009 07:32:45 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317523/ https://lwn.net/Articles/317523/ rsidd <div class="FormattedComment"> KDE 4.2 does have a weather applet. I couldn't find radar pictures, but I think those are useless eye candy, except for professional weathermen.<br> </div> Mon, 02 Feb 2009 06:46:07 +0000 briefs or boxers https://lwn.net/Articles/317515/ https://lwn.net/Articles/317515/ xoddam <div class="FormattedComment"> We already know he wears socks with sandals. I for one choose to remain ignorant about the underwear preference of our glorious BDFL.<br> </div> Mon, 02 Feb 2009 01:24:59 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317511/ https://lwn.net/Articles/317511/ smokeing <div class="FormattedComment"> In Linus' shoes, if my chosen DE announced a push for such an extreme case of cross-platform integration as KDE's flirtation with Windows, I would at least feel queer.<br> <p> He is known to be quite unexcited by all the virtualisation effort, and rightly so: why would one so intimately involved with Linux ever care to look at other platforms? And, when he sees a potentially enormous amount of work at KDE going to get it running, absurdly as it sounds, "natively" on Windows, why, he would so naturally turn away.<br> <p> (On an unrelated note, in that same interview, he openly flounts the public opinion and all the journalist folk quipping thusly (<a href="http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;taxonomyName=Software&amp;articleId=9126619&amp;taxonomyId=18&amp;pageNumber=2">http://www.computerworld.com/action/article.do?command=vi...</a>): "Hey, I usually do my presentation slides in PowerPoint." Subtle and enlightening, isn't it?)<br> </div> Sun, 01 Feb 2009 23:58:17 +0000 Weather applets https://lwn.net/Articles/317510/ https://lwn.net/Articles/317510/ madscientist <div class="FormattedComment"> He said "radar pictures". I don't know where you are but many areas provide relatively up-to-date radar, updated multiple times an hour; even every 5 minutes or so.<br> <p> I too find this very useful (although I use Gnome and their weather applet); for New England winters getting out of work before the snow hits can make the difference between a 45 minute commute, and a 4.5 hour commute.<br> <p> For whatever it's worth I find it more helpful as an applet, than looking it up on the web.<br> </div> Sun, 01 Feb 2009 22:10:10 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317507/ https://lwn.net/Articles/317507/ dlang <div class="FormattedComment"> what is it with bluetooth that you are seeing as non-functional? admittedly I don't do much with bluetooth, but I'm running KDE 4.x (on ubuntu 8.10) and it seems to be working for me.<br> <p> there was an update to ubuntu in the last week that recognises the built-in bluetooth on my T61 for the first time, but I don't know if that is a kernel, ubuntu, or KDE update.<br> </div> Sun, 01 Feb 2009 21:32:57 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317505/ https://lwn.net/Articles/317505/ dlang <div class="FormattedComment"> where is it that you live that the weather prediction isn't valid for more than 15 min?<br> <p> and what weather service is it that you use that updates itself that frequently?<br> <p> everything that I've ever looked at does (at best) a day at a time with 'local' temperature readouts (usually one per city or less)<br> <p> <br> </div> Sun, 01 Feb 2009 21:14:22 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317504/ https://lwn.net/Articles/317504/ truggieri <div class="FormattedComment"> The only question really is which DE is Bloat and which is UltraBloat.<br> </div> Sun, 01 Feb 2009 20:52:21 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317503/ https://lwn.net/Articles/317503/ eru <i>Personally, I consider telling me what the weather may be like in a few hours time to be one of the more useful things that my computer can do.</i> <p> Precisely. But I find it is also one of the less useful things a <i>desktop</i> computer can do. I don't lug it (or even a laptop) to places where I might want to known the weather. But I can nowadays easily get a weather report on my mobile phone (which is really a pocket-size always-connected computer) practically everywhere I might feel the urge to look it up. Sun, 01 Feb 2009 20:49:19 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317497/ https://lwn.net/Articles/317497/ callegar In my opinion KDE 4.2 is generally reasonably fast. I am using it on an older Athlon PC with an old Radeon 9600 graphics board, and it is pretty usable on the speed front, even with effects on. What I see as bad is that the road from 4.0 to 4.2 still has not brought us bluetooth and that many many things seem not to have adequate docs (I spent one afternoon trying to understand why kded was dying at every login, just to discover that I had to erase the cache in /var/tmp to make it happy). Sun, 01 Feb 2009 18:55:01 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317496/ https://lwn.net/Articles/317496/ sebas <div class="FormattedComment"> The slowness you perceive might be caused by lacking video drivers. Especially NVidia had some issues here in the past, most of which are fixed with the 180.22 release. That's painting performance, and it might vary per video driver, unfortunately.<br> Application startup should be comparable or faster than in KDE3. If you experience problems there, make sure it's a local problem, if it's not, please let us know what exactly goes wrong -- we can fix it most likely.<br> <p> Overall, from the experience of many users, KDE4 does feel snappy and fast. So it's most likely nothing general but an issue specific to your setup, meaning you don't have to accept slowness.<br> <p> Honestly, if you call the speed of development slow, then I'm just puzzled by your assessment and wonder what you compare it with.<br> </div> Sun, 01 Feb 2009 18:47:30 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317495/ https://lwn.net/Articles/317495/ sebas <div class="FormattedComment"> Yeah, so give the fine weather applet that just entered KDE extragear a shot. If you need multiple places, you can add more than one to your desktop. If you'd like a more basic weather applet, choose weather station.<br> <p> For other critical features, there's also a Plasma version of XEyes.<br> </div> Sun, 01 Feb 2009 18:40:08 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317486/ https://lwn.net/Articles/317486/ bronson <div class="FormattedComment"> This is a meaningless statement since it applies to pretty much every application and feature I can think of: "I need email" "Visit gmail" "I need an IDE" "Visit Heroku" etc. I guess there's no need to spend any time developing DEs anymore!<br> <p> Also, 15 seconds adds up to a lot of time when you're checking many times each day.<br> <p> </div> Sun, 01 Feb 2009 17:17:24 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317484/ https://lwn.net/Articles/317484/ robert_s <div class="FormattedComment"> So visit a webpage. It's 15 seconds more work, but it shouldn't be something that makes a desktop unusable.<br> </div> Sun, 01 Feb 2009 16:40:25 +0000 Did Linus Jump Too Soon? (Linux Journal) https://lwn.net/Articles/317483/ https://lwn.net/Articles/317483/ endecotp <div class="FormattedComment"> <font class="QuotedText">&gt; most would regard [a weather applet] as "useless eye candy".</font><br> <p> Presumably those people live in places where the weather is predictable. Personally, I consider telling me what the weather may be like in a few hours time to be one of the more useful things that my computer can do.<br> </div> Sun, 01 Feb 2009 16:35:29 +0000