[sldev] So what's in the "80%" part of the API?

Argent Stonecutter secret.argent at gmail.com
Tue Feb 27 16:51:52 PST 2007

> It might be beneficial to define a set of goals and determine a
> cost-benefit for them, and then go back and reassess the goals. A goal
> of making an interface where plugin developers never have to update
> their code is not going to be reasonable. A goal of having plugin
> developers only have to update their code every month or so might be
> attainable in some circumstances, but how much work would it take to
> maintain an interface like that, versus the amount of work it would  
> take
> for plugin developers to keep their code up to date?

Depends on how much you can automate the interface, and how well the  
interface is designed.

One goal could be an 80:20 API that tries to handle the things 80% of  
the plugins need, and the other 20% of the developers have to update  
on every release. Anyone talking to raw packets is probably in the  
20%, but someone who's just mapping "USB Consumer Control AC Home" to  
requesting your home location displayed on the world map might be  
able to go a year without having to change anything.

More information about the SLDev mailing list