A couple of readers let me know lots and lots of links to pictures in my old posts are broken. I checked with my IP provider, and it turns out the links went bad when they moved the site from a Windows server to a Linux server last month.
Windows isn’t case-sensitive when it comes to file names and links. Linux is. A whole bunch of pictures in the images folder have an extension of .JPG but are linked as .jpg in my posts. Windows interpreted, Linux doesn’t. The only way to track down and fix the links is to go through every post from the last five years, look for broken links, and update the file name. So that’s what I’ve started doing, occasionally mumbling “Why the @#$% did I write so many posts?!”
2009 is done. Moving on.
Geek Rant — you may want to skip this
As a programmer, I don’t like the case-sensitive feature one bit. For software I develop on my own to sell to customers, I prefer VB.NET for lots of reasons, one of which is that it’s NOT case-sensitive. When naming my variables and classes, I use what’s called CamelCase, capitalizing what would be the first letter of each word if they were separated …. e.g., TotalTrademarks, DateOfRenewal, BoundRecordset, etc. When I use those variables later, I can type in lower case and VB will auto-correct. So if I type dateofrenewal, it’s immediately converted to DateOfRenewal, which I use as sort of a spell-check. If my lowercase is auto-corrected to CamelCase, I know I typed the variable correctly.
In most of my contractor gigs, the companies have used C# for development — largely because old-time programmers who are now in management believe VB is a toy while C# is for serious programming. And that was true maybe 15 years ago. Now both languages are built on the same platform, call the same code libraries and compile into exactly the same machine code, so pretty much anything you can do with one, you can do with the other. You could even code part of your software in VB and another part in C#, and the compiler wouldn’t care. The difference is in the coding language itself, not the result.
Like Linux, C# is case-sensitive. So if I have a variable named DateOfRenewal and type dateofrenewal in my code, C# doesn’t auto-correct; it flags my variable as undeclared and then I have to go back and type it slowly, using the SHIFT key. And yes, I’ve seen code where a programmer intentionally created one variable with a name like TrademarkDate and another with a name like trademarkDate, which I think is both stupid and confusing.
Anyway, that’s my rant on the subject. I don’t like case-sensitive languages, and I don’t think sane people would want to have file names that are identical other than the capitalization.
Back to fixing all those @#$%ing links now …