Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask

Re: Re^3: RFC: New rootlevel CPAN namespace: XHTML (mean)

by elusion (Curate)
on May 08, 2003 at 19:46 UTC ( #256652=note: print w/replies, xml ) Need Help??

in reply to Re^3: RFC: New rootlevel CPAN namespace: XHTML (mean)
in thread RFC: New rootlevel CPAN namespace: XHTML

If you take over a CPAN module that needs help, do you redesign the interface if it needs it? Breaking the interface is considered bad, I think... but sometimes it's too broken to keep.

elusion :

  • Comment on Re: Re^3: RFC: New rootlevel CPAN namespace: XHTML (mean)

Replies are listed 'Best First'.
(jeffa) 5Re: RFC: New rootlevel CPAN namespace: XHTML (mean)
by jeffa (Bishop) on May 09, 2003 at 17:59 UTC
    I was waiting for someone with more experience in this matter to answer your question ... but since no one has i will share my opinion. Breaking an interface is considered bad, unless no one was using it in the first place. At the very least, instead of simply yanking out API calls and replacing them with new ones, you should instead keep the old calls and 'deprecate' them. By this you could emmit a warning when an old API call is called, telling the module coder to instead use the new API call. Then, after some time has passed, you might get away with yanking out those old API calls.

    The idea is to first give some an indication that certain methods are going to go away -- just don't make the users have to make a trip to the local planning office cellar and have to search by torchlight for a locked filing cabinet stuck in a disused lavatory with a sign on the door saying "Beware of the Leopard" to find out that their favorite API call is being demolished to make way for a new bypass. :D


    (the triplet paradiddle with high-hat)

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://256652]
[Corion]: Meh. I think I have now the parts down that I want from a simple Javascript frontend for single-page- applications with a aPerl backend. But it seems that all Javascript templating modules either don't support two-way binding (which would be nice) or ...
[Corion]: ... don't support server-side precompilation (which means the client has to compile all templates to Javascript themselves), or are giant frameworks that expect to do everything (which is not what I want)
[Corion]: I feel that there is a talk somewhere in there, either about the structure and parts, or how I used several parts to get a complete whole.
[Corion]: Maybe I can still find something that is compatible with handlebars.js (which has JS precompilation) but allows for two-way data binding (which is great for the UI)

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (5)
As of 2017-03-30 07:47 GMT
Find Nodes?
    Voting Booth?
    Should Pluto Get Its Planethood Back?

    Results (355 votes). Check out past polls.