RasterWeb!Microsoft wants to help you decide between a PC and a Mac…
They even have this awesome web site to help you do it…
That photo… there’s something… familiar about it…
Can we zoom in on it?
No… More! Can we zoom in on it more!?
Wait… those colors… Zoom more! And rotate it!
Say what!?!? I knew I’d seen those colors before…
So what does it mean!?!?
BarCampMadison3 will take place Saturday, August 28, 2010 from 10:00 AM to 7:00 PM. As of this post, barcampmadison.eventbrite.com show everyone who has registered for BarCampMadison.
I wasn’t sure how long the Eventbrite data would be around (does it disappear after the event?) but since it’s publicly accessible, I figured I’d post it here as well. Feel free to check out the web sites or Twitter streams of people who plan to attend BarCampMadison.
And of course, you can follow @barcampmadison on Twitter as well…
Let’s say you’ve got a file named “file.xml” and want it pretty printed, all indented nice and everything…
For just such an occasion I have a Perl script named “pretty.pl” and I just run my XML file through it like so: cat file.xml | perl pretty.pl
Here’s the code I use:
#!/usr/bin/perl use XML::Twig; use XML::Parser; my $xml = XML::Twig->new(pretty_print => 'indented'); $xml->parse(\*STDIN); $xml->print();
You can even pass it through right as it comes in over the wire: curl http://example.com/data/file.xml | perl pretty.pl
Here’s an example of data from Foursquare without pretty printing. (I used curl to grab the data. Also, I added in some line breaks, just to make it a little more readable.):
<?xml version="1.0" encoding="UTF-8"?> <checkins><checkin><id>123847273</id> <created>Mon, 09 Aug 10 00:50:33 +0000</created> <timezone>America/Chicago</timezone><venue><id>2357761</id> <name>The Kiltie</name><primarycategory><id>79067</id> <fullpathname>Food:Ice Cream</fullpathname><nodename>Ice Cream</nodename> <iconurl>http://foursquare.com/img/categories/food/icecream.png</iconurl> </primarycategory><address></address><city></city><state></state> <geolat>43.107391</geolat><geolong>-88.464475</geolong></venue> <display>Pete P. @ The Kiltie</display></checkin></checkins>
And here’s the same data, again using curl to grab it, and then passing it through the pretty.pl script:
<?xml version="1.0" encoding="UTF-8"?>
<checkins>
<checkin>
<id>123847273</id>
<created>Mon, 09 Aug 10 00:50:33 +0000</created>
<timezone>America/Chicago</timezone>
<venue>
<id>2357761</id>
<name>The Kiltie</name>
<primarycategory>
<id>79067</id>
<fullpathname>Food:Ice Cream</fullpathname>
<nodename>Ice Cream</nodename>
<iconurl>http://foursquare.com/img/categories/food/icecream.png</iconurl>
</primarycategory>
<address></address>
<city></city>
<state></state>
<geolat>43.107391</geolat>
<geolong>-88.464475</geolong>
</venue>
<display>Pete P. @ The Kiltie</display>
</checkin>
</checkins>
I still find Perl extremely useful for this sort of task… I’m sure there are other command line ways to do this, but this one works for me.
(Hat tip to A Curious Programmer where I picked up this Perl code from…)
13 years of blogging… You can browse through the archives if you like. It’s all there.
I just keep going. I don’t know why… probably because it’s hard to stop. I don’t give up easily, and I like to keep trying. Things were obviously very different in 1997 when we started. There were a handful of blogs and you could read them all during your lunch hour. As much as I’m saddened to see an old friend abandon their blogs, I’m often quite pleased to see some are still at it.
This is the part where I thank Dave Winer, because without him, I wouldn’t have started blogging. (Even if he does block me on Twitter.)
I’m considering a few new taglines, perhaps: “Wisconsin’s longest running blog” or something… I dunno, any suggestions?
Anyway, I’m just here to congratulate myself on 13 years of blogging, and hope for another 13 to come… Keep up the good work, self!
The Mozilla folks make it pretty easy to send them crash reports… In fact, I think it was Netscape that first implemented a way for the browser to easily submit a report when something went wrong and your browser crashed.
I did find some instructions for reporting a crash bug in Chrome, and of course Safari can also send crash reports. Hopefully this makes for better software in the future.
In digging into all the crash reporting, I found that Mozilla actually publishes the results they get. Head on over to their crash-stats site and take a look.
You can do custom queries for a few different Mozilla products, so in this screen shot I chose the current stable version of Firefox running on Mac OS X. Hmmm, looks like the Flash Player caused the most crashes…
I couldn’t find if Google or Apple has anything like this, but if they don’t, they should think about it… There’s some great data in there.