I even use it at work (using PortableApps.com).

But some sites (ok, only StackExchange sites) I visit I get multiple popups asking for my user name and password. Because I’m behind a firewall I have to enter my credentials, no big deal. But they don’t work! So I have to hit Cancel. Not just once, but, like, 4 times!

Annoying Popup

Annoying Popup 2

And it’s not the HTTP proxy, it’s asking for a “moz-proxy”.

I finally decided to Google my issue. I found some reports of others with the same issue. (Ironically, the last page was from a StackExchange site and produced the error.)

When I found a page suggesting it was a Firebug issue I opened it and found a bunch of “407 Proxy Authentication Required” errors for http://sockets.ny.stockexchange.com.

I also found these errors in the Javascript Console.

When I saw the “ws” protocol I was pretty sure the issue was with web sockets.

I decided to look to see if I could turn this off.

Google didn’t provide any obvious hits, but at the bottom of this page it mentioned turning on web sockets. So I looked in “about:config” and filtered on “socket”.

Sure enough, I was able to disable web sockets! Hurray! And now I don’t get those popups! Problem solved!

(This bug seems to be related.)

(Maybe I can make this guy hate Firefox a little less.)

More discussion and a  possible solution.

I decided to give it a try by setting a goal of running in the 2012 Corporate Cup Run.

I just got back from my 5th run. 1.5 miles around the neighborhood. And I can honestly say, I hate exercise. I don’t get any pleasure (read: endorphins) from exercising. I am listening to Java Posse so I did get a couple of chuckles along the way. But boy am I beat.

April 14, 2012 show

To follow up with the discussion, you need to set your Spring config like so:

<bean id="quartzScheduler" class="org.springframework.scheduling.quartz.SchedulerFactoryBean">
    <property name="triggers">
        <list>
            <ref bean="XXXXXXXXXXXXXXXXXXXX" />
            <ref bean="XXXXXXXXXXXXXXXXXXXX" />
        </list>
    </property>
    <property name="autoStartup">
        <value>${service.quartz.autostart}</value>
    </property>
    <property name="quartzProperties">
        <props>
            <prop key="org.quartz.scheduler.skipUpdateCheck">true</prop>
        </props>
    </property>
</bean>


Quartz ‘phoning home’ at start up.

From Effective Java:
More computing sins are committed in the name of efficiency (without necessarily achieving it) than for any other single reason—including blind stupidity.

—William A. Wulf [Wulf72]

We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil.

—Donald E. Knuth [Knuth74]

We follow two rules in the matter of optimization:

Rule 1. Don’t do it.

Rule 2 (for experts only). Don’t do it yet—that is, not until you have a perfectly clear and unoptimized solution.

—M. A. Jackson [Jackson75]

When I started programming I thought the goal was to produce code that was fast. So I wrote concise code without regard for readability. Now, I lean toward readability. I guess I’m just trying to differentiate performance and optimization. Performance is good. (Premature) optimization is bad. I struggle with this because I find it easier and more enjoyable working with the details and not at a system level.

I was thinking of my optimization categories and thought I needed to rethink my categories. First we have the “value” optimizations: colors, quotes around urls, combining values. These are all “safe”. Also “safe” was the removal of characters that don’t even get parsed: whitespace and comments.

The next level of optimizations I think of as “declaration” optimizations: optimizations that are dependent of the declaration and optimizations that are just declaration optimizations. I can’t compress the font-weight values unless it is for the font-weight declaration.

“(declaration) block” optimizations: whitespace? comments?

“rule” optimizations: combining rules, removing empty rules

“rule-set” optimizations: combining rules

“style sheet” optimizations

“gzip” optimizations: making anything lowercase

The auto industry has received a lot of media attention in the last year. I just wanted to jot down my thoughts about bailouts and recalls.
First, the bailouts. Looking back I am glad the gov’t bailed out GM. At the time I didn’t like the idea because 1) it was coming from a fund created for bailing out the finance sector and 2) I didn’t like the idea of bailouts. I didn’t like the “too big to fail” argument. The bigger they are, the harder they fall, but they still fall. I’m glad the fed wasn’t as shortsighted. I’m glad that GM was helped and believe that if the fed hadn’t bailout GM and the financial sector we would be in a much worse situation.

I wish they hadn’t helped Dodge/Chrysler. I’m never been a fan. Even the Viper received little respect from me. When I see my friends driving a Chrysler I point and snicker… well, at least in my head. (Sorry Eric and Hope!)

I’m so proud of Ford! I feel like a parent and my step-child just won the spelling bee! They haven’t been admired by me in the past, but they’ve made some smart moves in the last decade and I’m willing to make ‘em part of the family. (In fact, the last car we bought was a Ford.)

Too bad for Toyota

I feel sorry for Toyota. I believe they make quality cars. Even now, after the recalls I’m thinking that maybe I can get a deal now on a Prius with all the bad publicity Toyota has received. The loyal customers are the ones who will probably feel burned the most. I keep wondering how my Toyota-fan friend is feeling. A co-worker I talked to
Toyota employee thinking there was some gov’t conspiracy.
Dodge/Chrysler can die. Snicker and point at friend’s cars.