Why do I need to use a popular framework?

by

Frameworks have several advantages:

  • You don’t have to write everything. In your case, this is less of a help because you have your own framework which you have accumulated over the years.

  • Frameworks provide standardized and tested ways of doing things. The more users there are of a given framework, the more edge cases that have been encountered and coded for. Your own code may, or may not, be battle hardened in the same way.

  • Others can be recruited onto a project with a standard framework and have access to the documentation, examples and experience with that framework. Your own snippets may or may not be fully documented or have examples of use… but isn’t much chance that others are comfortable with them initially.

EDIT:

With regards to your idea of packaging up your own framework, the benefit of cleaning it up for public consumption can be larger than the benefit of getting others to use it.

The reason is simple: you will have to re-evaluate your assumptions about each component, how they fit together and how clear each piece is to understand. Once you publish your framework, your success will be strongly dependent on how easy it is to get up and running with.

Big wins with little effort are essential for adoption (those wins will encourage people to delve further into the framework). Ruby on Rails in an example of a framework that gives such big wins with little effort, and then has hidden layers of features that would have overwhelmed someone just getting started. (The question of the quality of RoR apps is not the point, the point is about adoption speed).

After people adopt a framework, it is about the ease of continued use. Little details like consistent parameter use patterns make all the difference here. If one class has many parameters on every method, while another has setters that are expected to be called before invoking methods, you will lose users because they can’t get a “feel” for what is expected in a given case without resorting to the documents.

If both ease-of-adoption and ease-of-living-with issues are addressed properly, you only have to get lucky for people to adopt your framework. If those issues are not addressed properly, even an initial interest in the framework will wane quickly. The reason is that there are many frameworks: you will need to stand out to gain the advantages of having others using your kit (as they rightfully are as wary of your framework as you are of others).

More Related Contents:

  1. What are these exactly?: Composer, Git and Pyrus [closed]
  2. Laravel blank white screen
  3. CodeIgniter PHP Framework – Need to get query string
  4. Why use a framework with PHP? [closed]
  5. If Singletons are bad then why is a Service Container good?
  6. Laravel 4 removing public from URL
  7. Enabling $_GET in codeigniter
  8. Registry design pattern…good or bad?
  9. URL Redirect / URL Masking [closed]
  10. How to run deprecated php codes on the latest XAMPP [duplicate]
  11. Get the full URL in PHP
  12. Replace the Variable Price range by the chosen variation price in WooCommerce 3
  13. Is there a PHP Sandbox, something like JSFiddle is to JS? [closed]
  14. mysqli ignoring the first row in a table
  15. PHP Create and Save a txt file to root directory
  16. Artisan migrate could not find driver
  17. How to check if $_GET is empty?
  18. another twitter oAuth cURL access token request that fails
  19. Absolute vs. relative paths
  20. How is testing the registry pattern or singleton hard in PHP?
  21. PHP object like array
  22. What causes: “Notice: Uninitialized string offset” to appear? [closed]
  23. Custom key-sort a flat associative based on another array
  24. How to use events in yii2?
  25. Detecting file upload size on the client side?
  26. Validate Email in php [duplicate]
  27. Convert PostgreSQL array to PHP array
  28. saving checkbox state on reload
  29. Update Command-line Output, i.e. for Progress
  30. Laravel Eloquent update just if changes have been made

Leave a Comment