One of the biggest cons I find are cold-starts. Meaning that there is some time required for any cloud provider to provision resources for your function and get it running. The more it is accessed, the less of a problem this is, but for a lot of people, half-a-second response times don't cut it.

Hey I forgot to paste something in when I did the article. I fixed it. Here is the update: { "compilerOptions": { "baseUrl": "src" }, "include": ["src"] }

Also know how react decides to re-render or not. So things like Javascript's objectref and memoization are important to understand.

instead of 5 different states, just use setDynamicClasses directly in the onChange events and get rid of the useEffect. This also fixes a bug where you could have 2 true classes, and have weird behavior. function App() { const [dynamicClasses, setDynamicClasses] = useState("roboto"); return ( <div className="App"> <h1>Change Font Style</h1> <button onClick={()=>setDynamicClasses("roboto")}>Robot</button> <button onClick={()=>setDynamicClasses("dela"))}>Dela Gothic One</button> <button onClick={() => setDynamicClasses("dancing")}>Dancing Script</button> <button onClick={() => setDynamicClasses("tegomin")}>New Tegomin</button> <p className={dynamicClasses}>Lorem ipsum dolor sit amet consectetur adipisicing elit. Soluta, quam!</p> </div> ); }

Just a few things: arrays need commas between values, not semi-colons. The reduce function might be more clear with an initial value, and maybe another example. That one can be hard for people. I did learn how to use map on a string though! That was something new for me. Thanks!

The biggest hurdle is the support from the React community. It is huge and generally adopted by enterprises. Vue may be great, but this is the real issue. It isn't good enough to topple React (yet) like React was to angular 1.x.

Marie-Elise Please do!

I've seen a bit by the guy. Not sure I need to read the whole book to get the idea, but if you think it is a worthy read, I might pick it up.