search

frameworkless-movement / manifesto

The Frameworkless Movement Manifesto
Creative Commons Attribution Share Alike 4.0 International
820 stars 23 forks source link

When do guidelines for a frameworkless approach become a framework? #9

Closed tlaak closed 6 years ago

tlaak commented 6 years ago

When you start forming guidelines and practical approaches for a frameworkless application, aren't you actually creating a framework?

What's the definition of a framework and when does a set of guidelines become a framework?

sensorario commented 6 years ago

I think, ... reinvent just wheels you need to reinvent. Reuse just wheels that are too old to create value today.

francesco-strazzullo commented 6 years ago

IMHO one of the prerequisites to work effectively with frameworkless code is to apply the YAGNI principle. My point is that you should just write code that solves that particular customer’s problem at that particular moment.

If you stick to YAGNI your guidelines are not a framework, just a solution to very specific problems. The problem with this approach is that a team should fight the urge to propagate your shiny new architecture to other projects, or to other parts of the application that don't need it.

I suggest reading these two articles from Matteo Vaccari's blog about working without frameworks.

  1. Part I
  2. Part II
francesco-strazzullo commented 6 years ago

@lorenzomassacci @Violo @adellava what do you think? We should try to add something about "not creating a new framework?"

lorenzomassacci commented 6 years ago

I tried to explain my opinion on this issue: https://github.com/frameworkless-movement/manifesto/issues/6 (What Frameworkless is not?)

I think it could be useful add this clarification in the README. In the next few days, I’ll propose a PR

francesco-strazzullo commented 6 years ago

@tlaak we add some information about this topic with the PR #12. If you think that it's not enough just open another issue.