Re:Give them a chance...
on
KDE 3.0 is Out
·
· Score: 0, Flamebait
The oft-heard cry of the noisiest KDE advocates. No explanation is given, the reader is expected to simply grok the wholesomeness of KDE and the lack of this mystical quality in GNOME. It is nonsense of course. Neither desktop is particularly "integrated" compared to Windows XP, and certainly not compared any version of the Apple Mac. Whatever "integrated" actually means.
I didn't read the rest of your post, but this is one of the most thoughtless, idiodic comments that I have read in a while. You bash people for saying KDE is integrated, then say that it isn't, then you say that XP and MacOS X are more integrated, then you reveal that you don't know what integrated means. How can you say that XP and MacOS X are more integrated when you admit that you have no basis to measure integration. It's simply ridiculous.
By the way, the reason people think that KDE is more integrated, is because there is more sharing of standardized components. For example, the open file dialog has many options on the way it displays files, and after customizing it, it will look the same when used from any KDE application. Gnome doesn't even have an open file dialog that is worth a damn.
KDE 3.0 does need at least 64 megs of ram to run comfortably( 128 is better ), but it really doesn't need a P3/400. A pentium 133 with 128megs would run great. KDE performance is much more dependent on ram than processor, especially if you turn off all of the eye candy.
Actually, the Altair was already fully functional. Bill just didn't have access to one...They wrote the code on a government funded computer.
Paul Alan wrote the emulator for the Altair while Bill Gates wrote BASIC. Paul Alan was the one to actually deliver the product to New Mexico, and had to write the boot loader on the plane trip there! It did run first time amazingly.
Have you tried Koffice from CVS? I'm guessing that you haven't.
KWrite is very stable and has all of the features that the average person needs.
KSpread is rock solid and has everything a person wants from a spread sheet.
KPresenter is also rock solid and has all the features needed to be a viable presentation program. It does a wonderful job of making HTML slides.
The three most important Office apps have come a long way and will be released soon. They have matured a lot and will prove to everyone that KOffice is here to stay.
This doesn't happen with interfaces. If a KDE application doesn't conform to the KDE style guide, then it is considered a bug and will be fixed. There is a lot of thought that goes into KDE's interface. Of course we can't control applications that are not part of KDE.
I don't believe that this is correct. The source for Kivio is in the KDE Koffice CVS and it includes the source for flowcharting stencils. You could easily add your own stencils if you wanted to. You may not have the source to their proprietary stencils, but you can't have everything. Also, Shawn Gordon is very helpfull and I'm sure he would help make sure that you were satisfied if you purchased the stencils from them.
Actually, these are called.desktop files and they provide all the functionality that you described. The standard was developed by KDE and Gnome. KDE uses it to its fullest, while Gnome uses most of it. Other desktops are free to impliment support.
If you want to use Linux for web browsing then it sucks  
This is not true!
1. Konqueror - Very fast, light, and mostly standards compliant. Has many features that none of the other browsers have.
2. Netscape 4.7 - Renders most pages correctly and is fairly quick. Downside is that it is unstable and ugly.
3. Mozilla - Fairly Quick, mostly standards compliant, and looks good. Downside is that it take quite a bit of memory and the UI is sluggish(Overengineering).
4. Opera - Haven't used it, but many say it is very fast and renders most pages correctly.
5. Lynx - Doesn't support graphics, but browsing is quick and it won't crash on you.
6. IE under WINE - I've heard that it works fairly well but haven't tried it myself.
My point? Browsing under linux may not be perfect, but we have plenty of choices, many of which get the job done and do it well.
Honestly, I think within a year Konqueror will be the best browser available for any OS. JavaScript is getting very good and is being very actively developed, Java support is almost perfect(use the JRE from blackdown), it supports CSS1 and most of CSS2. DOM Level 1 and 2 are supported as with https, and every IO protocal you can think of. It is fast and the codebase is clean and lean.
I also think that Mozilla is getting good, but development seems slower for what I believe to me many reasons.
Matt Newell
Re:I have had a fearful thought....
on
KDE 2.1 Is Out
·
· Score: 1
XUL-This just makes Moz more bloated and slower. Also less consistant with the rest of the desktop. Konqueror runs on Unix and that is all the cross platform that anyone needs.
DOM-Do you have any facts that say that Moz's dom support is superior. I don't know a whole lot about Moz, but I know(from looking at code) that Konqueror is built around DOM(Supports DOM 1 and partially DOM2).
ECMAScript-KDE2.0 had some problems, but 2.1 has very complete support. I would argue that Konqu is currently ahead of Moz.
MathML-Sound great, but very few people care.
Cross Platform-It runs on Unix and this is all that I need:)
KDE doesn't use a lightweight CORBA subset. Know the facts and don't talk about stuff you don't know. KDE uses binary modules because they run with *NO* performance overhead, unlike CORBA. The reason KDE chose to use binary modules is because there is no use for running a component over a network, the component can just be downloaded and then run on the same machine.
I could give you a long list of reasons why this is a stupid idea, but instead I'm just going to say this. KDE programmers use C++ and Gnome programmers use C and neither want to switch. They are two seperate desktops and they will stay that way so shut up.
This sounds like kde wants to do it's own package management, which is scary
I can gaurantee you that this is not the case. KDE developers have expressed over and over that they want the distributions to deal with the packaging problems. KDE only makes two types of packages, Source and Debs. The rest are sent back to KDE from the distros before release. This guy decided that because some distributions lacked an easy way to install KDE that he would try to make the problem better and I praise him for this.  
Matt Newell
The kdebase package is together because:
1. Many parts in kdebase depend on other parts in kdebase
2. KDE only make releases every once in a while, when they do, they just expect you to upgrade the whole thing.
Matt Newell
I have had anti-aliased fonts in all the applications(QT) that I use for over two months. I enjoy them very much and they look *BETTER* than windows fonts in all cases. This did take a bit of work to set up, but it is worth the effort.
People that say that AA fonts make their eyes strain, probably have their DPI set incorrectly or some other problem. The AA part of AA fonts should not be distinguishable from normal reading distances.
This article is very pointless in my mind. I don't know a whole lot about *BSD, but I know a bit about linux. First of all, they are testing the first version of a very major release, with a whole new VM, and they expect it to be properly tuned by default. It's not going to happen. Second, these two operating systems are very different beasts and behave differently in different conditions. I strongly believe that FreeBSD is the better choice for an out of the box web server, but for any site that needs real performance and has network administrators that know what they are doing, I would pick linux. Why, because using sendfile with the zerocopy patches, linux will serve much more content than freebsd. Then throw in Tux, then you really have a serious web serving machine that will be the performance leader every time.
For the desktop, Linux is always just a bit ahead of FreeBSD. The reason for this is because most developers are developing their stuff for linux and soon after it is ported to the BSD's. But linux does currently have much better USB support and video card support is also better when it comes to DRI.
Linux is just now catching up to FreeBSD in terms of performance, but Linux will overtake it and leave it behind in the coming months simply because there are many more people interested in linux.
Linux uses double 4byte pointers and that limits a processes address space to 4GB, which results in about 2GB or so of physical memory(much of the address space is taken up by other things). You can get around this by using threads, or by special mmaping strategies. Most single processes probably shouldn't be using more than 4GB or ram anyway. This is mainly just a limitation of ia32 design and anyone who needs the ability to address more than 4GB should be using a 64bit processor.
Slashdot Mirror
The oft-heard cry of the noisiest KDE advocates. No explanation is given, the reader is expected to simply grok the wholesomeness of KDE and the lack of this mystical quality in GNOME. It is nonsense of course. Neither desktop is particularly "integrated" compared to Windows XP, and certainly not compared any version of the Apple Mac. Whatever "integrated" actually means.
I didn't read the rest of your post, but this is one of the most thoughtless, idiodic comments that I have read in a while. You bash people for saying KDE is integrated, then say that it isn't, then you say that XP and MacOS X are more integrated, then you reveal that you don't know what integrated means. How can you say that XP and MacOS X are more integrated when you admit that you have no basis to measure integration. It's simply ridiculous.
By the way, the reason people think that KDE is more integrated, is because there is more sharing of standardized components. For example, the open file dialog has many options on the way it displays files, and after customizing it, it will look the same when used from any KDE application. Gnome doesn't even have an open file dialog that is worth a damn.
KDE 3.0 does need at least 64 megs of ram to run comfortably( 128 is better ), but it really doesn't need a P3/400. A pentium 133 with 128megs would run great. KDE performance is much more dependent on ram than processor, especially if you turn off all of the eye candy.
I didn't know that real developers actually visited this site anymore. If you have the time you should check out kuro5hin.org
You are a fucking idiot.
There is a *stable* patch for tabbed konqueror that will be included in 3.1.
Maildir support was added to cvs right after KDE2.2.0 was released. It will be in the next version of kmail.
It is not a micro-kernel. It is a modularized, multithreaded, monolithic kernel. Just like linux.
Actually, the Altair was already fully functional. Bill just didn't have access to one...They wrote the code on a government funded computer.
Paul Alan wrote the emulator for the Altair while Bill Gates wrote BASIC. Paul Alan was the one to actually deliver the product to New Mexico, and had to write the boot loader on the plane trip there! It did run first time amazingly.
Matt Newell
I meant KWord not KWrite.
Matt Newell
Have you tried Koffice from CVS? I'm guessing that you haven't.
KWrite is very stable and has all of the features that the average person needs.
KSpread is rock solid and has everything a person wants from a spread sheet.
KPresenter is also rock solid and has all the features needed to be a viable presentation program. It does a wonderful job of making HTML slides.
The three most important Office apps have come a long way and will be released soon. They have matured a lot and will prove to everyone that KOffice is here to stay.
Matt Newell
This doesn't happen with interfaces. If a KDE application doesn't conform to the KDE style guide, then it is considered a bug and will be fixed. There is a lot of thought that goes into KDE's interface. Of course we can't control applications that are not part of KDE.
Matt Newell
QT 3 will include alpha channel support using the Render extension. This means hardware accelerated per channel alpha. Matt Newell
I don't believe that this is correct. The source for Kivio is in the KDE Koffice CVS and it includes the source for flowcharting stencils. You could easily add your own stencils if you wanted to. You may not have the source to their proprietary stencils, but you can't have everything. Also, Shawn Gordon is very helpfull and I'm sure he would help make sure that you were satisfied if you purchased the stencils from them.
Matt Newell
There has been an option for this since 4.0
Matt Newell
Actually, these are called .desktop files and they provide all the functionality that you described. The standard was developed by KDE and Gnome. KDE uses it to its fullest, while Gnome uses most of it. Other desktops are free to impliment support.
Matt Newell
No offense, but you should really check to make sure anti-aliasing is working before you post that it causes more eyestrain than W2K.
*YOU WERE NOT USING AA FONTS*
Why, because nvidia's X server does not currently support the render extension and so anti-aliased fonts will not work with it.
If you want to use Linux for web browsing then it sucks
 
