[goto11]

> Yeah. Every couple years people who write JS come up with new garbage frameworks that don't really move the needle forward.

I presume this is in contrast to the Haskell community where there is a single perfect web framework which solves all problems for everyone?

[crimsonalucard]

Yeah your presumption is absolutely correct. I love seeing you use loaded presumptions to try to communicate with me.

I presume that after I say this to you you’re going to stop communicating with me because shoving random presumptions up someone’s mouth isn’t a polite and civil way to communicate. Prove me wrong.

[goto11]

Fair enough. But you have are some fairly strong (bordering on inflammatory) criticism of JS frameworks and the people developing them - but without any specifics which would allow one to counter you (or agree with you for that matter).

It just "garbage" and "mistakes" and "people who don't learn" - how do anyone argue against that?

[crimsonalucard]

You can argue against the generalization if it’s wrong. If it’s not wrong your best bet is to stand by why the framework is good despite the correctness of the generalization.

It’s a cheap but affective method to use details to attack generalizations. However the insidious thing about generalizations is that details can be dismissed as noise irrelevant to the main point. A real argument against a generalization is another generalization, with supporting evidence.