{"id":1278,"date":"2007-08-29T23:54:32","date_gmt":"2007-08-29T21:54:32","guid":{"rendered":"http:\/\/vizZzion.org\/blog\/2007\/08\/revolution-or-hype\/"},"modified":"2007-08-29T23:54:32","modified_gmt":"2007-08-29T21:54:32","slug":"revolution-or-hype","status":"publish","type":"post","link":"https:\/\/vizZzion.org\/blog\/2007\/08\/revolution-or-hype\/","title":{"rendered":"Revolution or Hype?"},"content":{"rendered":"<p>Yesterday, in a press inquiry which ended up in my mailbox (as most KDE press inquiries do), I got asked whether<br \/>\n    KDE4 will be a revolution, or if it&#8217;s just a hype. While there certainly is quite a hype around KDE4, the answer<br \/>\n    is not quite so simple. Let me try to explain.<br \/>\n    The Free Desktop and KDE have come a long way during the last years. There have been various huge changes in KDE&#8217;s<br \/>\n    social structure, in it&#8217;s infrastructure and of course in the sourcecode itself. I&#8217;ve split this into three different<br \/>\n    areas where I think a shift in paradigm has taken place.<\/p>\n<h3>Target Groups<\/h3>\n<p>        This is probably the one that has the most to do with the question. KDE is<br \/>\n        about to enter the mainstream market. KDE4 will not be for geeks and<br \/>\n        enthusiasts only, but for a very wide range of users. Those new users (casual<br \/>\n        computer users, no IT experts) have different perception of software, and<br \/>\n        they&#8217;re generally not willing or able to fix small problems, while our<br \/>\n        current userbase (early adopters from a marketing POV) can fix minor glitches<br \/>\n        themselves. Now let&#8217;s have a look what KDE 4.0 will be: First stable version<br \/>\n        of our frameworks and libraries, a first set of applications we think meet<br \/>\n        our standards. As every dot-oh release, there will be glitches (we are<br \/>\n        perfectionists, but we also need to release early, release often). So 4.0<br \/>\n        might not be perfect in every single aspects, it *will* need some polishing.<br \/>\n        We hope, however, to reach the quality of what currently is KDE 3.5 early in<br \/>\n        the release cycle.<\/p>\n<h3>Technological<\/h3>\n<p>        Sound handling and hardware management are two examples that are now being done<br \/>\n        in a central place. Software and users need to get used to this. This means<br \/>\n        that not every application will take full advantage of all those new<br \/>\n        frameworks since they&#8217;re just too, well new. Also, being able to make use of<br \/>\n        search, semantic desktop features, complete new visual possibilities, easy<br \/>\n        access to multimedia and all the goodness the pillars of KDE 4 provide will<br \/>\n        set some developers to think what is possible now, it enables creativity<br \/>\n        because it makes it easier to integrate all those things in one application.<br \/>\n        I&#8217;m pretty sure we&#8217;ll see some very innovative new applications of those<br \/>\n        technologies popping up in the course of the next release cycle, a lot<br \/>\n        probably post 4.0. More than once, last weekend someone who was not working<br \/>\n        on KDE yet would ask me if his idea of a new application or way to organise work<br \/>\n        would be possible to implement. In all cases, with the new technologies it would<br \/>\n        even be relatively trivial. This, on the one hand says a lot about the applicability<br \/>\n        of our technologies, but also that we&#8217;re able to attract new people and that those<br \/>\n        people will bring a lot of new and exciting ideas into KDE.<\/p>\n<h3>Community<\/h3>\n<p>        The community has grown a lot during the last 2 to 3 years. We&#8217;ve not only<br \/>\n        lots of new developers, but also completely new parts of the community. See<br \/>\n        the usability people, usability is a process embedded in our development<br \/>\n        process now. The Marketing Team is also rather new, and working with the<br \/>\n        developers. The KDE community is really growing from a Free Software project<br \/>\n        into a Free Culture project and thereby becoming a broader set of qualities.<br \/>\n        At the same time, our developer community is<br \/>\n        growing, we get lots of new developers and developers shift also into the class of<br \/>\n        critical core developers. KDE is a *very* healthy community as it stands.<\/p>\n<p \/>\n    Bottom line: There&#8217;s a hype around KDE4 and we hope we can live up to that. During<br \/>\n    the last years, the KDE community has gone through an evolution and is now a mature<br \/>\n    and healthy Free Culture project that is about to revolutionise the computing experience.<\/p>\n<p \/>\n    <strong>update:<\/strong><br \/>\n\tComputerworld has <a href=\"http:\/\/www.computerworld.com.au\/index.php\/id;339066012\"><br \/>\n\tpublished the interview<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Yesterday, in a press inquiry which ended up in my mailbox (as most KDE press inquiries do), I got asked whether KDE4 will be a revolution, or if it&#8217;s just a hype. While there certainly is quite a hype around KDE4, the answer is not quite so simple. Let me try to explain. The Free&hellip; <a class=\"more-link\" href=\"https:\/\/vizZzion.org\/blog\/2007\/08\/revolution-or-hype\/\">Continue reading <span class=\"screen-reader-text\">Revolution or Hype?<\/span> <span class=\"meta-nav\" aria-hidden=\"true\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-1278","post","type-post","status-publish","format-standard","hentry","category-kde"],"_links":{"self":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/1278","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/comments?post=1278"}],"version-history":[{"count":0,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/posts\/1278\/revisions"}],"wp:attachment":[{"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/media?parent=1278"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/categories?post=1278"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vizZzion.org\/blog\/wp-json\/wp\/v2\/tags?post=1278"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}