I'm glad to see this post, and I'm glad front-end developers are starting to rebel against the nuttiness of what has happened in their corner of the web. I dec

I'm glad to see this post, and I'm glad front-end developers are starting to rebel against the nuttiness of what has happened in their corner of the web. I declared myself out a while ago. It took some digging in of the heels and a bit of a short term career hit, but I no longer do much web development. I do data work, I guess they call it "data engineering" now, lots of pipeline stuff. My background was in math and operations research, and I do calculation as well as data pipelines, so it works out nicely. I really had to start refusing to do javascript, though. I'd still do full stack (which means I handle simple frontend stuff but pass it onto someone more talented if it needs to be more elaborate) if we used Rails or something like it. That, I don't mind, and if I had to do it all myself due to it being a personal project, I'd happily keep things relatively simple in rails. If I needed something more specialized for data analysis, I'd probably write it as a service in python. Til then, I love that ostensibly Polish expression "Not my circus, not my monkey". Front end developers are going through framework churn unseen since the MVC days of 2005. You do what you do, folks, have at it, knock yourselves out. One thing, though - no, I'm not going to start writing data analysis code in Javascript so we can keep things consistent with the front end.