4 ms·
It's also why I chose Vue over React. In terms of capabilities they are fairly similar but the the existence of an official router and official state managemen
by noir_lord 8y ago
It's also why I chose Vue over React.
In terms of capabilities they are fairly similar but the the existence of an official router and official state management store means that the "things that can break in horrible ways" surface is reduced.
I stuck with KnockoutJS for a long time because they had (for a JavaScript project) incredible backwards compatibility and stability.
I've been programming long enough that "the new hotness" is of much lower interest than "what capability does it give me I don't have and will I still be able to build/deploy this in 3 years if I need to".
Also if something seems amazing I'll wait a year, if it was amazing it'll still be amazing in a year and I'll have 365 days of other people smacking their heads on the not amazing parts.
- projectramo 8y agoThe knockout documentation is a thing of beauty. One should start with the framework for that reason alone.
- Kiro 8y agoWhat's the official state management?
- lhorie 8y agovuex