materialdesignweb VS coffeescript

I wanted something that didn't require recompilation and allows me to extend built components. Like an Chip extends a Button. I needed something that allows modification of its HTML template and layering of CSS styles on top of an extended element's styles. Frameworks are pretty rigid in this regard and I wanted to write less code to make a smaller final deployment, instead of copy pasting or having to write complicated mixins and abstractions.

My phone is basically grayscale expect for really minor blue hue. I'm not sure why, and I know how the Material You theming works (built a framework around it).

For the curious: Test page - Source Code

Source: https://github.com/clshortfuse/materialdesignweb/tree/archive-md2/components

If you're tired of it, I've been maintaining my MD framework for more than 4 and a half years since 2018. And before that I was working with Google on the AngularJS implementation in 2015. So I've been looking at and working on the same styles for over 7 years.

Here is the JS for one of the components. Only Chrome natively understands it right now. The alternative is to use a element referencing the CSS, but will call FOUC on the first fetch.

Code

That said, there are ways to embrace the JS ecosystem without actually using JavaScript. Many popular languages have transpilers that will convert code written in that particular language into something that will run natively in a web browser (in other words, JavaScript). Even TypeScript is a language that gets transpiled into JavaScript, so it's not that outrageous of a concept, it just gets more difficult to do the further you get away from languages that don't already look like JavaScript.

As a front-end web developer, do you still use CoffeeScript or jQuery? Unlikely, as TypeScript, ES/TC39 and Babel (and the retirement of Internet Explorer thanks to @codepo8 and his EDGE team) have helped to transform JavaScript into some kind of a modern programming language.

CoffeeScript

On the other hand, companies choose React because that's where all the developers are. If you want to build something that can be maintained years from now, you better not choose the next hype train that goes straight to nowhere (remember CoffeeScript ?). You want something battle tested that has stood the test of time, where you won't have trouble finding developers to scale once you need to. And nobody ever got fired for choosing React.