Library, Framework, SDK. Vs or &?

The planet's population today is nearing eight billions. Almost three-fifths are active internet users. If they want to find something, 90 percent go for Google. The more answers they get the more billions dollars come to the company's pocket (it was 135 last year). 

To show that not only profit but also public good are the issue, Google is investing in an online education of its users. That's why Sideways Dictionary was created in 2017. The guide is using analogies instead of definitions to explain IT terms.

Bots are like ghosts in Pac-Man, API is similar to wooden toy with shapes and bug is the same thing as fly in a drink. The very first phrases came from the pen of journalist Nick Asbury, next ones can be add by anyone else. The platform is open to public. Metaphors for Library, Framework and Software Development Kit are still missing. It's time to fix it.

 

Foto: Sylvia Yang/Unsplash

LIBRARY

Is like baking bread in own kitchen. You can have a yeast from your roommate, buy a flour in the shop and find the form in kitchen supplies. 

FRAMEWORK

Is like bread baking workshop. You have to follow precise recipe, use specific kind of flour and work with available tools. One loaf will be same as the other. 

SDK 

Is like a kitchen where the bread is baking in. There are ingredients, oven and tools to work with. Even a cookbook to read. How to use all of this is up to you. One can be creative or follow exact instructions. 

CONCLUSION

You take things from library (function, methods, classes/ingredients) which you need for work (to create own application/bake a bread) Framework asks you for things (concrete piece of code/specific kind of flour) needed for exact rules to be followed. In SDK there is all of this mixed (libraries, frameworks and other tools/ingredients, oven, recipes) and it's up to you what you create with them.