The Lifecycle of Every Web Framework Ever
Everything that can happen, has happened, and will happen again.
Every web framework has the same story. It all starts with a burning desire for simplicity and descends slowly into madness. Your job is to spot the warning signs and end the cycle.
Stage 1
Developing web applications is so hard. Surely there needs to be a better way of doing this. We should just standardise these reoccurring development patterns into a simple new framework.
Step 2
We’ve just released version 1 of this web development framework. We hope it makes life much easier for you and rapidly increases your productivity by giving you all these features out of the box!
Step 3
We’ve been overwhelmed by the response to version 1 of the framework and we are so excited to see so many of you using it in your everyday work. However we have noticed that some of you have had to implement some difficult workarounds to deal with certain edge cases that you have faced. So we are pleased to announce that version 2 of the framework makes all those things much easier.
Step 4
The exponential growth in the popularity of the framework has been phenomenal since the release of version 2. As the framework has grown we have considered the architecture carefully have come to the realisation that the framework must evolve to meet the needs of our growing user base. As such we have implemented significant architectural changes to version 3 of the framework. These changes may introduce some new complexity to your applications, and create a steep learning curve for any newcomers to the framework, but they will provide you with significantly more power and control over your applications while also boosting performance by some percentage you probably don’t care about. These changes are supposed to be backwards compatible but most likely will require some refactoring of your exisiting applications and cause them to break the moment you upgrade them. However, we believe the trade off will be worth it!
Step 5
Developing web applications is so hard. Surely there needs to be a better way of doing this…
