[gopher] Re: Item Type Suggestions

["Jay Nemrow" <jnemrow@xxxxxxx>]

Constantly trying to prognosticate and plan for some unforeseeable
future also means that products never get made.  I would give you a
cute example (like the y2k bug), but it is hard to make an analogy to
some product everyone knows about that never got made - perhaps Duke
Nukem 2008.

On 7/10/08, JumpJet Mailbox <jumpjetinfo@xxxxxxxxx> wrote:
> Expediency is what always gets us into trouble.  Does anyone remember the Y2K 
> bug?
>
>
>  --- On Wed, 7/9/08, Jay Nemrow <jnemrow@xxxxxxx> wrote:
>
>  From: Jay Nemrow <jnemrow@xxxxxxx>
>
> Subject: [gopher] Re: Item Type Suggestions
>  To: gopher@xxxxxxxxxxxx
>
> Date: Wednesday, July 9, 2008, 12:28 AM
>
>
>  Although the philosophy of all of this just gets my heart beating faster,
>  Cameron has the perspective of the person actually coding all of this in the
>  real world client!  I would just as soon have the client working smoothly as
>  to force it to obey a nice idea that makes coding a nightmare.  Let the
>  programmer win the day!
>  On Tue, Jul 8, 2008 at 3:25 PM, Cameron Kaiser <spectre@xxxxxxxxxxxx>
>  wrote:
>
>  >
>  > Here's the problem with that, though: the browser thinks in MIME
>  types.
>  > To get the proper MIME type out of a file that could be arbitrarily CSS,
>  > XML *or* HTML, you'd need to resort to content sniffing or extension
>  > grokking, which is what I want to avoid.
>  >
>  > I'm fully in agreement with your first paragraph, but for certain
>  tasks a
>  > 1:1 mapping is going to be unavoidable from an expediency point of view.
>  > At least for this specific case I cannot see a way of avoiding it.
>  >
>  > --
>  > ------------------------------------ personal:
>  > http://www.cameronkaiser.com/ --
>  >  Cameron Kaiser * Floodgap Systems * www.floodgap.com *
>  > ckaiser@xxxxxxxxxxxx
>  > -- The only thing to fear is fearlessness -- R. E. M.
>  > -------------------------
>  >
>  >
>  >
>
>
>
>
>