On Monday, Adobe released a press release that it had completed its acquisition of Macromedia, Inc. on December 3rd, 2005. This week, they’re starting to actually integrate their product suites, Creative Studio and Studio 8.

So today, it’s time for us to reflect on a few of Macromedia’s crowning achievements…

They single-handedly destroyed ColdFusion after purchasing it from Allaire by forsaking the “small, robust footprint” mentality and adding an antisocial, schizophrenic feature set which didn’t like to get along with itself. This they did instead of fixing its core issue: instability, which prevented its widespread proliferation and acceptance in Enterprise environments. Not to be outdone, they eventually scrapped CF, and released a new “MX” — no doubt a short-hand version George Carlin’s sixth dirty word, adopted by its developers who typed “I hate this new mx!!” in company e-mail — version based on Sun’s ill-gotten, red-headed, bastard-child: JavaServer…

Machine after machine has succumbed to the quagmire that is Macromedia Studio: an obese application which insists on digesting more than its share of the file types you use most — from the tiniest of GIFs and JPEGs to the simplest of JavaScripts and HTML files that you’d quickly open in the Picture Viewer or Notepad — into its esurient entrails, not to be seen for up to ten minutes while its associated application finally opens with a multitude of windows asking you what you’d like to do next. I’d like to see the damn file I tried to open, thank you…

They destroyed a number of popular websites by creating chromeless Flash animations which give you full-page Advertisements inside your current browser window, effectively blocking the majority of content you’re trying to read, and not even your pop-up blocker can stop them…

Good riddance.

It’s pretty clear that Adobe’s going to focus on the creative side, especially merging PDF and Flash. With any luck, they’ll get rid of that ravenous, mangy dog, ColdFusion-MX, and open the door for someone else to write a real CFML server (better yet, a binary interpreter like CLI-PHP!) that doesn’t cost upwards of $1300 Startup and $90K/year in staffing to support it.

Seems James Lileks released another book last month, and I didn’t even notice until today…

Man! While Monty’s on the subject of zealots (which, let’s be honest, is always a great topic), why am I getting so many e-mail complaints and comment spams dogging this site for nothing other than its lack of CSS?

Firstly, I simply don’t care if you’re running the latest piece of animal dung with a name stolen from a deplorable 1982 movie starring Clint Eastwood. You’re a 7% minority by our statistics.

Secondly, if you consider yourself a web designer and you can’t make a page that looks right in all browsers, you need to find another form of employment. Or maybe find a form of employment — the real world detests your kind of attitude.

Thirdly, we have no intention of validating with XHTML 4.01 Strict. Why bother, when what we’re doing works? The page you’re looking at looks exactly the same in every single browser that comes here save for Lynx.

Fourthly, if you have no other complaint about this site than its lack of CSS, then obviously we’re doing something right.

CSS has become the Whine of the Uberdork: “Technical people can be creative, too!”

Regardless of what an Uberdork can do making a Round CSS Layout, it still won’t give them any sense of design skill or color coordination. It expands their possibilities, yes, but for the most part, their sites are still going to be ugly. Form & Function will most always be at odds.

It’s a fact that the *vast* majority of sites carrying those “CSS Certified!” banners DO NOT conform the specification they’re carrying the banner for. I’m one of those freaks who clicks it on every site I see it on, and I rarely hit a single site that conforms with no errors — and I’ve only ever seen two sites at all that got no errors, and no warnings.

With the majority of the published Templates, Skins and Designs out there using CSS, at least 50% of them will not work in one browser or another. Commonly, those designs carry the banner, “Your browser sucks! Download TPFKAN Now!” Logic dictates that they should instead read:

“I don’t like your browser because I’m too much of a zealot to believe real-world statistics showing a super-high IE market share, and thus the entire market share is using an inferior product which does not conform to specifications, and even though 50% of the people in the world are using IE, the specification is what is standard and not what people are using. Therefore, you should go and download TPFKAN because I’m too much a lazy prick to fix my code which is most probably based on an RFC rather than an actual, certified standard.”

Thus far, the majority of the CSS styles you see out there are written by Technical Programmers who do it just so they can complain about the limitations of the most popular browser by far (kudos to Mr. Bill).

I have no problem with CSS, but some common sense needs to be used when designing pages with it. We do make use of CSS — a lot of it! We have a tabular structure, all decked out with CSS inside. It’s relatively tidy, and people seem to think it’s a decent design, aside from complaining that it’s not in such-and-such DTD.

As for TPFKAN, I hate it. The best way to screw up IE forever is to install TPFKAN. Actually, an even better way is to uninstall TPFKAN, which will take half of the settings and HKLMClasses with it, just like its mother product did.

People love to complain about how bad Netscape was, and forget that Firefox is just a new version of the same old junk.

I read an interesting article by the father of a Marine on-leave, who relayed the sentiments of his son:

[According to said Marine] morale among our guys is very high. They not only believe they are winning, but that they are winning decisively. They are stunned and dismayed by what they see in the American press, whom they almost universally view as against them. The embedded reporters are despised and distrusted. They are inflicting casualties at a rate of 20-1 and then see shit like “Are we losing in Iraq” on TV and the print media. 

Today’s the day that we’re supposed to be thinking about all of our Veterans, and about those who are currently deployed. That speaks volumes.

And you can’t argue with it.

For all your sacrifices, guys and gals from past to present, I, for one, Salute you. Thanks for being there and doing what needs to be done.

Now, the amusing part here is *not* the sign itself. To me, it’s just a moose-crossing sign. I’ve seen plenty of those in Canada.

This one, however, is located just outside of Linton, Indiana. On a farm. Where they raise … Buffalo.

Buffalo.

Not moose.