Sunday, September 22, 2013

Saints win, Cowboys win. Just need a Miami win and all will be right in my house.

Not to mention the Eagles, Redskins, and Giants lose.

Funny when the NFL official starts his call with "Here's the situation".


Murray TD in 2nd QTR should have been a touchback. Why you ask? #Cowboys


DeMarco Murray scores a TD in the 2nd quarter of the Cowboys Rams game. But was it a TD?

Murray did not have clear possession of the football at the exact point it touches the pylon. Check out the picture above. This is right when the ball hit the pylon. You know this because the pylon moves when he hits it with the ball, but in this picture it is just leaning slightly, so this  is right when the pylon is hit. With that in mind, look at his hands and the ball. He does not have possession. The ball is not touching the ground yet, and Murray's feet are in-bounds, so if he would have possession this would be a TD.

What this means is that the ball is fumbled into the end zone an then out of bounds, which would make it a touch back and the Rams would take possession.

I'm a Cowboy fan, so I am glad it was not called, but the intricacies of the NFL fascinate me, and it is a big reason why I love this game..


Murray is earning his paycheck today. #cowboys

Sent from my Droid Charge on Verizon 4G LTE

Wednesday, September 11, 2013

Resond.js, Modernizr, html5boilerplate, html5shiv, etc. --> IE, the Al-Qaeda of browsers.

I remember my first real job doing Web stuff. I was working Working for Verizon SuperPages, and had to build our sites using this template based CMS. We would find ways to hack the CMS by putting code in places that weren't design for it, and customizing sites. This was 2001 - 2005. It was pretty much an IE world. But even then, we an issue came up I would check my sites on a Mac we had up there that was running IE5. What a mess. I remember being so relieved when the Mac/IE5 browser feel off the map. Little did I know that this was only the beginning.

The next layer of IE hell was IE6. Because of Windows Vista being crap, people stuck with XP for a long, long time (me being one of them). And because of that, people stuck with IE6 a long, long time. IE6 didn't really prompt you to upgrade. Then, when all the cool HTML5/CSS3 stuff started coming out, IE users were left in the dark. Even when IE9 came out, which was somewhat HTML5/CSS3 compatable, its usage was pretty low, because of all the XP machines still out there that couldn't upgrade to IE9 even if they wanted to. Most XP machines were 32bit and IE9 ran on 64bit systems, which was mostly Win Vista, and people were slow get rid of XP. There for a while you could buy PCs with either OS, and lots were still choosing XP (me being one of them).

So now IE6 is pretty much out of the picture, although I just had a project last week that required IE6 comparability (now where did I put that PNG hack?). But IE7-8 are really not much better than 6. Yes, I can use transparent PNGs, but there are all kinds of rendering issues, as well as little to no HTML5/CSS3 support. Granted, IE9-10 have a pretty big numbers, but some really cool stuff just doesn't work in IE7-8 and does not degrade gracefully. 

This is where all the hacks, patches, etc are still needed. Luckily frameworks like jQuery have a lot of built in IE fixes, but you still need Resond.js, Modernizr, html5shiv, etc. to fix some specific issues. And those issues can turn your cool-ass web site/app in to crap if you don't find an IE solution.

This is a very worn-out old rant that many have made over and over again. It just still comes up so often that I have to purge from time to time.

The good news is that if all browsers were equal there would be a big "make website" button somewhere that would crap out a site, and my work and pay would substantially decrease.

Sunday, September 8, 2013

Football rant: Bad calls in Saints v Falcons game. Yes, I am biased, and yes the Saints did win, but...


They spotted this about a foot shy of the 1st down. Really? I know the yellow line is not official, but when they brought the chains out, the first down was right on the yellow line. His knees are not down and the ball is over the marker. Should have been a 1st down.



Notice the Falcons O lineman tackling the Saints pass rusher? That would be holding. Not called.



The Saints running back is clearly out of bounds, but the Falcons defender continues to make the tackle and pulls him to the ground a good two feet out of bounds. Should have been a flag on Falcons. Not called.



The Saints on this play were flagged for hitting the QB. This is a close call (I guess), but the problem with the rule is that the defender makes his move to make a hit on the QB when the QB is still running upright, but the QB goes into a slide after the defender has already started his motion to make a hit on him. How can the defender possibly make that adjustment at the last second? I think it's a bad call, or maybe a badly defined rule. If you are the QB and you're about to get him, you can simply go into a slide and get the call every time. 


That's my (somewhat joking) rant. I am so glad the NFL is back!

Go Saints! Go Cowboys!

Day started with a bang, then oyster po-boy (Cajun Food), football (Saints Win), freelance work ($$). I win.