Deconstructing Frameworks

by moodyharsh 2016-09-01
deconstructing-frameworks #

Deconstructing Frameworks

Economic incentives for framework creators,

  1. Books
  2. Training
  3. Consulting
  4. Vendor Lock-In
  5. A three letter acronym
  6. Plug-Ins / Modules
  7. Stardom, Star Gazers and Followers
  8. Free Support

I think the worst aspect of frameworks is that they thrive on pandering to the competent idiot. The idiot who never realised that a Programming Language is a Platform. The idiot who will also vigorously defend his framework because only incompetent retards use the other framework.

I suppose the only serious question to ask is can all programming be reduced to search, copy, connect with a large enough framework ?

Replace everything with libraries

Backend

Anything built after CGI / FastCGI / Servlet can be thrown down the gutter and be replaced with libraries.

Middlewares like Sinatra, Flask, express are the way to go.

Templates and Web Components

  1. Control: ejs

Fears of not using a framework …

Code Reuse

Code reuse can happen at

  • Primitives
  • Data Structures
  • Algorithms
  • Design Patterns
  • Domain Models

You can encourage code reuse in your organisation with private code repositories.

With scaffold generators like yeoman, you can help solve boilerplate code as well.

Consistency

This is the easiest to solve. Don’t use two libraries at the same time which serve the same purpose.

Enforce a style guide for the code and a selection criteria for libraries.

End Note

The real question to ask is, why should you or your programmers learn and wrestle with a framework’s myopic word-view than solve real problems ?