Comment by j on "What are your thoughts about JSS?"

so let me recap :D because I love it ... "you can write declarative" .... CSS by nature is declarative and maintainable. If you actually understand what you're doing.

But I know that a lot of devs actually don't know what they are doing and create super complex structures coupled with almost everything just to add a new button color :D ....

that's why I'm willing to make this trade-off because I understand that some don't like to think about CSS when they work :) and I don't get upset reading 20times !imporant

to me it's useless overhead :) but if you don't really understand CSS it's a nice tool to decrease the complexity hence the sideffects of CSS ....

I wish this "maintainable" keyword would be true for all of us.

:D me too, i wouldn't be in shock that often.

Yeah, really just trying to get rid of the regular CSS maintenance nightmare … We gain something, we loose something, but we move forward.

@oleg008 yes and it's understandable that some of us are not interested how the language works and abstracts and interacts based on certain settings.

As long as it works everything is okay :) There are basically only one valid point in using JSS because those general things work only under certain assumptions.

Isolation.

and that's good enough to me :) , to me, this quickly escalates to tooling-masturbation, sometimes you only need a "hammer" :) and the more heterogeneous your systems get the more orthoganal tooling is important :) not coupling your CSS with JS or the rendering process :)

I was really curious when i first read about it :) and i was thinking about how awesome it could be :) eliminating dead CSS code creating a clean abstraction, validation and warning and such .... but in the end I was disappointed by the implementation and ofc real world applications who actually have to do a transitional phase shifting technology and not "we start with this".

some of us are not interested how the language works

CSS was not designed for components and large sites. Even it's full understanding doesn't allow you to scale it in team and code size in a robust way. Its global nature with documents in mind works just for relatively small projects. This is not to blame on developers who don't understand how CSS works.

Isolation

I guess by isolation you mean scoping, basically automated unique selectors, right? I will publish an article soon which explains the difference between scoping and isolation. They are very different terms.

not coupling your CSS with JS or the rendering process

CSS and JS are already coupled if you render/manipulate html using JS.

I was disappointed by the implementation and ofc real world applications

I am curious to hear specific problems you stumbled over!

@oleg008 it's a descriptive language :) so the "designed-for" is more about convinience and how you structure things :) you could just go for atomic css and they're are religious wars about that afaik :). It's not about blame it's about structure either you have one or you don't and if you don't develop or don't want to develop one you need tools. JSS is one tool :)

i know the difference but the scoping is the isolation of the component :) namespacing :) or do they really inline CSS based on the common AST with dead code elimination without a semantic context ?

not what I meant ;) i was talking about heterogenous architectures which transition :) jss probably wont work for a PHP part of an old application which means duplicated code which i meant with orthogonal designs :)

But this is not that important to me at all :D it's just my opinion

Search Hashnode