Show HN: ReactCSS – Inline Styles with Support for React, Redux and React Native
1–10 of 48 posts
Re: Show HN: ReactCSS – Inline Styles with Support for React, Redux and React Native
#2Nice project!
We have a project like that one of our developers wrote except it will compile the classes back to a CSS stylesheet for you for performance and will unify identical styles to not have duplicates and save space https://github.com/Mosho1/react-style
Re: Show HN: ReactCSS – Inline Styles with Support for React, Redux and React Native
#3What happened to the separation of concerns between CSS and JS? In my experience most developers dont want anything to do with CSS. They want a designer who can code to do that.
Re: Show HN: ReactCSS – Inline Styles with Support for React, Redux and React Native
#4What happened to the separation of concerns between CSS and JS? In my experience most developers dont want anything to do with CSS. They want a designer who can code to do that.
It's just a slightly different syntax for CSS but still is CSS.
Re: Show HN: ReactCSS – Inline Styles with Support for React, Redux and React Native
#5Nice project! We have a project like that one of our developers wrote except it will compile the classes back to a CSS stylesheet for you for performance and will unify identical styles to not have duplicates and save space https://github.com/Mosho1/react-style
So it translates everything back to CSS, is that how it handles hover and pseudo classes?
Re: Show HN: ReactCSS – Inline Styles with Support for React, Redux and React Native
#6What happened to the separation of concerns between CSS and JS? In my experience most developers dont want anything to do with CSS. They want a designer who can code to do that.
The component paradigm that react is built around is all about working with very small objects, where everything you need for that component is in one file. It's a fantastic model when you are working with a complex interface that has many components to it. It's a paradigm that needs to be managed and used carefully though, otherwise you'll end up with massive 2000 line files.
I never thought there was a separation between JS and CSS, that sounds a little outdated, to be honest. As a front-end developer, I would be expected to do JS and CSS.
Re: Show HN: ReactCSS – Inline Styles with Support for React, Redux and React Native
#7What happened to the separation of concerns between CSS and JS? In my experience most developers dont want anything to do with CSS. They want a designer who can code to do that.
The React ecosystem seems to be geared towards masking HTML/DOM/CSS behind Javascript/code, such as when developing mobile apps. I do not think "separation of concerns" is a priority.
(Not agreeing with this BTW, but there is a subset of developers who seem to think this is just great.)
Re: Show HN: ReactCSS – Inline Styles with Support for React, Redux and React Native
#8What happened to the separation of concerns between CSS and JS? In my experience most developers dont want anything to do with CSS. They want a designer who can code to do that.
That bridge has already been crossed when they put the HTML into the JS. Any designer changing CSS is going to want access to the HTML, so they're already mucking in the JS anyways.
Re: Show HN: ReactCSS – Inline Styles with Support for React, Redux and React Native
#9Nice project! We have a project like that one of our developers wrote except it will compile the classes back to a CSS stylesheet for you for performance and will unify identical styles to not have duplicates and save space https://github.com/Mosho1/react-style
So it translates everything back to CSS, is that how it handles hover and pseudo classes?
Yes, exactly - it also produces smaller file sizes and in our experience it's faster.
It's also nice to be able to use classes and integrate with CSS seamlessly when you need to.
Re: Show HN: ReactCSS – Inline Styles with Support for React, Redux and React Native
#10What happened to the separation of concerns between CSS and JS? In my experience most developers dont want anything to do with CSS. They want a designer who can code to do that.
IMO it makes it easier for devs that dislike CSS to make sweeping changes due to all of the relevant styles being in one place.