"Denial-of-Service Attack Found In Btrfs File-System" didn't happen. A vulnerability was found. That's a big deal, no reason to obscure it.

Can Google invent a text search feature? You know, where you type words into a text box and Google returns a list of pages that contain those words? That would be cool. Can Google work on that next?

Gandi rocks, no doubt about it. However, they cannot protect a domain owner from the US government.

I have my domain there because they respect the rights of a domain owner far more than other registrars, but there's nothing they can do if the US government wants a domain in a US-hosted top level domain. When it comes .com, .net, or .org, NSI is all that matters. And unfortunately, they don't care about domain owners.

Sure, but it's not really a newspaper, it's a glorified blog. This was a big win for everybody involved.
If the snarkiness was in the print version of NYT, it would be noteworthy. As is, not much more than a cat fight.

The author thinks he owns facts. It doesn't work like that. What a baby.

I'm not sure which 'forever' you're thinking of. If the location bar was for searching, there wouldn't be a need for that little search box to the right of it.

Before the awesome bar, the closest thing to search in the location bar was automatically adding 'www.' and '.com' to bare names. Even that went away for many years due to the whitehouse.com brouhaha.

I'll let the 'typing in URLs is bad' pass. We all know that's silly.

What's so awful about the Awesome Bar is that it has partially repurposed the location bar, causing the UI to be inconsistent.

In all cases before the awesome bar, the location bar was used for URL's. After the awesome bar, the location bar is almost always used for URL's, but during text entry it is used to search both URL's and web page titles.

An inconsistent UI us a bad UI. The awesome bar introduces inconsistency into the firefox UI. It's bad.

Disabling the awesome bar solves part of the problem. However, it doesn't restore the functionality the location bar had before it was replaced by the awesome bar.

It's not just the the awesome sucks. It's that mozilla removed something that worked and replaced it with something that doesn't. Turning off the part that doesn't work is insufficient to solve the problem.

Have they dumped the awesome bar yet? It makes my browsing more difficult nearly every day.

What are they going to do next? Replace the menubar with a start button? Oh, wait...

Perhaps. However in this case, I believe they felt burned by Lotus and decided to just buy whatever Microsoft was selling because surely it's what theprivate sector uses. And that must be what's best.

That's great and all, but what would be *really* cool, is if Google provided some way to search for pages that contain a specific word or phrase. Yeah, that would be cool. Some kind of search engine where I type in words and the search engine returns only pages that contain those words. Can Google work on that next?

Availability often comes at the cost of reliability.

If you put 2 drives in a RAID-1 mirror, the odds of a drive failure goes up. After all, you now have twice as many drives that might fail. However, a single drive failure no longer makes the data unavailable.

RAID-1 lowers reliability with the goal of raising availability. Paying sysadmins to swap drives is way cheaper than paying people to sit around waiting for their critical data to be restored from tape.

Low reliability is probably just a sign that their systems are highly redundant. Not really surprising.

From the "fix"

> FH_DATE_PAST_20XX
> change '/20[1-9][0-9]/' to '/20[2-9][0-9]/'

That's no fix, it just puts the problem off for another 10 years. Why call the rule FH_DATE_PAST_20XX, shouldn't it be FH_DATE_PAST_201X? At least then the hack would be documented.