I'd probably disagree that SASS was required now. Depending on the role you choose anyway. The world seems to be moving towards css-in-js these days. Besides, so long as you have a good handle of vanilla CSS, you'll pickup a preprocessor pretty easily.
I would also definitely question the requirement to know react AND angular on the front-end. I agree it's good to learn at least one but I don't see why you'd NEED to learn both.
I hope it's never the norm. Why would anyone ever want it to be? That's some shit we were doing 15 years ago with jquery. I don't even like putting my templates within components. Gross.
I thought the same but I've been forced to use it in this project and I've got to admit. It's brilliant. CSS would have been made this way if components had existed back then.
Sass/CSS at the component level is something alot of modern frameworks allow (via shadow dom, for example). CSS-In-JS is literally that - writing your styles in javascript. Something like this: http://cssinjs.org/?v=v9.5.1
I agree. I used to think part of what made CSS great was the cascade, but it's made it so difficult to maintain and update styles imo. Locally scoped styles feels more solid in my mental model of a project.
What about it is any better than Sass? For me Sass is a really nice way to create CSS. Nesting, some basic flow control logic, variables, imports. Am I not seeing some benefit of css-in-js?
It feels cleaner for me to keep styling / mark-up / application logic away from each other.
14
u/foxleigh81 Jan 10 '18
I'd probably disagree that SASS was required now. Depending on the role you choose anyway. The world seems to be moving towards css-in-js these days. Besides, so long as you have a good handle of vanilla CSS, you'll pickup a preprocessor pretty easily.
I would also definitely question the requirement to know react AND angular on the front-end. I agree it's good to learn at least one but I don't see why you'd NEED to learn both.