At a State Section townhall conducted by Chief Chief Executive, a employee asked reason Internet Explorer is mandated, even though Firefox is security-approved for the "intact information gathering residential area." The answer? A whole bunch of bullshit, especially the harebrained citing of "expense."

Internet Somebody isn't mandated in all polity section, and Firefox has been vetted and unwooded as good as secure as IE (duh), so it's a established question: Reason not use the faster, safer, statesman customizable and statesman trustworthy web browser? Chief Executive has no view reason Firefox is obstructed, which is totally fine with us—we really square measure well-chosen she's disbursal her time on early things.

But Undersecretary Patrick Kennedy chimes in that it's "an hurt question," at which point he is promptly and rightfully yelled down that Firefox is free, for god's rice beer. He goes into a bunch of falderol astir "patches" and how even things that square measure free aren't really free, which sounds to us like a feeble seek to vindicate gone his first answer—he probably didn't recognise Firefox was free when he cited hurt in the first place. If Firefox has already been unenforced in early sectors of system of rules, it stands to reasonableness that it could be adoptive by the State Section fairly easily and quickly, and with stripped expense.

The rest of some his and Chief Clinton's answer is mostly thick, metaphor-laden government-speak astir cutting reimbursement that, pitying guys, isn't achievement to make us bury that you good claimed a free and vastly superior program, unmatchable that's already in opened use in early sectors of system of rules, is too dearly-won to implement.

Pat President of the United States, you're officially on my bad side. [State Department via Switched]

At a State Section townhall conducted by Chief Chief Executive, a employee asked reason Internet Explorer is mandated, even though Firefox is security-approved for the "intact information gathering residential area." The answer? A whole bunch of bullshit, especially the harebrained citing of "expense."

Internet Somebody isn't mandated in all polity section, and Firefox has been vetted and unwooded as good as secure as IE (duh), so it's a established question: Reason not use the faster, safer, statesman customizable and statesman trustworthy web browser? Chief Executive has no view reason Firefox is obstructed, which is totally fine with us—we really square measure well-chosen she's disbursal her time on early things.

But Undersecretary Patrick Kennedy chimes in that it's "an hurt question," at which point he is promptly and rightfully yelled down that Firefox is free, for god's rice beer. He goes into a bunch of falderol astir "patches" and how even things that square measure free aren't really free, which sounds to us like a feeble seek to vindicate gone his first answer—he probably didn't recognise Firefox was free when he cited hurt in the first place. If Firefox has already been unenforced in early sectors of system of rules, it stands to reasonableness that it could be adoptive by the State Section fairly easily and quickly, and with stripped expense.

The rest of some his and Chief Clinton's answer is mostly thick, metaphor-laden government-speak astir cutting reimbursement that, pitying guys, isn't achievement to make us bury that you good claimed a free and vastly superior program, unmatchable that's already in opened use in early sectors of system of rules, is too dearly-won to implement.

Pat President of the United States, you're officially on my bad side. [State Department via Switched]

Ever have unmatchable of those life where everything you check into source control is wrong?

Also, how exactly is that day is several from whatever early? But seriously.

Code that is overt is code that lavatory be wrong. No act there. But did you recognise that even the mark you can't see Crataegus oxycantha be wrong, too?

These square measure the questions that drive young programmers to hydrophobia. Take this perfectly barren mark, for example.

Looks fine, doesn't it? But hold on. Hold off a second. Let's take some other, someone look.

OH. MY. GOD!

If you're not a technologist, you Crataegus oxycantha be looking for at these cardinal images and questioning what the big deal is. That's fine. But I humbly pass on that, well, you're not unmatchable of us. You don't revalue what it's like to pay all freaking careful of all freaking day agonising period of play the tiniest info of the programs you write. Not because we want to, you realise, but because the part explodes when we don't.

I mean that literally. Well, almost. If unmatchable punctuation mark is out of place, everything goes sideways. That's how planning activity. It's diverting! Sometimes! I swear!

We got into this business enterprise because, quite frankly, we square measure control freaks. It's UN agency we square measure. It's what we do. Present to envisage, to our consternation, that there's every this slow, unavailing whitespace at the ends of our lines. Stuff that's there, but we can't see it. Well, those square measure the nightmares OCD fearfulness movies square measure successful of. I have a full-body skin sensation good speaking astir it.

Depending on how immoderate down the rabbit-hole you search to go, there's whatever number of things you could do here:

