New York Times, May 31, 2008:
“This time, it was the top of the crane that fell. The huge pieces smashed into the penthouse of a nearby building, then tore off a row of balconies and plummeted to the street in a shower of bricks, dust and debris. Two men, both workers, were killed.”
Where’s Spider-Man when you need him?
4 responses so far ↓
Jon Maloney // Thursday, June 19, 2008 at 17:18
I am exploring your blog after seeing the link in the BookMooch forum. I enjoyed the Spider-Man 3 video. I haven’t seen the movie yet.
The comments screen doesn’t work in my old Mozilla browser, but works fine in Firefox.
Taneli T // Thursday, June 19, 2008 at 20:16
Thanks for posting the comment, it let me test drive the approving system for comments. Everyone’s first comment has to be approved before it shows on the blog, but after that the rest of them should appear immediately.
I liked Spider-Man 3, it was a fun adventure, and I enjoy how Sam Raimi handles the human drama between characters in those films. Not quite as good as the first in the series, but better than the second.
Good to know about the Mozilla browser too. How old is it?
Jon Maloney // Friday, June 20, 2008 at 7:03
I’m using Mozilla 1.7.12 dated September 15, 2005. There was one more minor release, 1.72.13, which was the final Mozilla release. The successors became Seamonkey and Firefox. I still use Mozilla because of one feature that I use constantly as I browse, and that’s the ability to increase text size by rolling the mouse wheel without pressing any other keys. My screen resolution is 1024×768 which makes the text on many web sites too small for me to read comfortably.
Only about 1 of every 167 visits to my web site is with Mozilla. Here are the browser statistics for 45,289 visits to my web site in June: 79.6% Internet Explorer, 12.7% Firefox, 4.4% Safari, 1.2% Mozilla, 0.6% unknown, 0.5% Netscape, 0.3% Opera, and each of the others was 0.1% or less.
Taneli T // Monday, June 23, 2008 at 11:01
Wow, nearly three years. That’s a lot in web browser years especially with all the Ajax stuff showing up recently in code, but that text size increasing feature sounds like a good one to have sometimes.