Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror

Comment Re:Tools are judged ... (Score 1) 329

On the other hand, the local auto mechanic probably has a dozen wrenches and a parts truck that comes around every other day that can bring a new one in for nearly zero overhead. So she might be willing to accept a higher failure rate.

Using male gendered pronouns for overwhelmingly male-dominated professions isn't sexism. If you threw a rock into a crowd, you'd hit more male teachers than female mechanics. It's okay to assume a mechanic is a "he" and a teacher is a "she".

Or, alternately, go whole hog. Instead of someone working in aerospace or other sensitive area, say a woman working in aerospace or other sensitive area.

Your last paragraph suggests that your pronoun gendering may have been intentional and part of a larger issue you wished to promote. If so, bravo! I award you one Internet point for being aggressively subtle.

Comment Re:It's just an issue that's gotten too polarized (Score 5, Insightful) 618

This is one of those things that SXSW doesn't want to burn a lot of calories on trying to wrangle. SXSW is still mostly focussed on music and movies. Nerds fighting over video game politics are not in the wheelhouse.

Put another way, you go to SXSW to have a great time. You do not go there because you want to fight over ideology. Nobody from the alt-rock music scene is making angry Tweets because the alt-country guys have a venue, nor vice versa. As far as SXSW is concerned, both factions are music fans who might find common ground, but otherwise are not interested in open warfare.

Activists on games, they're not so chill. (They'll become chill, after gaming has passed through the "Fonzie Barrier," where rebellion and fear mellow and become folksy humor.)

TL;DR: SXSW isn't interested in burning resources on your gay slapfight over who's right on the Internet.

Comment Re: Chrome (Score 1) 97

The code for the DRM module Firefox uses is not part of the Firefox build system, but is downloaded at runtime. This can be done whether it's a Firefox built by Mozilla or not. So the DRM question has no bearing on whether you can call your version Firefox or not.

This series of blog posts: http://blog.gerv.net/2010/01/p... explains why Mozilla doesn't let just anyone call their modified version "Firefox".

Gerv

Comment Re: Haha. (Score 1) 97

The bug is unfixed for philosophical reasons, not because it's hard to fix. The Bugzilla developers feel history should be immutable.

And there has been no rewrite into another language since that bug was filed; Bugzilla as released by Mozilla has always been in Perl.

Gerv

Comment Re:"an act of social provocation"? (Score 1) 367

The funny (tragic) part is that the kind of people who tend to be strongly pro-gun, also tend to be strong against social programs that could prevent a great deal of the violence typically associated with guns.

Ain't that the truth...

It's not really the truth. If you doubt it, go to the neighborhoods in your city most thoroughly covered by "social programs."

I wouldn't go there unarmed, but that's up to you.

All of those violent neighborhoods would benefit from more of the law-abiding residents being armed to the teeth. The old saying goes "an armed society is a polite society," as nothing deters assholery so much as the sudden onset of room temperature-ness.

Comment Re:The Blame Game (Score 1) 1532

"Beyond that, failure to raise the ceiling would mean missed payments on existing U.S. government debt. And that might have terrifying consequences."

According to what I was told yesterday, this is unconstitutional. Debt payments _will_not_ be missed. http://blogs.reuters.com/breakingviews/2011/06/28/default-not-an-option-under-u-s-constitution/

It would seem that Krugman is basing his entire article on incorrect information. The dollar will not become insolvent. The stock markets may crash, but that would only be due to canceled government contracts and 800 000 people out of governmental work.

Comment Re: Sounds good to me (Score 2, Informative) 555

http://www.ncausa.org/i4a/pages/index.cfm?pageid=71

"Brewed coffee should be enjoyed immediately!
"Pour it into a warmed mug or coffee cup so that it will maintain its temperature as long as possible. Brewed coffee begins to lose its optimal taste moments after brewing so only brew as much coffee as will be consumed immediately. If it will be a few minutes before it will be served, the temperature should be maintained at 180 - 185 degrees Fahrenheit. It should never be left on an electric burner for longer than 15 minutes because it will begin to develop a burned taste. If the coffee is not to be served immediately after brewing, it should be poured into a warmed, insulated thermos and used within the next 45 minutes."

Sounds like McDonalds was doing it right. I guess the woman that burned herself was unfit to experience coffee. Are you?

Comment Regexp::Assemble (Score 1) 190

Note first, I am _not_ saying to replace your call to grep with a call to perl. Perl _is_ fast on assembling strings into a great matching system, but it still takes a _very_ long time to parse, say, 65000 separate strings.

So combine them all into one. Use Regexp::Assemble. With a little bit of fidgetting, it works with GNU grep, as well. Here's an example script, that I've named regex-opt:

!BEGIN regex-opt.pl!
#!/usr/bin/perl
use strict;
use Regexp::Assemble;

my $gnu = 0;
if ((defined $ARGV[0]) && $ARGV[0] eq '-gnu') {
        shift;
        $gnu = 1;
}

my $ra = Regexp::Assemble->new;
while () {
        $ra->add($_);
}

my $string = $ra->as_string();

if ($gnu) {
        $string =~ s/\\d/[0-9]/g;
        $string =~ s/\(\?:/\(/g;
        $string =~ s/([()?|]{})/\\$1/g;
}
print $string;
!END!

So, you have a file with your tens of thousands of lines of patterns to match. Ok, ./regex-opt < patterns.txt > matchpattern.re. This may work with egrep, but it's perl regex syntax, so maybe not completely -- procmail | egrep -f matchpattern.re

With 65000 lines, GNU grep takes about half an hour for the tasks I give it. After assembling all 65000 lines into one expression, even when that expression is _megabytes_ in size, it loads quickly and has the speed of a decision tree.

So, as you accumulate new patterns, output them to a file. Also, _always_ keep your list of separate match patterns -- I'm not sure how well this package can handle reparsing a regex back into itself. Do matches like so:
egrep -f <(cat matchpattern.re newpatterns.txt)

and once a week,
cat allpatterns.txt newpatterns.txt | regex-opt > matchpattern.re; sort -u allpatterns.txt newpatterns.txt > temp.txt && mv temp.txt allpatterns.txt && rm newpatterns.txt

Slashdot Top Deals

Money cannot buy love, nor even friendship.

Working...