"you don't always need to think about the ability to hire additional developers who know your framework of choice"
Unless you are hiring a junior dev who has no experience I think this statement is pretty far fetched. The ramp up time for a new dev on a framework that isn't widely adopted yet will be way higher, plus hiring developers who would even want to work with said framework sounds like a task in itself as well.
If you want to enhance HTML use Vue, if you want to focus on Javascript for everything use React. I like the idea of Svelte coming in to push other frameworks forward, but by no means do I think Svelte will be the future (this may not age well, but at this time my opinion).
For a junior, sure, but I would expect a mid-to-senior developer working on front-end JS for a living to have some experience of at least one of the popular rendering libraries/frameworks and therefore to be able to understand at least the essentials of any of the others after a few hours of training. They're relatively simple interfaces, and many of the same concepts come up in most or all of them. Of course it will take a bit longer to understand the edge cases, any unusual or unique aspects, and any common traps to avoid, but you don't need all of that to be productive with everyday front-end development work. Presumably anyone new and/or below senior level is going to be supervised/mentored while they're getting up to speed and have their code reviewed anyway.
Finding all the intricacies and gotchya's of a new framework does not happen in a couple of weeks. Also, a total workflow change is not adapted to in a couple of weeks.
That's sort of the beauty of Svelte. The surface area is minimal, and as such - though there are gotchas, you can almost count them on one hand.
I learned to use Svelte (granted, v1), in 45 minutes, and build something using it. I guarantee that a developer won't need 2 weeks to become comfortable in it.
Training doesn't happen in a vacuum. Intricacies and gotchas should be known and hopefully documented by the existing team which can help ramp a new developer up quickly
I read that as an addendum to "Not everything needs to be thought of as a business use case". Which is to say: if you're working on something for fun, just choose the stack you'll enjoy the most.
I was writing Svelte code after an udemy class having done Vue prior to that. They aren't that different. anyone who can write react or vue code could be writing svelte code in a week.
The people that run the voice program at Mozilla seem to be very disconnected from the rest of Mozilla. They are essentially an "innovation team" that jump from project to project across the company acting as almost an agency inside Mozilla. Seems this model has really made projects like this suffer because there isn't a team always there to iterate on the project and make it better.
"you don't always need to think about the ability to hire additional developers who know your framework of choice"
Unless you are hiring a junior dev who has no experience I think this statement is pretty far fetched. The ramp up time for a new dev on a framework that isn't widely adopted yet will be way higher, plus hiring developers who would even want to work with said framework sounds like a task in itself as well.
If you want to enhance HTML use Vue, if you want to focus on Javascript for everything use React. I like the idea of Svelte coming in to push other frameworks forward, but by no means do I think Svelte will be the future (this may not age well, but at this time my opinion).