Slashdot Mirror


Ark Linux Review, A Distro with an Identity Crisis

mikemuch writes "ExtremeTech has a review of Ark Linux 2006.1, which launched earlier this month. Overall, the reviewer likes this free KDE-based distro, but had to question some implementation choices, such as using the less-compatible Konqueror over Firefox for its default web browser. And for a distro that bills itself as 'a Linux distribution for everyone — designed to be easy to install and learn for users without prior Linux' the installation should hide command-line scrolling and be able to more automatically install standard graphics card drivers."

12 of 181 comments (clear)

  1. Konqueror by IWannaBeAnAC · · Score: 4, Interesting

    So, what exactly is wrong with Konqueror?

    1. Re:Konqueror by Peaker · · Score: 4, Interesting

      Konqueror is still having problems handling GMail (read Google Talk in it)

      That's what I thought too.

      Then I changed my browser identification in GMail to be Mozilla/5.0 and then it suddenly worked.

      Apparently Google are screwing up with Konqueror by checking the browser id.
      I don't suppose they do this out of bad intentions, but they prefer the site reverting to HTML than not working cryptically.

  2. Reviewer missed the point by dbIII · · Score: 4, Informative

    Konqueror shares libraries with other KDE applications so is likely to have a smaller memory footprint than Firefox.

  3. Rule #1: Don't try to please everyone by EmbeddedJanitor · · Score: 4, Insightful
    Anything that is "xxx for everyone" is going to fail. You can't please everyone. If you do you end up with something that has no niche value.

    If you're going to build a distro, or any product for that matter, think long and carefully who you really want to target.

    --
    Engineering is the art of compromise.
  4. Tetris! by calculadoru · · Score: 4, Funny

    Oh come on, before you start bashing them - look, they have a nice Tetris game for you to play while it installs!
    That's got to be worth something, no?

    --
    The power of accurate observation is commonly called cynicism by those who have not got it. -- G.B. Shaw
  5. Konqueror by AaronW · · Score: 4, Informative

    I have been using Konqueror a lot. I got fed up with Firefox when after 24 hours of browsing it was consuming 800MB of RAM, even though the cache size was set at 32MB. I have found that Konqueror is often faster, uses a lot less memory, and is generally more stable. There are a few sites where I have had trouble, but I've also had problems with some sites with Firefox (and a few of those worked with Konqueror). Konqueror has gotten a lot better, especially 3.5. A number of additional fixes went into 3.5.4. My only real complaint is that the adblock feature needs a lot of work to catch up with the Firefox extension.

    The file dialog for Konqueror, when I download and save binaries, is infinitely better than the one in Firefox. The UI on Konqueror is also much easier to customize, adding or removing buttons at will. Some of the buttons I find quite useful, like scaling the web page larger or smaller. I also like the fact that plug-ins run as a separate process than the browser and I can run them niced. It also means I can run a 64-bit browser and integrate 32-bit plugins.

    I also like the bookmark toolbar better in Konqueror. I can easily add folders or book marks to any folder I want with only a couple clicks.

    As a file browser, Konqueror is actually quite nice. It's not the big bloated mess people make it out to be. In fact, if anything is a big bloated mess, it's Firefox. Konqueror uses kparts, so that if, for example, I open a .c file in it, it loads the shared libraries for the editor, or if I click on a multimedia file, it loads kaffeine. Just about everything in KDE is a part, so they can be reused. PDFs are also great in Konqueror when it uses kpdf instead of that bloated Acrobat mess.

    Hell, I can't even open more than one instance of Firefox, even on different machines if my home directory is shared over a network. Konqueror has no such problems.

    The Konqueror browser I'm typing this from has 18 open tabs and has been open for probably about a week or two. It's consuming 475MB of virtual memory and 116MB of resident memory, but I have had a *lot* more tabs open in the past. I can rarely keep Firefox going for more than 24 hours or so, and it gobbles up memory at an astronomical rate (even 1.5.0.6).

    As far as rendering web sites goes, I believe Firefox had problems with Slashdot for the longest time, while Konqueror did not.

    --
    This post is encrypted twice with ROT-13. Documenting or attempting to crack this encryption is illegal.
  6. Let's be accurate. by Anonymous Coward · · Score: 5, Interesting

    To be more accurate, KHTML is the actual rendering engine, while Konqueror encapsulates it and adds the other functionality (ie. tabs, configuration screens, etc.) necessary to create a full-fledged browser.

    A quick way to compare KHTML to Gecko (the rendering engine of Firefox) is to look at the source code for each. What one will immediately notice is that while both are written in C++, the code of KHTML is far cleaner than that of Gecko. Gecko suffers from an over-architecturing, which directly leads to code bloat and unnecessary complexity. KHTML, on the other hand, has been designed to be simple and clear, without an overly convoluted architecture.

    What we end up getting with KHTML is a rendering engine that is of a far higher quality than that of Gecko, mainly because the developers are so easily able to extend it. With the upcoming KDE 4 release, which will likely be portable to Windows and Mac OS X, the portability advantages of Gecko's architecture will be rendered obsolete.

    1. Re:Let's be accurate. by IamTheRealMike · · Score: 4, Informative
      A quick way to compare KHTML to Gecko (the rendering engine of Firefox) is to look at the source code for each. What one will immediately notice is that while both are written in C++, the code of KHTML is far cleaner than that of Gecko. Gecko suffers from an over-architecturing, which directly leads to code bloat and unnecessary complexity. KHTML, on the other hand, has been designed to be simple and clear, without an overly convoluted architecture.

      That's a little unfair. In fact I have read the source code to each and I wouldn't say one is far clearer than the other. Maybe that used to be the case but they've cleaned Gecko up a lot in the past few years. It's true that the Mozilla dialect of C++ is a little more obtuse than the Qt dialect, however, Mozilla is a hell of a lot more portable than KHTML is not only between operating systems but also between compilers, and that makes a big difference. Gecko also has a lot of features that KHTML does not have - for instance the combination of the fact that its objects are easily exposed to JavaScript and XUL is what makes the Firefox extensions culture so vibrant. Where are the extensions to Konqueror? There might be a few, I guess, but nothing like what you have with Firefox. It's hard to see how they could have made extensions so powerful without the platform parts like XPCOM which make the C++ harder to read.

      What we end up getting with KHTML is a rendering engine that is of a far higher quality than that of Gecko

      Meaningless assertion, not backed up by fact. I claim the opposite. Gecko is fast, very standards compliant and trivial to extend using reasonably well documented APIs and technologies. For instance look at XTF. It has support for a lot of new things like SVG, MathML, designMode and so on. KHTML might support these things, depending if you use the Apple fork ... or it might not.

      With the upcoming KDE 4 release, which will likely be portable to Windows and Mac OS X, the portability advantages of Gecko's architecture will be rendered obsolete.

      No, I rather think it won't. The portability of Geckos architecture already allowed it to make massive gains on Windows, the only platform that matters statistically. Where was KHTML in all of this? Now don't get me wrong, it's not a bad rendering engine at all, but to claim a Windows port of KHTML will make Gecko obsolete is rather naive. Maybe KDE 4 will rock my world but right now it's mostly a set of marketing web pages and fancy codenames for various abstractions over already quite abstract technologies (HAL, gstreamer etc).

  7. Re:So which is it? by ozmanjusri · · Score: 5, Informative
    So which is it?

    It's Konqueror. The Ark Linux devs give their reasons in one of the forums:

    We think that Konqueror is a much better browser. Konqueror follows the standards (in particular CSS) more closely than any other browser, it integrates better with the rest of the system, it doesn't drag in hundreds of libraries nothing else needs, and its user interface is better, because it doesn't make weird decisions like using the wrong button order. (We think the weird "Do you want to do this? [No] [Yes]" button order used by Firefox and a couple of other projects is plain wrong, because it contradicts normal language use -- what's the last time someone asked you in plain English "Do you want to xyz? No or yes?"?

    If you absolutely need it, you can simply apt-get install firefox though.

    http://forum.arklinux.org/viewtopic.php?t=65&highl ight=firefox
    --
    "I've got more toys than Teruhisa Kitahara."
  8. yeah, yeah, where's the problem? by twitter · · Score: 4, Interesting

    As such, firefox is dedicated to being a browser where the web is a primary focus, whereas konqueror is more like a swiss army knife where the web is an included convenience.

    So, what's the mysterious "less compatible" component? Every now and then I'll find some page that won't work. Once in a blue moon, a right click Firefox open will do better, so I keep it around. The problem is mostly with non free junk like Macromedia Flash and IE specific navigation.

    I use Konqueror as my primary browser because it's file handling is so excellent. The web looks like an extension of my computer and I like it that way. It renders standard compatible web pages without a problem and it's split tab capability (think the old Windoze 3.1 file manager) makes it an excellent research tool. Integration of tools like kpdf and kget make a seemless browsing experience that is top notch. Next to that, Firefox feels cramped.

    But, hey, I could be missing something. What is it?

    --

    Friends don't help friends install M$ junk.

  9. Swiss army knife? Call it KParts integration by vdboor · · Score: 4, Insightful
    Konqueror on the other hand is a file manager, also a file viewer. It's such a good file viewer that you can view either local or remote files, and not only pictures and pdfs, but also html files, meaning you can also view graphic html files on remote servers, aka the web. As such, firefox is dedicated to being a browser where the web is a primary focus, whereas konqueror is more like a swiss army knife where the web is an included convenience.

    This myth should actually be seen as a compliment to KDE. Why? The components you mention all come from the standard KDE libraries, or they are supplied by additionally installed applications. Konqueror is just a shell, host for all of them. Just like ActiveX/OLE integrates applications seamlessly together in Windows.

    Konqueror can host a KHTMLPart, KatePart (text editor), file-viewer part, image-viewer part. They can all be developed by separate appliations. Install a PDF viewer, and Konqueror can load it's PDFPart too. The networking support you mention come from the standard KDE-IO libraries, they haven't been klunged into Konqueror at all (every KDE application has KDE-IO and KPart support!).

    Saying that this would remove developer resources from KHTML isn't really true. Developers working on a PDFPart likely wouldn't have ended up coding for KHTML anyways.

    --
    The best way to accelerate a windows server is by 9.81 m/s2 ;-)
  10. Oh come on. by quag7 · · Score: 5, Interesting

    Hiding scrolling text is ALWAYS evil. I don't care what Windows users are ALLEGEDLY used to and prefer. Anyone who would prefer less information than more information - especially given the possibility that something can go wrong - is not someone I want making decisions about how Linux distros work.

    I've never used Ark Linux before, but the idea that somehow by castrating Linux and making it look and feel like Windows it will somehow compete with or replace Windows strikes me as highly unlikely.

    Apple - which, depending on what numbers you buy into, has even a greater market share than Linux, though has barely put up any kind of substantial fight against Microsoft in terms of the number of people using it - and where the Mac *has* succeeded is in the ways it is different from Windows. I wonder how many Mac users would applaud a choice by Apple to change something in the Mac OS so as "not to scare off Windows users." Answer: almost none. Or perhaps, none. Frankly, and I'm not even a Mac user, a Mac user who took that attitude would disappoint me as someone who is at least amused by OS partisanship.

    If you are going to use Linux, or FreeBSD, be ready to use a command line. Some people can get by without it because they don't do much, or have incredible luck and every upgrade works perfectly and nothing ever breaks, but frankly, the population that is served by hiding the command line is miniscule compared to those of us who appreciate - and in fact use Linux or a BSD *because* of that command line.

    I'm really getting tired of this idea of making "Linux ready for the desktop" in the sense of making it flashy and "slick" like Windows. I've got no objection to making Linux look nice and function logically in terms of its GUI, but not at the expense of dumbing it down and hiding its strengths, which a lot of people want to do.

    I want VERBOSE error and status messages, and as much access to the console and logs as possible. Transparency all the way down. I want this in Windows too since I'm forced to use it for work but I'm not going to get it.

    The command line is what makes UNIX-like OSes what they are - to me, anyway.

    I'm sick of people trying to make it Windows, or make it like Windows, or look like Windows.

    I'm not particularly interested in sacrificing functionality so people who are afraid or unwilling to learn command line basics.

    As for the default browser, for god's sake, can we stop pretending that it MATTERS WHAT IS INSTALLED BY DEFAULT. Can we stop pretending that the main concern about Linux is what COMPLETE COMPUTER ILLITERATES will make of it? Sheesh. INSTALL AN ALTERNATE BROWSWER IF YOU DON'T LIKE THE DEFAULT CHOICE LIKE SO MANY WINDOWS USERS DO WHEN THEY DOWNLOAD AND INSTALL FIREFOX.

    Guess what? In Linux you can install what you want, change the wallpaper, and change your menus and shortcuts around. Shocker!

    Macs aren't (and rightfully so) measured against Windows in terms of similarity to Windows's philosophy of design (and look and feel) and neither should Linux. By which I mean, they're not measured against it as if not being like Windows is a deficit.

    The idea is to present a significant alternative to Windows which is better (verbosity of the OS is definitely a plus - how many people like the way a Windows fresh install tries to hide system folders, file extensions, and resort to other such dicketry? Not me and frankly not anyone I know, including those who have a fraction of interest in computers than I do). How many people applaud having a completely withered, pathetic command line in Windows? Not me. How many people think having everything so GUI-centric in Windows has improved peoples computing skills, overall productivity, and so forth? I'm not bashing GUIs and wizards; I'm just saying that the command line should be a transparent, well-documented alternative so if the average user wants to automate simple tasks (like rotating wallpaper hourly or something), it's clear and obvious how to do that.