This is not true!
1. Konqueror - Very fast, light, and mostly standards compliant. Has many features that none of the other browsers have.
2. Netscape 4.7 - Renders most pages correctly and is fairly quick. Downside is that it is unstable and ugly.
3. Mozilla - Fairly Quick, mostly standards compliant, and looks good. Downside is that it take quite a bit of memory and the UI is sluggish(Overengineering).
4. Opera - Haven't used it, but many say it is very fast and renders most pages correctly.
5. Lynx - Doesn't support graphics, but browsing is quick and it won't crash on you.
6. IE under WINE - I've heard that it works fairly well but haven't tried it myself.
My point? Browsing under linux may not be perfect, but we have plenty of choices, many of which get the job done and do it well.
Honestly, I think within a year Konqueror will be the best browser available for any OS. JavaScript is getting very good and is being very actively developed, Java support is almost perfect(use the JRE from blackdown), it supports CSS1 and most of CSS2. DOM Level 1 and 2 are supported as with https, and every IO protocal you can think of. It is fast and the codebase is clean and lean.
I also think that Mozilla is getting good, but development seems slower for what I believe to me many reasons.
Matt Newell
XUL-This just makes Moz more bloated and slower. Also less consistant with the rest of the desktop. Konqueror runs on Unix and that is all the cross platform that anyone needs.
DOM-Do you have any facts that say that Moz's dom support is superior. I don't know a whole lot about Moz, but I know(from looking at code) that Konqueror is built around DOM(Supports DOM 1 and partially DOM2).
ECMAScript-KDE2.0 had some problems, but 2.1 has very complete support. I would argue that Konqu is currently ahead of Moz.
MathML-Sound great, but very few people care.
Cross Platform-It runs on Unix and this is all that I need:)
Matt Newell
KDE doesn't use a lightweight CORBA subset. Know the facts and don't talk about stuff you don't know. KDE uses binary modules because they run with *NO* performance overhead, unlike CORBA. The reason KDE chose to use binary modules is because there is no use for running a component over a network, the component can just be downloaded and then run on the same machine.
Matt Newell
I could give you a long list of reasons why this is a stupid idea, but instead I'm just going to say this. KDE programmers use C++ and Gnome programmers use C and neither want to switch. They are two seperate desktops and they will stay that way so shut up.
Matt Newell
This sounds like kde wants to do it's own package management, which is scary
I can gaurantee you that this is not the case. KDE developers have expressed over and over that they want the distributions to deal with the packaging problems. KDE only makes two types of packages, Source and Debs. The rest are sent back to KDE from the distros before release. This guy decided that because some distributions lacked an easy way to install KDE that he would try to make the problem better and I praise him for this.
 
