Software Framework

Inversion of Control

Framework has slots for your code

Application-level coding, library-level coding, and framework-level coding are completely different in terms of skills and style.

abstractions should provide escape hatches to work around restrictions for minimizing frustration

Software Framework Types

Low Level Framework

High level Framework

No Code

AI doesn't care about shared logic, extensibility, or inheritability of components. it just implements what it needs. Frameworks may become obsolete in the future.

Will we care about frameworks in the future?

I've been building lots of apps by using LLMs and Agents. I'm currently up to about 17 tools, utilities and demos over the duration of a couple of weeks. I build them for me and because tools like Replit have enabled me during my small spots of free time to build fully working sites and apps that solve the immediate problem that I have. I've felt incredibly productive. I've a hypothesis that something like these Agents will be how we build software in the future, so as I build these apps I try to never adjust the output, I want to see how far that I can get with the machine creating all the code and so see how far away we are from this future.

https://paul.kinlan.me/will-we-care-about-frameworks-in-the-future/

The cost of convenience — surma.dev

It is tempting to build abstractions so developers have to do less and build more. However, this can easily end up causing frustrations with developers if not done right.

https://surma.dev/things/cost-of-convenience/

Software Framework

Inversion of Control

Recommendations