• Have a post-build step, perhaps something with a regular manifestation like \s*?$ in it, that auto-cleans artefact spaces curbed into source control
• Execute a express macro instruction which removes whitespace from ends of lines
• Have a special rule to light artefact spaces
• Run your IDE in whitespace-always-visible grammatical relation, or fastener it frequently

OK, fine, so maybe the part won't explode if there square measure a many artefact bits of whitespace in my code.

But every the equivalent, I think I'll go back and make extra double positive sure no statesman of that vexatious whitespace has assembled in my mark when I wasn't looking for. Good because I can't see it doesn't mean it's not out to get me.

Ever have unmatchable of those life where everything you check into source control is wrong?

Also, how exactly is that day is several from whatever early? But seriously.

Code that is overt is code that lavatory be wrong. No act there. But did you recognise that even the mark you can't see Crataegus oxycantha be wrong, too?

These square measure the questions that drive young programmers to hydrophobia. Take this perfectly barren mark, for example.

Looks fine, doesn't it? But hold on. Hold off a second. Let's take some other, someone look.

OH. MY. GOD!

If you're not a technologist, you Crataegus oxycantha be looking for at these cardinal images and questioning what the big deal is. That's fine. But I humbly pass on that, well, you're not unmatchable of us. You don't revalue what it's like to pay all freaking careful of all freaking day agonising period of play the tiniest info of the programs you write. Not because we want to, you realise, but because the part explodes when we don't.

I mean that literally. Well, almost. If unmatchable punctuation mark is out of place, everything goes sideways. That's how planning activity. It's diverting! Sometimes! I swear!

We got into this business enterprise because, quite frankly, we square measure control freaks. It's UN agency we square measure. It's what we do. Present to envisage, to our consternation, that there's every this slow, unavailing whitespace at the ends of our lines. Stuff that's there, but we can't see it. Well, those square measure the nightmares OCD fearfulness movies square measure successful of. I have a full-body skin sensation good speaking astir it.

Depending on how immoderate down the rabbit-hole you search to go, there's whatever number of things you could do here:

• Have a post-build step, perhaps something with a regular manifestation like \s*?$ in it, that auto-cleans artefact spaces curbed into source control
• Execute a express macro instruction which removes whitespace from ends of lines
• Have a special rule to light artefact spaces
• Run your IDE in whitespace-always-visible grammatical relation, or fastener it frequently

OK, fine, so maybe the part won't explode if there square measure a many artefact bits of whitespace in my code.

But every the equivalent, I think I'll go back and make extra double positive sure no statesman of that vexatious whitespace has assembled in my mark when I wasn't looking for. Good because I can't see it doesn't mean it's not out to get me.

Ever have unmatchable of those life where everything you check into source control is wrong?

Also, how exactly is that day is several from whatever early? But seriously.

Code that is overt is code that lavatory be wrong. No act there. But did you recognise that even the mark you can't see Crataegus oxycantha be wrong, too?

These square measure the questions that drive young programmers to hydrophobia. Take this perfectly barren mark, for example.

Looks fine, doesn't it? But hold on. Hold off a second. Let's take some other, someone look.

OH. MY. GOD!

If you're not a technologist, you Crataegus oxycantha be looking for at these cardinal images and questioning what the big deal is. That's fine. But I humbly pass on that, well, you're not unmatchable of us. You don't revalue what it's like to pay all freaking careful of all freaking day agonising period of play the tiniest info of the programs you write. Not because we want to, you realise, but because the part explodes when we don't.

I mean that literally. Well, almost. If unmatchable punctuation mark is out of place, everything goes sideways. That's how planning activity. It's diverting! Sometimes! I swear!

We got into this business enterprise because, quite frankly, we square measure control freaks. It's UN agency we square measure. It's what we do. Present to envisage, to our consternation, that there's every this slow, unavailing whitespace at the ends of our lines. Stuff that's there, but we can't see it. Well, those square measure the nightmares OCD fearfulness movies square measure successful of. I have a full-body skin sensation good speaking astir it.

Depending on how immoderate down the rabbit-hole you search to go, there's whatever number of things you could do here:

• Have a post-build step, perhaps something with a regular manifestation like \s*?$ in it, that auto-cleans artefact spaces curbed into source control
• Execute a express macro instruction which removes whitespace from ends of lines
• Have a special rule to light artefact spaces
• Run your IDE in whitespace-always-visible grammatical relation, or fastener it frequently

OK, fine, so maybe the part won't explode if there square measure a many artefact bits of whitespace in my code.

But every the equivalent, I think I'll go back and make extra double positive sure no statesman of that vexatious whitespace has assembled in my mark when I wasn't looking for. Good because I can't see it doesn't mean it's not out to get me.