In general I agree that all that JSS mess is something invented by someone too lazy (to put it mildly) to learn how CSS works (just like hooks – too lazy to figure out "this" and classes in JS), but if you read the docs a bit closer, you'd find that plain CSS works just as well https://material-ui.com/guides/interoperability/.
10 years of Front end Development. I quit
11–20 of 50 posts
Re: 10 years of Front end Development. I quit
#12[deleted]
Re: 10 years of Front end Development. I quit
#13In general I agree that all that JSS mess is something invented by someone too lazy (to put it mildly) to learn how CSS works (just like hooks – too lazy to figure out "this" and classes in JS), but if you read the docs a bit closer, you'd find that plain CSS works just as well https://material-ui.com/guides/interoperability/ .
> just like hooks – too lazy to figure out "this" and classes in JS
That's just a part of why hooks exist: https://reactjs.org/docs/hooks-intro.html#motivation
The more important parts have to do with code reusability and complexity.
And the way classes work in React is not typical and there _are_ non-standard behaviors to them, so to brush that additional complexity aside is myopic.
Re: 10 years of Front end Development. I quit
#14The Material UI library for React is such a piece of garbage and I actually believe it’s one of the main reasons why so many devs hate React. You can use React without and your happy will be so much happier!!
Re: 10 years of Front end Development. I quit
#15I'm a casual so don't take this post as authoritative or anything, but I feel like people are forced to use frameworks to do anything more complex than a static website meant for desktop only. For example, to make a fully responsive website that adapts from desktop to mobile and vice versa and can dynamically create forms and stuff, there's no one place to go and see a SUPER OFFICIAL STANDARD OF HTMl/CSS way to do it. There are some official resources like w3school and mozilla, but they're only good for really simple things. You find a bunch of scattered guides around the web, none of them really explaining the choices in their settings very well or at all. So as a beginner, I feel like I am just throwing shit at a wall and hoping something sticks and works, until I find some other setting from a different guide to do some other thing that breaks the first feature. With modern frameworks, you can achieve some structure and order, because someone else did all the boilerplate and groundwork so that you can just make a damned website like you wanted to do instead of floundering around from tutorial to tutorial.
Re: 10 years of Front end Development. I quit
#16In general I agree that all that JSS mess is something invented by someone too lazy (to put it mildly) to learn how CSS works (just like hooks – too lazy to figure out "this" and classes in JS), but if you read the docs a bit closer, you'd find that plain CSS works just as well https://material-ui.com/guides/interoperability/ .
> just like hooks – too lazy to figure out "this" and classes in JS That's just a part of why hooks exist: https://reactjs.org/docs/hooks-intro.html#motivation The more important parts have to do with code reusability and complexity. And the way classes work in React is not typical and there _are_ non-standard behaviors to them, so to brush that additional complexity aside is myopic.
Oh, did I? But as far as I remember, not having to figure out classes was one of the official reasons why hooks came to be, which was clearly stated in the corresponding blog post, I think.
Re: 10 years of Front end Development. I quit
#17Earlier quoted context omitted.
> just like hooks – too lazy to figure out "this" and classes in JS That's just a part of why hooks exist: https://reactjs.org/docs/hooks-intro.html#motivation The more important parts have to do with code reusability and complexity. And the way classes work in React is not typical and there _are_ non-standard behaviors to them, so to brush that additional complexity aside is myopic.
Oh, did I? But as far as I remember, not having to figure out classes was one of the official reasons why hooks came to be, which was clearly stated in the corresponding blog post, I think.
Oops, the original comment I was replying to is gone... I didn't notice before that people here seem to like to comment and then delete it a minute later.
Re: 10 years of Front end Development. I quit
#18Man, chill out. Don't let the burnout or a few bad days cloud your judgement. A lot of new tooling is shit. It was always like this. It's like someone judging FE dev by all the jQuery monstrosities in 2010 or by Angular 1.x in 2013.
Choose good tools, but most importantly, good projects. They're out there.
Re: 10 years of Front end Development. I quit
#19You’re not wrong. I just quit the industry as well; the multiple levels of webpacked transpiled bullshit, react modules for spacer divs and “type safe CSS” really got me down. Between ass backwards code, renting mainframes from Amazon, and surveillance capitalism I realized that everything I loved about commercial web engineering has gone to shit. I have no idea what my next move is but right now I don’t really care.
Go work on embedded stuff. There are lots of jobs where you work primarily with electrical engineers. It is pretty much the opposite of front end work.
Embedded work has its good points, but it has its downsides. I wouldn’t advise anyone to change because they expected the tooling or libraries to be better designed, or if they imagined that working with electronics means dealing with less bugs or that they might be working with more skilled people!
I have relevant background to say this, although my embedded work is very rusty. I have an EE degree and a small amount of experience with electronics. I’ve been doing web front end for over a decade which was mostly 100% JavaScript SPA dev work (recently quit because browsers are hell: I did like the money and some of the challenges!).
Re: 10 years of Front end Development. I quit
#20One time I had to use Ember as the front end and drupal API as the backend. Seriously, what a mess. But I was getting paid...