Goodbye Stupid TextReplace Utility

As expected, someone pointed out a simple utility to handle my command-line search and replace needs: gsar – General Search And Replace utility. It does what I need it to do quite nicely. It doesn’t allow for regular expression searches, but I don’t need that anyway. So my TextReplace utility is officially scraped. Thanks to Mike Gunderloy @ Larkware (previously RSS subscribed).

Stupid TextReplace Utility

Is there a decent (note, my standards are low) command line text file search & replace utility around? Everything I’ve found is a perl script, requires Ruby or costs money. Not that I can’t afford $25 for a usable utility, but I don’t think $3 / line of code is worth it. I built an ultra-simplistic .NET utility that was 8 lines of code (not including error handling, usage guide and license) that just takes a single file name, search regular expression and replacement text and uses the built in regular expression object to do the replacement.

I expect that someone will point out something ultra-obvious to me, and I’ll send my ultra-simplistic code to the recycle bin. If not, I’ll post the 8 lines of code (plus the error handling, usage guide and license).

Designer Think About Pagelayout

Certainly not as bad as being found by searching on “shmuck“, but I got a interesting Google referral today – “designer+think+about+pagelayout“. My site come up as the top hit for that search (at least it does right now). The question is – did the searcher start with that search, or was that a refinement? I know sometimes when I Google, I come up with some strange search strings as I try to weed out the irrelevant deadwood. The joys of full text search…

Response to Space Shuttle Loss

For me personally, it had been quite an exciting week for Science and Technology. Internal Microsoft conference, hearing Ray Kurzweil speak, dinner with other webloggers – I was pumped. But like every else this morning, I am deeply saddened by the news of the loss of the Space Shuttle Columbia. The TV just reported that a senior US official has confirmed that there is no hope for the survival of the crew.

I have two immediate reactions beyond the sadness. First, I am in awe of the people who risk their lives in the pursuit of Science. So many of us reap the benefits of the risk and sacrifice of these heroes. It gives me a new perspective since the biggest risk of my job is carpal tunnel syndrome and my biggest sacrifice is time away from my family. Second, several reporters on the TV this morning are asking questions about the future of the Space program. Dan Rather pointed out that there are only 3 shuttles left and that the most recent one was built more than 10 years ago. In my opinion, the only tragedy bigger than the loss of the crew would be the loss of the space program itself. In the wake of a tragedy, there will be an inevitable slowdown. But tragedies like this mean more needs to be done, not less. How far has technology come in just the 10 years since the last shuttle was built? How much better and safer could we an orbiter built today be? From modeling to simulation to on-board instrumentation, Moore’s law tells us that computers are 1000 times faster today than they were when the Columbia was built 20 years ago. Let’s take that knowledge and put it to use.

Dinner, Weblogs & Code

Training for 8 work days + pregnant wife = much less time for blogging. But I did make it out to Sam Ruby‘s Weblog Gathering. Full list of attendee’s is available at Anita Rowland’s weblog (no RSS feed 😢). Had a great time.

Highlight for me was meeting Miguel de Icaza of the Mono project. He showed of Mono on his laptop plus took the time to explain why they chose the licenses they did. But the coolest part was first meeting him. When I realized who he was, I introduced myself and expressed how impressed I was regarding Mono’s progress. His response: “You guys have built a great platform.” I wish all interactions between commercial & non-commercial software advocates could be so respectful. (no flames please – I realize my employer has been equally at fault for not being respectful. Hopefully, we’re changing that.)