but IMO it should be the other way around -- learning the core of the tools from experiments in vanilla web, then when projects get big enough or when joining a

but IMO it should be the other way around -- learning the core of the tools from experiments in vanilla web, then when projects get big enough or when joining a team of developers go to the frameworks to help manage the multiple moving parts and concurrent merges. Sure, components can help with that without having to lean on a framework, but a framework can help align the opinions of the frontend design.