bigtanner1337

@throwaway26342 I agree, to an extent. A mid to senior level JS developer should be able to pick up React fairly quickly. A junior developer will struggle, no matter which framework/library is used.

@CharlesW I guess there's a reason why people short hand "On the Origin of Species by Means of Natural Selection, or the Preservation of Favoured Races in the Struggle for Life" to "the one about evolution" :) Sorta captures the essence without the bells and whistles.

Agreed, for those of us on Windows, the assumption that Node/NPM folks make that we'll have Python installed on our machines by default is not very nice.

Hooks, I agree, those take a while to get used to. Once you do though, the code is so much cleaner than doing it based off of the lifecycle. And yeah, functional components make calling .render() unnecessary, the component _is_ the function.

React would be in contention if I too was working on a server-side rendered (Isomorphic) app. There would be others in the running too. Though for a purely user-browser driven UI, I still think React is far and away better than the alternatives, at least for right now.

@PaulHoule, interesting, what other limitations on Vue did you run up against?

Comparing Vue to React, the # of downloads React has is almost off the charts. Hard to justify using Vue in 2022, almost 2023. Very few use cases Vue is better at than React.

A 45-minute dive into some of the top security mistakes made while developing custom applications—and what software developers can do to avoid them. Recorded at a Keyhole Software education event featuring Senior Consultant Zach Gardner in August 2022.