In my repo:
I've added a React version.
If you haven't seen my previous post on Vue read it here: Book Site Vue
This continues my quest for a replacement for Knockout.
I would say this would be more of a learning curve for developer which had a Knockout background. Some concepts are difficult for people without a functional language background. Having delved into the Haskell pool I was able to transition into that mindset. I was able to get things setup with just babel. In a "real" site using node and typescript are probably a must. Getting things up and running took me more than it did with Vue, but that was mostly due to the lack of seperation between markup and code. Once I was able to switch into that mindset, things were smooth sailing. The one directional binding makes sense, but it is yet another learning curve. It is workable once you've adapted to its peanut butter and jelly in the same jar approach.
At first glance it seems wrong to mix markup and script, and it also seems wrong to have inline styling. It is handy to have "everything in one place". Keeping a things flow top down approach and passing callbacks versus binding also seems somewhat cumbersome.
This kind of goes out the window with the React approach.
Recently relicensed under MIT
I like Vue, React is usable, and if I inherited a project with it I would work with it, but I don't like it as much as Vue at the moment.