May 31st, 2017
I’m more concerned about HTML-in-JS than I am about CSS-in-JS.
As in jsx? Or something other?
Have you tried Vue.js’s server side rendering? I’ve fallen in love with it hah.
The whole stack needs to go.
I am worried about them both equally.
After #10kapart I’ve found myself doing so much more in an HTML stage before starting with CSS+JS. And I specialise in v interactive things!
And later, A-Frame in JS!
I am using Twitter client that probably used both of those approaches and I am very satisfied!
The end result is HTML anyways and same accessibility principles apply
Once React (and JSX) gets rid of those unecessarily nested divs there’s really nothing to be concerned about. Really.
Then you have my blessing, my son. To rephrase: I am more concerned about client-rendered HTML-in-JS than CSS-in-JSS.
Gotcha. Yeah, I totally agree there 😁
Assuming you’re talking about server-rendered, then sure. But what concerns me is client-rendered HTML-in-JS regardless of which framework.
I’ve been a semantic markup defender for years. Worked with React daily for 2 years now and the only real “problem” I see is the div soup.
I don’t understand, how does react lead to nested divs? It specifically prevents that by not attaching a dom per component. plsthx
I read the chapter you pointed to (thx!); are you saying client rendered apps are problematic in general?
That’s not very “progressive” is it? :P (jk)
I’m a lot more concerned about js-in-html 😁
I’m always concerned about HTML haha