Frontend frameworks are a positive sum game! Svelte has no monopoly on the compiler paradigm either. Just like I think React is worth learning for the mental model it imparts, where UI is a (pure) function of state, I think the frontend framework-as-compiler paradigm is worth understanding. We're going to see a lot more of it because the tradeoffs are fantastic, to where it'll be a boring talking point before we know it.

Final Form makes the assumption that your validation functions are "pure" or "idempotent", i.e. will always return the same result when given the same values.

Final Form makes the assumption that your validation functions are "pure" or "idempotent", i.e. will always return the same result when given the same values. This is why it doesn't run the synchronous validation again (just to double check) before allowing the submission: because it's already stored the results of the last time it ran it.

If your React component’s render function is “pure” (in other words, it renders the same result given the same props and state)

Pony pureness, really? While polyfills are naughty, ponyfills are pure, just like ponies.

Polyfills are naughty as they patch native APIs, while ponyfills are pure and don't affect the environment.

With a RIMS, librarians don’t just manage a collection of primary sources; they develop reports and metrics by curating metadata from all departments, making the library not only the go-to spot for information on campus, but also the go-to spot for information about the campus.  

mixhumanmotives,nottopurifythem

purecareer