Slashdot Mirror

JWZ would tend to agree with you:

Some people, when confronted with a problem, think:
"I know, I'll use regular expressions."
Now they have two problems.

* http://regex.info/blog/2006-09...

No one will ever read this comment, but this picture tells you exactly where he is :

http://regex.info/exif.cgi?imgurl=http%3A%2F%2Fassets.vice.com%2Fcontent-images%2Fcontentimage%2Fno-slug%2F8b4cd78e0012f775d7dc621f5498b675.jpg

Sorry - just like the OP I'm assuming everyone knows what I know! It's a common problem...

"Some people, when confronted with a problem, think
“I know, I'll use regular expressions.” Now they have two problems."

http://regex.info/blog/2006-09-15/247

IIUC the geotagging has been added in LR 3.
But for those of us still on LR 2 there is the [b]excellent[/b] plugin:
http://regex.info/blog/lightroom-goodies/gps

You think that's funny? Can you guess what his name means in japanese?

Baka

The actual quote is this:

Some people, when confronted with a problem, think "I know, I'll use regular expressions." Now they have two problems.

The source of the quote is Jamie Zawinski, who said it on Usenet in 1997.

First off, Mr. Zawinski is recorded as being rather prejudiced against Perl, so I'd take any comments he's made regarding regex's with a massive grain of salt. In fact, I'd probably just ignore him altogether. Besides, his comments are focused almost entirely on the *mis*uses of regexes, not their appropriate application.

As for your second complaint... uhh, who cares? Premature optimization is the devil. So if regex's allow you to cleanly implement a simple solution to a problem (and regexes *are* very well suited to certain tasks, even if they do tend to be misused, particularly in languages such as Perl where they're very tightly integrated), it would be foolish to move to another technique based solely on performance concerns without first profiling the code.

'course, the real irony, on the performance front, is that Mr. Zawinski himself said "The heavy use of regexps in Emacs is due almost entirely to performance issues: because of implementation details, Emacs code that uses regexps will almost always run faster than code that uses more traditional control structures." So maybe they aren't so evil or slow after all?

Because you just can't discuss regular expressions without bringing up this quote:

Some people, when confronted with a problem, think "I know, I'll use regular expressions."
Now they have two problems.

-- Jamie Zawinski, 1997, in alt.religion.emacs

Cost is no object. Profit is unnecessary. All that matters is that construction continue. Japan has dammed all but maybe one river (many of them multiple times), built tunnells through mountains so that villages of less than 100 people can have a bullet-train stop(!! move over Sen. Stevens !!), paved many a riverbed in concrete, eliminated dirt from the cities (almost every square inch is paved), etc., etc.

I recall visiting a dam in Nagano that had special turbines so the water could be pumped back *up* into the reservoir behind the dam during the night (luckily the next dam was less than a mile below!) so that extra power could be generated by this dam in the day during the summer so Tokyoites could have air-conditioning. This dam used more power than it made, obviously. (Economically, this scenario might actually make sense, but it is interesting to think about ... could this happen in the US?).

When I lived in Tokyo they tore up my street every few months relaying pipes. First gas, then water, who knows what else. Then a few months later, since the street had been patched so many times, they repaved it. Streets that are 3 years old are routinely torn up (including the concrete kerb) and repaved. They always looked like they still had years and years left of service in them. In the 30 years my family's lived in Northern Virginia (affluent, high-traffic area) I can only think of 1 or 2 times certain major roads in town were repaved.
      From small: http://regex.info/blog/2007-03-25/403
      To large: http://en.wikipedia.org/wiki/Akashi-Kaikyo_Bridge
The likelihood of the projects (for instance the Akashi Kaikyo Bridge) recouping investments is papered over and never taken seriously, except to BS the public or to rationalize the hidden logrolling which is required to acquire the budgets necessary to build the projects.

--
learnjapanese.poddedcell.net (Step Up Nihongo)

I agree, on XML, but your original post was that you 'keep seeeing' that quote, and was wondering what it meant. The original used regular expressions as the issue rather than XML. The phrase itself seems to have become a meme.

Your original post implied (to me at least) that you were missing the point of the meme itself (if I'm misunderestimating you, apologies), especially since I've never seen it applied to XML before. (Agreed that the validity of the meme for both XML and regexps is at least debatable.) I understand it as saying that any problem complex enough to require mulling over before you even decide on a solution vector of regexps|XML|neural networks|genetic algorithms|laser-toting killbots is likely to have problems with the implementation of the solution as well...

Oh yah?

http://regex.info/blog/2006-09-15/248

What's New
New in the Third Edition are a new chapter on PHP (and upgraded PHP coverage throughout the core chapters), and a completely rewritten Java chapter to reflect changes from Java 1.4.0 to Java 1.5/1.6. Otherwise, there are only minor updates and typo fixes. (For example, if your interest is Perl or .NET, there's little new in the Third Edition that's not in the Second Edition.)

Second edition. A good general reference with specific implementation notes for Perl, Java, .NET, etc. It is by far the most thumbed-through book on my "shelf" (aka, "The pile of books on the corner of my desk"). Good for beginners or experts needing a handy reference.

You wouldn't think so, but it's also a good cover-to-cover read, provided you're interested in that kind of thing.

By Jeffrey Friedl

It would be nice if those computers you have there have access to the internet. There are tons of free resources to supplement language learning.

Here are what internet can provide:

• Online dictionaries
  I recommend the following English Japanese dictionaries:
  Jeffry's Japanese English Dictionary
  SPACE ALC
  Yahoo! Jishou (Yahoo! Dictionary)
• Tutorials online
  I recommend the following website:
  Nihongo Resources
  
• Online news sites
  Since these students are learning Japanese, chances are they don't know enough Chinese characters (2000+ of them) (and grammar) to read your average Japanese newspaper. I suggest news sites written for children:
  Kodomo Asahi (Children's Asahi)

Perl regexps are just more powerful than most - that's why many other languages have Perl-compatible regex support available as libraries or in the language (e.g. PCRE). To you it's cryptic; to people who know Perl, it's more powerful and more readable. See regex.info for Jeffrey Friedl's great book on regexes which covers many languages including Perl.

Kitou = Glans (of the penis)

The word "Kitou" is composed of two Kanji, or pictograph, characters. Each character represents one noun. The first kanji means "turtle" and the second means "head". Put them together and you get "turtle head", a rather visual description of the tip of a penis peeking out of the foreskin.

> I'm not sure what exactly "Nozomi" means, but a search on images.google.com sure didn't give me a bullet train :/

Well, do some more homework and you'll find out that "nozomi" can also be interpreted as wish, desire, or hope . It is also a common woman's name as well as the name of Japan's first mission to the planet Mars.

Asadachi = Morning wood

"Asa" means "morning" and "Dachi" (or rather "Tachi") means "standing". Sometimes "t" is turned into a "d" to make the word easier to say, kind of like how the English word "better" is often pronounced as "bedder". Anyways, if you put the two words together, you get "morning standing". I'll leave it to your imagination to figure out what body part is *ahem* standing.

How so?

If you look at the 6Bone list archives you'll see there was a recent thread on how spammers are already exploiting IPv6 open relays.

IPv6 is no panacea.

How so?

If you look at the 6Bone list archives you'll see there was a recent thread on how spammers are already exploiting IPv6 open relays.

IPv6 is no panacea.

The reviewer forgot to mention the wonderful errata list of the book! Can be found here.

http://regex.info

Jeffrey