Let's compare an established de facto standard which is a monstrosity beaten into submission over several years, to an experimental implementations of an unfinished standard. Oh, and lets leave out the fact that the new one is perfectly cross-platform and open while the old one isn't.

Would a filesystem cache cause the system to swap?

I don't know how caching works in W7 but on Linux, if the system has to "turn to disk-based virtual memory to handle tasks" then the memory utilization isn't caused by buffers because buffers are never swapped out to disk. If W7 behaves in a similar manner the it's either a memory leak, system bloat or the caching mechanism is broken.

Incorporating a "split view" in the default file manager, in my opinion, is an overkill and a symptom of feature creep. I realize KDE strives to give the user freedom of customization but sometimes it introduces needless complexity. Managing layouts is not a job of a file manager.

I'm fond of the traditional UNIX mindset: write a program to do one thing, but do it well. If I need two vertical panes with different directories in it then I fire up two file manager windows and use a window manager with tiling. If I'd have to work with a standard WM I'd just install Midnight Commander or an alternative.

But it would be wasteful. The assignment operator is used lot more often in C than the comparison operator. It's only logical to make the former, shorter. There may exist other problem domains which make the inverse true, but they are a niche.

Funny you mention this. From the article:

I'd like to hang the guy who modded this as Flamebait by the balls. Let's just add a "-1, Nuh-uh" modding option already?

No worries, you can get off mine.

This issue isn't exclusive to Fedora. PackageKit is (or was) destined to be the package and update framework for many distributions. Fedora got hit first because it's the distribution which usually had been going for the cutting edge. Fortunately everyone else will be spared the hassle of damage control and setting the developer straight. This whole uproar may inspire a better focus on scrutinizing the whole *Kit approach, which is IMO a good thing.

I'm not sure about the current development structure but I think it would be optimal to get more developer feedback from other distributions on the *Kit framework. This project looks like it really could use more transparency and QA, especially when it's going to be responsible for desktop security across many distributions.

Let's hope that quote won't get him a place in the "famous last words" fortune of UNIX security.

Things get complicated when the project's server are physically compromised. I agree that the mechanism is neat and very useful but the developers jumped the gun when they altered the default configuration without notifying anyone. This change wasn't even mentioned in the release notes. That alone raises questions about the project's development process.

Fedora prided itself with default security policy since it had SELinux enabled by default. This change is exactly in the reverse direction.

If it actually works as advertised we'll have to check our luggage 48 hrs before planned flight.  If that in turn works as advertised, we'll have to check in 24 hrs before flight, then get dunked and go hang out at the airport bar while watching fellow travelers for signs of 'glow'.  Could be fun - I just want the TSA to pick up my tab at the end of the wait.

I really like us to come up with better debugging techniques before we go further into these bio-engineering stuff.

You may not think much about it but ways to safely detect landmines can save a number of arms, legs, and lifes. They could help avoid another child losing a leg while playing in a field where landmines were placed.

Falcon

Ahem.

The IRS has *nothing* to do with Use Taxes. That's your local Member State that collects use tax, not the central government.

You'll love it. Even the progress bars beep!

Oh. So you're that guy.