new naming conventions: watch your step

[Brent Putman]

On 10/16/13 9:56 AM, Ian Young wrote:
> On 16 Oct 2013, at 14:32, Marvin S. Addison <marvin.addison at gmail.com> wrote:
>
>> A Mac alternative is to create a case-sensitive HFS+ filesystem (e.g. a 
>> file-backed sparse volume) and copy your Eclipse workspace there for the 
>> refactoring work.
> That's a great tip, thanks!

I like Marvin's idea too, had not thought of using a file-backed volume
like that. 

Issues like this are why for many years now, when I get a new Mac, I
always reformat the machine's entire disk with the case-sensitive HFS
variant.  That way I never have to worry.

My rationale is that just about anything I do as a developer is probably
going to be deployed in a case-sensitive environment (Linux 99.9% of the
time nowadays) and so developing in a case-sensitive environment
eliminates "surprises" at runtime.  (Plus I'm just fundamentally a Unix
guy and like case-sensitivity).

Of course, the reverse also happens:  I've been bitten on my Macs by
certain software vendors (looking at you Adobe...) that apparently only
do QA for their products on Macs with case-insensitive filesystems,
leading me to have to figure out myself that to eliminate some segfault,
etc, I need to symlink Foo.dylib to foo.dylib, because their developers
mucked up the case in their linker/dependency config.

But I still think it's worth the trouble, personally.