What is so bad about this article is that the headline says "Review of Gnome 2.6" and then the article only discusses Nautilus -- which is only a single part of Gnome.
He's reviewing the upgrade to GNOME. And guess what was upgraded in 2.6? No, guess!
Apart from flaming the spatial Nautilus, there's nothing short of a rant in generalities here. Nothing is mentioned specifically, and it's just the author whining about GNOME's design principles. Are we sure this wasn't written by Rob Enderle?
On the contrary, the strength of the author's claims is that they can be applied to other parts of the system as well. He complains about the lack of configurability with Nautilus but he could have just as easily have complained about the lack of configurability with metacity or something else on the typical GNOME desktop.
C'mon, the people required to pay for using BK for contributing to a free project are those who wouldn't have chose it in the first place! Now I don't have a problem with paying for software, if I decide it's something I want to use, but I have a huge problem with paying for software that I didn't choose to use, when most other people using it (including the ones who chose to use it) don't have to pay.
When you characterize the problem like that it sounds even LESS like BK's fault. With everyone now aware of the licensing terms the solution seems simple: don't use it if it's going to cause problems.
I happen to think the license is a bit silly (though perhaps necessary for BK's survival as a company). But in any case, it seems like the solution is for people to just plan their software usage accordingly. With a BK to CVS gateway available, there's literally nobody forcing you to use the thing.
Finally it's a bit misleading to say that it was BitKeeper that made Linus 10x more productive. Before BK they didn't use any source control at all, and all patches were sent either in private email or onto lkml. It's not surprising that using source control improved things!
It's also not surprising that Linus believes a source control package (BitKeeper) that was developed specifically with his needs in mind and based on his input is much more effective than the other products available would be.
I usually don't, butif you read the BK license, you will notice that it disallows you to work on competitors (including CVS and subversion) if you are a BK user.
Only if you're a user of the free version of BK. You have to pay for the commercial version of BK in that case. I find it very entertaining that the subversion people complain about this.
No, the BitKeeper license is evil. Go read it sometime -- it prevents folks from working on competing systems. This means that folks working on Free revision control (like me!) are substantially hampered if we want to also do some work on the Linux kernel.
No, it doesn't. It prevents people only from using the free version of BitKeeper to create competing systems. How evil!
He's been known to spread FUD about Arch in public, and is otherwise not a very nice person to have as a competitor *or* a supplier.
Time for us Linux fans to put our money where our mouths are. You want to see widespread use of Linux on the desktop? Buy Doom3. I'm serious - if there were significant sales on Linux it might persuade other software companies to start coming out with stuff for Linux too.
Or just play Quake 3 or Doom 3 on Linux. They monitor who's using which client versions and the Linux client usage is just as unimpressive as the Linux client sales figures.
To me that is just an incredible feat of timing and business acumen, and one that was almost totally optimal for his shareholders (albeit not Time Warner's shareholders... but hey, he was the seller, not the buyer!)
Didn't Time Warner and AOL shareholders both get, um, AOL-Time Warner stock as a result of the deal? You know, the stock whose value plummeted?
Second amendment rights advocates do not believe this either.
I hope you're not including the NRA among "second amendment rights advocates," because they're literally always at one pole during debate of any gun-related issue, no matter what it is. They very much act as if they believe second amendment rights are completely unlimited, which is one of the reasons why political gun issue debates are always so idiotic in the US.
2 GB+ files. Some versions of Win32 can do them, some can't.
Much like Unix and Linux.
Of course the really big difference is that NT has supported these large files from the very beginning (1993), much earlier than most Unixes and close to a decade before Linux.
Anyone remember Sprint by Borland? Of course you don't.
Actually I've still got my copy. There's never been a faster editor for huge files, although I don't have it running anymore. It's around here somewhere...
A second point is that the dangers of low level radiation are drastically overstated. While there is disagreement on the casualties, the fact there is a rift in the attributed numbers is very clear. The UN reports fewer than 50 people died and a few 1000 (horrible of course - I feel so sad for these people) with thyroid cancer. These numbers are in stark contrast to the 300,000+ that some people cite.
Just a quick note: determining the health effects of the radiation release with precision is pretty hard because the area in which it happened was suffering from all kinds of industrial polution, poverty, and so on before the release even happened. Things were pretty bad there already but it's unlikely that we can know precisely how bad they were since that was during the Soviet Union's reign.
You can focus on the fact that Sun JDS is basically an out of date, underfeatured version of SuSE Linux. Although if things go according to plan it will soon be accompanied (replaced?) by a version of Sun JDS running on Solaris x86.
I have to wonder how much more effective the local LUG may be towards closing the Digital Divide by providing Free and Open Source Software for Windows, Mac, Linux, and other OSes for the community through the library.
If the people at the local LUGs are one-tenth as dogmatic as the average slashdot-reading Linux fanatic, they won't be effective at all, since the librarians will dismiss them out of hand.
Slashdot Mirror
He's reviewing the upgrade to GNOME. And guess what was upgraded in 2.6? No, guess!
On the contrary, the strength of the author's claims is that they can be applied to other parts of the system as well. He complains about the lack of configurability with Nautilus but he could have just as easily have complained about the lack of configurability with metacity or something else on the typical GNOME desktop.
When you characterize the problem like that it sounds even LESS like BK's fault. With everyone now aware of the licensing terms the solution seems simple: don't use it if it's going to cause problems.
I happen to think the license is a bit silly (though perhaps necessary for BK's survival as a company). But in any case, it seems like the solution is for people to just plan their software usage accordingly. With a BK to CVS gateway available, there's literally nobody forcing you to use the thing.
It's also not surprising that Linus believes a source control package (BitKeeper) that was developed specifically with his needs in mind and based on his input is much more effective than the other products available would be.
Sure you can. You'd just have to pay to use BitKeeper.
The horror!
Only if you're a user of the free version of BK. You have to pay for the commercial version of BK in that case. I find it very entertaining that the subversion people complain about this.
No, it doesn't. It prevents people only from using the free version of BitKeeper to create competing systems. How evil!
Oh, well, he's not nice. That changes everything!
That was true about 3 years ago.
Or just play Quake 3 or Doom 3 on Linux. They monitor who's using which client versions and the Linux client usage is just as unimpressive as the Linux client sales figures.
Of course that implicitly includes about 95% of the game publishers out there. How many publishers actually host their own update patches?
I had a Celeron 433 that would play a DVD well enough - without an MPEG2 decoder, I might add. Maybe the problem is not CPU-related.
Those people will find that shaders are the least of their problems on Linux...
Didn't Time Warner and AOL shareholders both get, um, AOL-Time Warner stock as a result of the deal? You know, the stock whose value plummeted?
The free ATI drivers can run any Linux game that isn't UT2K3 or UT2K4, so how is it trolling?
My mistake, I didn't realize you making such a content-free point.
Um, the president didn't pass the PATRIOT act. The congress did.
I'm gonna go out on a limb and guess that the president actually signed the bill...
I hope you're not including the NRA among "second amendment rights advocates," because they're literally always at one pole during debate of any gun-related issue, no matter what it is. They very much act as if they believe second amendment rights are completely unlimited, which is one of the reasons why political gun issue debates are always so idiotic in the US.
Much like Unix and Linux.
Of course the really big difference is that NT has supported these large files from the very beginning (1993), much earlier than most Unixes and close to a decade before Linux.
I'm sure ROOT's other users would agree with you. All five of them.
Actually I've still got my copy. There's never been a faster editor for huge files, although I don't have it running anymore. It's around here somewhere...
Just a quick note: determining the health effects of the radiation release with precision is pretty hard because the area in which it happened was suffering from all kinds of industrial polution, poverty, and so on before the release even happened. Things were pretty bad there already but it's unlikely that we can know precisely how bad they were since that was during the Soviet Union's reign.
You can focus on the fact that Sun JDS is basically an out of date, underfeatured version of SuSE Linux. Although if things go according to plan it will soon be accompanied (replaced?) by a version of Sun JDS running on Solaris x86.
RPM = Redhat Package Manager. Duh.
If the people at the local LUGs are one-tenth as dogmatic as the average slashdot-reading Linux fanatic, they won't be effective at all, since the librarians will dismiss them out of hand.
Why be Dilbert when you can be the Pointy Haried Boss?
My biggest problem is I am too good at what I do
Congratulations, you're well on your way to achieving your goal.