Social Media

Finding our brave faces

I agree with Jeffrey Zeldman in that I’m also surprised that George Oates was laid off from Yahoo and her work with Flickr. I also thought that George’s recounting of how she found out she was laid off was telling, and sad.

Once upon a time, Yahoo was the bright and shiny future. Once upon a time, Flickr was one of the most dazzling of the new breed of startups. The success of both was based less on equipment and technology, and more on the people who helped create both companies. How Yahoo treats the people it has let go, is a measure of what the company thinks of itself. Evidently, those still in management in Yahoo, and at Flickr, don’t have a high opinion of themselves.

(An earlier interview with GeorgeMore on the layoffs.)

History JavaScript

Battle of the Bulge

Recovered from the Wayback Machine.

On this anniversary of the World War II Battle of the Bulge, Jules Crittenden provides a comprehensive summary of the battle, as well as a book and other references, and photos.

The photos are especially compelling, as they lack of romanticism of so many WWII photos in books and in other publications. The following photo is of members of the the 82nd Airborne, my Dad’s division, following the 340th Tank Battalion. The photo is from the Life Magazine collection hosted by Google.

82 Airborne following tank

My Dad’s war history has been on my mind quite a bit recently, since reading Norman Costa’s story of his father and his experiences during D-Day. My father was also in the same battle, and in the same regiment. Unfortunately, my father, unlike his, was not comfortable telling his daughter about some of the more difficult moments during the war. As I told Costa in an email, Dad was less reticent with my ex-husband.

Dad…grew up in a time when one shielded “unpleasant” stories from the womenfolk, which means he did not tell me stories of especially difficult times. He did, however, share them with my ex-husband, who passed them on to me.

Dad was, at one time, trapped by sniper fire, and thought he was a goner, until other soldiers managed to kill the sniper. His worst time, though, was leading a small group of men towards a farm with a house designated as a “spotter” house, which should mean the house was safe. However, Dad didn’t know if the house was safe or not, so ordered his men to stay behind, under cover, while he checked the place out. The house was safe, but unfortunately the men took cover in a shell blast “crater”, which got hit by another shell. Dad returned, only to find all of the men dead.

Most of Dad’s war memorabilia was lost during a move years ago, but he gave me the handgun, an M1911, he carried during the war. Dad paid a German POW a package of cigarettes to engrave his name on the barrel, and attached his paratrooper wings and the 82nd Airborne badge to the handle on one side, a photo of my uncle, who was in the Navy during WWII, on the other.


Shock, Awe, Economics, and the Web

Battered into a fetal ball by waves of bad economic news, only surfacing to watch an occasional crash and bash flick, such as Iron Man, I discovered my own personal bailout via Naomi Klein’s book, “The Shock Doctrine: The Rise of Disaster Capitalism”. Oddly enough, it wasn’t something that Klein wrote (though she has many interesting points and I hope to write more on her book at a later time). No, it was a quote by the master of the Chicago School, Milton Friedman, himself, that loosed my death grip on self. As introduction to his book, Capitalism and Freedom, Friedman wrote:

only a crisis—actual or perceived—produces real change. When that crisis occurs, the actions that are taken depend on the ideas that are lying around. That, I believe, is our basic function: to develop alternatives to existing policies, to keep them alive and available until the politically impossible becomes politically inevitable.

The irony that the free market system Friedman loved so well is now experiencing its own “shock and awe”, as corporations grasp at despised government intervention, like a baby its bottle, has not escaped me. But for me, the operative phrase in this quote is “the actions that are taken depend on the ideas lying around”. This is totally irreverent to the problems we’re facing, and I apologize in advance for seeming to trivialize the very difficult times we’re all facing, but when I read this phrase I thought to myself, “Internet Explorer, your days are numbered.”

Consider this: movement forward in the web has been stymied in recent years because, we’re told, thousands of corporate intranets, and millions of corporate employees using these intranets are dependent on tricks and hacks put into place to support Internet Explorer 6. Add to this the, in my opinion, anal fixation that web pages must look the same in every browser, and most of our page design has been stuck like a bug in pitch.

Now that the corporations are downsizing in order to preserve what they can of executive compensation, the machines on which these applications run are being sold for scrape, tossed out along with the other chaff (i.e. employees). And those still employed, frankly, have other concerns than whether IE supports opacity or not.

I don’t believe I’m alone in seeing the Friedmanesque possibilities of our current economic disaster. What better explanation for the recent production release of Google’s Chrome browser? Google released Chrome from its beta utilizing a speed for which the company is not known. After all, isn’t the GMail still in beta? Come to that, isn’t the Google search engine still in beta?

Then there’s the fact that Chrome is currently only supported in Windows, just like IE. Only like IE, as a matter of fact. No, I am sure that Google sensed corporate shock, and moved quickly to displace IE in the hearts and minds of upper management—not to mention the hearts and minds of millions of newly unemployed workers who are no longer subject to the intransigence of corporate IT. If by doing so, Chrome also kicks Firefox, Opera, and Safari in the face in its haste, eh, casualties of war.

I am not displeased by Google’s move. After all, Chrome supports XHTML and some SVG, both of which Microsoft seems incapable of implementing. However, there is some confusion about what Chrome is, or is not, capable of supporting. True, Chrome has utilized the excellent WebKit, which also serves as the soul of Safari. However, as others have discovered and my new experimentation in web design demonstrates, Chrome has a different graphics engine (Skia) than Safari/Webkit. In the interests of “stripping” down the browser to make it lean and mean for web applications, the developers also made it rather, um, unattractive. At least for now. If you view this web page using Chrome, you will see that Google currently does not support the CSS3 text-shadow property, though it does support box-shadow. It also supports border-radius, though badly—the anti-aliasing is less than optimal, as is the support for alpha transparency.

While it is true that text-shadow, box-shadow, and border-radius are CSS3 properties, and thus not part of a released specification, they are supported in Safari 3.1 (and Firefox 3.1 and partially in Opera 9.x). Because of the Webkit tie-in between Safari 3.1 and Chrome, people may be confused when what works in Safari, does not work in Chrome. Well, those people who don’t have other, more pressing, worries.

Screenshot of Chrome in action