>"No framework" generally means "poorly-written custom framework" This thinking is part of the problem: the idea that not-using a framework almost necessarily

>"No framework" generally means "poorly-written custom framework" This thinking is part of the problem: the idea that not-using a framework almost necessarily means you're writing garbage. >Do you have any code samples to share from your vanilla JS apps? I can show you bad code from popular frameworks too--in particular, hacks to get around the "magic" that frameworks offer. And, invariably, we move on from the framework because now there's "something better". And, we say "that's just progress". No one wants to admit that the last framework was just bad. It's a trend that's been going on for decades in programming, and not just with JS frameworks. Stick around long enough and you'll see exactly how predictable it is.