in reply to Re^2: (OT) Fixing OSX's biggest weakness as a dev platform
in thread (OT) Fixing OSX's biggest weakness as a dev platform

The objection, nonetheless, can be sustained. Not every Unix filesystem is case-insensitive; Perl certainly doesn't care. If, when faced with an established system that “does not do as you prefer,” you fundamentally redefine that such a system in such a way that will break thousands of core applications for that system ... that's just a little too much hubris.

Replies are listed 'Best First'.
Re^4: (OT) Fixing OSX's biggest weakness as a dev platform
by dragonchild (Archbishop) on Apr 10, 2008 at 18:34 UTC
    I swear I addressed that concern in my original post, which is why I discussed partitioning the bootdisk into a standard partition for the system and a non-standard case-sensitive partition.

    And, for the record, Perl -does- care. It just doesn't force you to worry about it if all developers don't use case-sensitivity in their package names. But, that's an open hole. For example, the current plan of adding a 'x' (in lowercase) for extensions. DBIx, CGIx, etc. What happens if you have a company called CGIX and your module namespace is CGIX:: ?

    My criteria for good software:
    1. Does it work?
    2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
[reply]
[reply]
        You're SOL. *shrugs* In practice, that happens rarely. The CGIx/CGIX one, I've run into.
        My criteria for good software:
        1. Does it work?
        2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
[reply]
        Be like Java, com::apple::CGIx edu::cmu::cs::bovik::cheese
[reply]

In Section Meditations