loading...

re: The Cost of Investing Too Heavily in a JavaScript Framework VIEW POST

FULL DISCUSSION
 

I appreciate your article and I need to add a bit of color to your commentary about material-components-web. I’m actually the maintainer of RMWC rmwc.io , the community framework that google mentioned in their goodbye post.

Making the assessment that mdc-react was abandoned because frameworks are bad is an incorrect hypothesis, although I understand how one could draw that conclusion. The truth is, Google is the biggest smallest company out there. They still have internal politics, teams that shift, and they’re notorious for killing things off at random. mdc-reacts plug was pulled for a variety of reasons, but most of them were non-technical in nature.

Web components is a framework, like it or not. Write enough custom vanilla JS and you’ll likely have created a framework of your own. They will definitely come and go, but I doubt the web component that was written 5 years ago will need any less refactoring than your React or angular app.

In my quest to become the most infinitely pragmatic dev, I’ll tell everyone: write code using whatever tools you need to solve your problems that you and your colleagues can agree on. Good code is code regardless of what framework you use. Also, I’ve been around long enough to know that in 5 years, some new guy or girl will be cursing your name no matter what “bulletproof” tech you choose today :). Happy coding everyone, keep solving the problems 🚀

Code of Conduct Report abuse