Matt Newell
The kdebase package is together because: 1. Many parts in kdebase depend on other parts in kdebase 2. KDE only make releases every once in a while, when they do, they just expect you to upgrade the whole thing. Matt Newell
I have had anti-aliased fonts in all the applications(QT) that I use for over two months. I enjoy them very much and they look *BETTER* than windows fonts in all cases. This did take a bit of work to set up, but it is worth the effort.
People that say that AA fonts make their eyes strain, probably have their DPI set incorrectly or some other problem. The AA part of AA fonts should not be distinguishable from normal reading distances.
Matt Newell
This article is very pointless in my mind. I don't know a whole lot about *BSD, but I know a bit about linux. First of all, they are testing the first version of a very major release, with a whole new VM, and they expect it to be properly tuned by default. It's not going to happen. Second, these two operating systems are very different beasts and behave differently in different conditions. I strongly believe that FreeBSD is the better choice for an out of the box web server, but for any site that needs real performance and has network administrators that know what they are doing, I would pick linux. Why, because using sendfile with the zerocopy patches, linux will serve much more content than freebsd. Then throw in Tux, then you really have a serious web serving machine that will be the performance leader every time.
For the desktop, Linux is always just a bit ahead of FreeBSD. The reason for this is because most developers are developing their stuff for linux and soon after it is ported to the BSD's. But linux does currently have much better USB support and video card support is also better when it comes to DRI.
Linux is just now catching up to FreeBSD in terms of performance, but Linux will overtake it and leave it behind in the coming months simply because there are many more people interested in linux.
Matt Newell
Linux uses double 4byte pointers and that limits a processes address space to 4GB, which results in about 2GB or so of physical memory(much of the address space is taken up by other things). You can get around this by using threads, or by special mmaping strategies. Most single processes probably shouldn't be using more than 4GB or ram anyway. This is mainly just a limitation of ia32 design and anyone who needs the ability to address more than 4GB should be using a 64bit processor.
Matt Newell
Actually, linux does not differentiate between processes and threads. Processes can share( and inheret) and number of things including memory.
Matt Newell