You're replying to a comment by Mr.Key.

Mr.Key Permalink
March 11, 2016, 05:53

I think it is better to use a framework, but to choose a solid one. My thoughts are that projects which choose a framework based on the level of hype, are itself pretending to become a hype. Culture match.

Maybe it's like a person is an average of 5 people he or she connects regularly; a project is an average of technologies it uses. Solid, matured framework choice probably means solid project. For projects whose authors hunt for customer hype, it is obvious to choose everything related with hype. Ascetic projects tend to chose lean dependency stack. Project bloated with all possible technology stack could mean the result is hard to maintain despite many very clever things in it. It's a diverse world.

Otherwise, your arguments are correct and the points are valuable for making decisions. Decision to avoid everything is just one of possible decisions, however.

Reply To This Comment

(why do I need your e-mail?)

(Your twitter handle, if you have one.)

Type the word "floppy_508": (just to make sure you're a human)

Please preview the comment before submitting to make sure it's OK.