It really really is. I’m on the windows download page. Looking at a list of six different available downloads. There’s PHP 5.3, and there’s PHP 5.2. Some say “thread safe” and some say “non thread safe”. They all say x86, which is the 32-bit version. There’s a dropdown at the top of the page which lists these. The dropdown also lists x64 downloads which are for 64-bit windows systems. But there’s no download actually available for 64-bit. Why are these in the dropdown then? There are also VC6 and VC9 versions. Wtf is that? Oh…if you read a little bit…those stand for Visual C version 6 and Visual C version 9. You know, I’m as big a geek as the next guy, and I can sort of run a C compiler, but why the fuck do I need to be exposed to this garbage?
Sooooo Busy »« Cross-browser issues explained
Just a note…while I’m working on this website, trying to fix their broken grid on the members’ page.
Use margin in your CSS. Prefer margin to padding. Usually if one of the browsers will act funny, it will be IE. So code your HTML/CSS to the other browsers, and use conditional comments to take care of the IE irregularities. That’s how the blueprint guy does it. I’ll go with that answer.
And the main culprit is margin/padding. IE has some weird rules about collapsing margins/padding together…only in the vertical direction.
Something like that…honestly who the fuck wants to know about this? Only someone who is getting paid.
PHP On Windows is a Goddamn Mess »« Facebook URL Hacking
I just got a request from a client of mine to link to their new facebook account. While I was checking it out I just noticed how weird this URL to their facebook page is:
facebook.com/home.php?#!/pages/SDC/292654549892?ref=ts
That sure-as-shit looks like a unix-style shell script to me. Everything after the home.php? at least. I wonder if they use that to their advantage? Must be…it’s something I have to look at more in-depth later.
Cross-browser issues explained »« Email Server Tip
