CSS in JavaScript is like replacing a broken screwdriver with your favorite hammer
zendev.com
zendev.com
In fact the seperation causes so much mental overhead, that we need interactive browser dev tools just to be able to find what styles are applied to what element. So ultimately the idea of putting everything in one spot, per component, is actually pretty reasonable.
the reason the screwdriver was broken is because we're trying to use it as a hammer. So replacing it with an actual hammer makes sense. And the thing is, we still have a fully functional screwdriver at our disposal (for global styles, e.g.).
I've considered JS taking over CSS more and more thoroughly inevitable for about four years now. The pressures on CSS are just too intense for non-Turing completeness to be anything but a leftover remnant of the dream of the "Semantic" web, doomed to fade the same way [2]. People want what only hooking a programming language up to the layout engine is going to give them. You can see it in CSS itself, as it grows ever more "declarative" styles that involve introspecting into the elements themselves, at their content, at their position in the tree, at their siblings.... CSS has long since let the camel into the tent.
(In fact per my earlier comment today, https://news.ycombinator.com/item?id=15218359 , I would consider even CSS-in-JS to still be an intermediate phase to where we're truly going.)
As for the fact that it will be a mess... well... yeah, it will. Welcome to the web.
[1]: I know about the "Turing complete" CSS. It requires user interaction. Cute, but nothing more.
[2]: "What? The semantic web is stronger than ever! Just look at what Google does with its search results!" ... which is a mix of some ad-hoc tags that are rarely the RDF tags the Semantic Web vision was based on, and a whole whackload of machine learning and language analysis. The Semantic Web vision was fundamentally that we can just hand tags out and everybody in the world will eagerly and accurately classify their stuff for you. It has failed (for reasons meditating on the previous sentence will make abundantly obvious), and what today seems to be the "Semantic web" is even moreso a repudiation of the original ideas, rather than confirmation.
It's probably fair to say the semantic web is about trying to make your data accessible. It includes considering that you don't know what the user agent is going to be, what degree of separation there is between that user agent and the user, how the people behind it might find whatever data you're presenting to be useful, what the capabilities of the user themselves is. So you make some effort to produce a resource that's legible to person or machine guided with reasonable direction. If you know there's an existing convention for expressing semantics that overlap with your domain, sure, use that, but if not, any thoughtful reflection of the underlying data will probably be useful.
This does take some effort, and there's the question of whether or not it's worth it, particularly in a business context, because the unexpected uses of your data are often opportunities for others to not only add value but capture it. The Google example is relevant here.
But the other thing is, in my experience, it's useful to you. There's a dictum attributed to Torvalds: "Bad programmers worry about the code. Good programmers worry about data structures and their relationships." I've observed that when a web application project is oriented around thinking about relevant data and its semantically-accessible representation (that "R" in URL), the overall legibility of the project improves from an engineering perspective.
Right now, with the approach of treating the browser as The VM That Lived™, it seems to me the gestalt is very much about worrying about the code.
None of this is to say, though, that CSS is THE way to style documents. There's nothing about semantic resource oriented thinking that precludes using JavaScript or something else to control visual presentation. There's a lot of ways to use JS to do things worse than CSS, and CSS despite some serious warts does have a couple of decades of good thinking put into it as well, but I think there's a case to be made for examining approaches from JavaScript or another DSL (or DSSSL, heh).
I'm talking about how Google now knows business hours and addresses and other such things about local businesses. It isn't because local businesses went in and labeled their HTML semantically. I was interacting with one business a couple of months ago that literally left the stock photos of restaurants up on their webpage that look nothing like their current location, and didn't care, because as far as the business owner was concerned, if the menu was up, the website was basically done.
"It's probably fair to say the semantic web is about trying to make your data accessible."
I'm not just using the Semantic Web in a vague way. I'm using it in the way in which the term was used ~2005 (and a few years in each direction), when the religiousity around declarative CSS and such was at its fever pitch. It was not just a vague desire that somebody find something useful; people literally thought someday you'd be able to do things like
import semantic
print semantic.Website("http://www.chilis.com/").Get("CEO")
It failed. It failed hard. It failed so hard and so big that there's still people who haven't processed its failure, because they still think something like "it hasn't been tried", without realizing that that's how hard it failed... it was such a failure that it wasn't even a thing that could be tried because it was too impractical. But every once in a while the idea still pops up like a shambling zombie that doesn't realize it's been made dead twice over.
CSS itself isn't vestigial, but a lot of aspects of its design are, including a lot of people's vague hopes about how maybe someday it'll sort of kinda become "Semantic" someday if we just keep hoping hard enough, despite its decade+ record of failure on that front. If somehow the web had been nothing but style tags until today, and we set out to replace CSS, I seriously doubt the result would be CSS again; it would probably be a JS extension.
Consider, though, that this is in part because there already are conventions for this kind of data that make it easier for people (or machines) to pull that data out of the page. The semantic signifiers aren't markup, which moves the problem out of the trivial realm, but they're notable enough it's not even particularly necessary to use machine learning to find them.
Addresses and hours are actually examples of the utility of semantic conventions, even if they're not part of a markup spec.
> I'm not just using the Semantic Web in a vague way. I'm using it in the way in which the term was used ~2005 (and a few years in each direction), when the religiousity around declarative CSS and such was at its fever pitch.
Speaking of religiousity, the religious world has fundamentalists who see their texts claim a flood covered the whole earth and believe the only way to read that is absolutely and literally. There are atheists who agree that's the correct way to read those texts and so obviously they're ridiculous and consequently without value. It's interesting how often the anti-religious and the fundamentalists agree on premises if not conclusions.
There was a movement of true believers in a specific vision of the semantic web. What you're talking about may be the only thing those people mean by the semantic web, but it isn't the only thing that people have meant when invoking concerns about semantic markup.
Perhaps it is silly to get bogged down in a discussion of the semantics of the phrases like "The Semantic Web." Perhaps instead it would be helpful if we could introduce some distinctions through the increased structure of formal terminology?
If you spent four years trying to write UIs on the order of 100k SLOC and style them without CSS, you'd realize pretty damn fast that you want CSS.
In contrast, inline parsed CSS such as styled-components seems nuts to me.
The syntax was also awkward to me at first:
const StyledLink = styled(Link)`
color: palevioletred;
font-weight: bold;
`;
const StyledLink = styled(Link)({
color: "palevioltred",
fontWeight: "bold"
})
(Edited for some formatting)
const Button = styled.button` font-weight: {props => props.active ? 'bold' : 'none'} `; <Button active > This will be bold </Button>
I've found it to be very handy.
If the browser is what I have to work with then I am going to be writing JavaScript to manipulate HTML / CSS. No amount of CSS wizardy is going to really help. At the end of the day my logic is in JSS and I have to update a UI somehow. This is where and why design patterns like MVC are so popular. You can do all the ugly integrated JS/HTML/CSS in UI components just like in any native UI toolkit and then you update these thru your more pure "controller" logic that tries its best to just shove some data at the UI later and let it do its thing.
Somewhere, if not MVC, but still with some separation between UI and your app logic you still have code that says "Okay, some state has changed, anyone that cares, here is the state that has changed."
I think what the author laments is that is is extremely easy/tempting and common to just dig into those always available globals to solve design problems. This is why so many JS template and other frameworks exist, everyone is trying to find a nice way to do this that makes sense to them. So, I don't care what you do in your UI layer. If you want to make a rats nest of CSS in JS, go for it. If you want to create some beautiful HTML+CSS+JS design that minimizes JS and CSS weirdness, go for it. As long as you give me an API to deal with your thing and not some ass-ugly encapsulation breaking thing that makes me deal with the UI I can separate out the coding effort into better conceptual parts.
This is where people get frustrated with modern JS. As an experienced programmer I can often get things done quickly in most environments and figure out the key parts pretty quickly, even when you are doing things like dependency injection or I have to go through your abstracted bi-bidirectionally dependent class hierarchy hell, I am okay with this. Drop me into a modern JS stack where in order to "do things right" I have to basically completely relearn CSS and figure out a dozen new esoteric and new JS micro frameworks and I just get annoyed.
So far the only antidote I have found to this was Vue. It seems to support this more immediate dirty style of scribbling with DOM globals or the fancier modern things advanced JS/CSS UI folks know how to do that take days of `npm install` and packing and minifying and JSXing and whatever the heck else is going on in the JS world these days.
Anyway, my point was, deal with it. CSS/HTML/DOM kind of suck as a UI layer, but they work. Hide it in your basement. Don't let it infect the rest of your code using well tread design and programming practices. Get on with your life.
edit: Just to add, my one real criticism for the topic of discussion here is that it takes a LOT of esoteric, bleeding edge knowledge to "do the right thing" in JS/CSS these days. CSS is always adding new things and it creates a compatibility nightmare. As a casual occasional person that wants to write a UI using CSS/DOM I am never going to a.) reach the complexity where this matters and b.) have time to learn all that stuff to do it right. I am not convinced big teams with people dedicated to this chore can learn quick enough to keep up while still building a system that plays well with development teams and their speed of knowledge consumption/learning while trying to ship code. Old school things still work, are reliably, and solve the problem 80-90% of the time.
I think the problem is that developers do not understand that CSS should be treated like other languages, and developers should organize it rather than let anyone write it as they wish. You don't write your server code in a single file without functions, using global variables and introducing side effects, you don't let a trainee edit important code without reviews, why do you do it with CSS?
I remember reading that Github had something around 9000 CSS rules on a single page. Github developers are talented, but somehow they didn't pay proper attention to CSS code too.
CSS code should be split into components, should be easy to analyze, and should be written so that minor edit of one widget won't break something else on another page.
> In fact the seperation causes so much mental overhead, that we need interactive browser dev tools just to be able to find what styles are applied to what element.
That means CSS is not well organized.
I was one of the skeptics and felt CSS, SASS, or Less.js was good enough for me until one I day I was tired of setting up my loader in Webpack and I just dropped in styled-components.
And then my JSX was more beautiful because my tags now had its purpose in the name. And I didn't need to worry about class names anymore. And adding variations (modifiers in BEM) was a breeze. And I didn't need to go back a forth between the CSS and the component to style it. It was just so much better that now I'm a convert. I still can work with CSS only but the convenience that styled-components brings to my components is invaluable.
I hope this sheds some light as to why we prefer to write CSS in JS than writing good old CSS.
https://vuejs.org/v2/guide/single-file-components.html
About CSS in JS, though, it mostly just seems like a different way of getting the same thing on the page, changed only by the idea of scoping it to some component and maybe some needed flexibility when building dynamic CSS rules. I'm still not convinced any of those CSS approaches propped by the author are necessary or even necessarily that helpful. They can be confusing to developers not familiar with it and burdensome when truly not needed. I'm open to other opinions, though.
* Is there any special usecase for that kind of feature? I mean a button is a button and should always look the same (except maybe size and color)...
* Aren't components always looking the same way and a simple naming/clustering-strategy like BEM is enough to be flexible to change the style of some specific component?
[Edit] formatting
Scoped CSS (like CSS Modules, or whatever Vue has) is just taking BEM, building that into the language and handling it for you automatically without having to worry about silly Block__object--modifier rules.
I'd like to add that IMO the right approach is to use CSS that belongs to a component in the .vue file, but also keep a global CSS project for utility classes.
In real life large web apps CSS is very coupled to behaviour and DOM structure. A large part of the advances towards _adaptable_ component-based code comes only when you let go of principles like DRY.
Let me put it this way, if I come along to change a feature in one of the 100s or 1000s of components in a project I _only_ want to think about the JS and CSS in that component's folder. I don't want to think about how that component exists in a vast web of generic CSS utilities and abstracted decoupled code. Copy and pasting CSS properties is cheap. Conversely overly abstracting your presentational code is a short cut to expensive CSS spaghetti.
It's about component encapsulation, which intimately includes its visual presentation. If you can't think of your component as encapsulated single unit then you might as well not be using components. And if you're not using components, then for the love of God don't use CSS in JS.
> I don't want to think about how that component exists in a vast web of generic CSS utilities and abstracted decoupled code. Copy and pasting CSS properties is cheap. Conversely overly abstracting your presentational code is a short cut to expensive CSS spaghetti.
You probably know this, but based on your phrasing I just wanted to point out that DRY isn't for mechanically compressing source code; it's for removing 'out of sync' issues, like causing bugs when we forget to update this copy of a procedure when we altered that copy.
Removing such 'conceptual repetition' makes life easier, since (a) we don't need to remember any couplings that need to be kept in sync (this is the "obvious" benefit), but equally importantly (b) if there are multiple copies of something, we don't have to worry about the other ones since they're not related.
It's perfectly fine if many similar chunks of code are scattered around a project, as long as they don't have to be 'kept in sync'. The whole point of "components" (/modules/packages/etc.) is to be self-contained, so it's perfectly reasonable to avoid coupling them together in a "vast web".
Wrong abstraction < Redundancy < Elegant abstractionWhy even bring that up? All 'CSS-in-JS' approaches have a way to reuse styles without having to resort of copy and paste.
Sealed the fact to me that the author is biased towards CSS, without actually knowing anything about CSS-in-JS solutions.
DRY means different things in different contexts - if you are writing a utility function that is pure and has no side effects, then of course you want to write the function once. The CSS cascade, however, has a tendency to spew side effects all over your application views (e.g. one style that affects a ton of different components), which you then need to override by adding new styles. But be careful, because your new styles have side effects also! Ad infinitum....
For this reason, I regard the CSS cascade as an anti-pattern in most situations. I think that ideally, you want to isolate most of your view specific css to a module attached to the view - so that you are pretty confident that it doesn't have any side effects AND it's easy to know when you can safely delete it. That way you can avoid specificity wars and doing a paranoid but justifiable 'Search in All Files' every time you want to change a style.
Also to implement hover or other styles, you have to go back to CSS or use JS which is much worse.
Also, it's not CSS, it's inline styles, and you lose the cascading advantage. Say I want every anchor tag on my site to be the same color, without CSS I have to go stick that style on every one individually. Realistically you would make it component, but it's a component that wouldn't need to exist with just one line of CSS.
I'm sure it's possible to write in this way correctly, but every time I've seen it it's been awful. But that probably has more to do with the fact that the devs writing it really didn't care much to write clean styles.
I'm not saying CSS is definitively better, that's just my opinion. But if you are going to advocate inline styles you have to know the trade offs and be able to justify them.
But on the other hand, I often end up with a few "primitive" base components that use CSS-in-JS and reuse these components.
So I have a few components with "inline" styles and the rest uses these components.
For a refactor I simply have to change these components.
What? Components and cascading? Only inline styles make sense if we are talking components. Each component must be self-contained, pure and predictive. Why the hell do we want 90s technology again?
And for me personally, at least for heavy-duty web applications, modular components are far more useful.
It doesn't have to be inline styles. Styled components ( https://www.styled-components.com/ ) inject unique css classes.
CSS-in-JS !== inline styles, at all, yet seems to be a rallying call for people who fear "something different".
But you don't. You have a popup calendar component and none of it's links are supposed to be colored at all.
The problem isn't that anyone is wrong here; it's that there are actually multiple things going on here and depending on where you felt the pain last is where your opinion might fall.
I use a lot of 3rd party components that have their own styling and attempting to affect that globally is disastrous for them.
But I'm also rolling out an entirely new style and layout for all our applications and I'm not changing the code -- it's almost entirely global CSS changes.
Sometimes it's hard to reconcile these two things.
Most people seem to find that, rather than providing the consistent theming it promises, automatic inheritance of properties is confusing and unpredictable.
Better to manage consistency through explicit includes of constants instead.
Of course that is how people have been using less/sass for a decade+ now too.
Of course the result is cleanly written style sheets, but the output is a mass of duplicated code.
In that case your source code is tidy and the mass of duplication in the output is not so bad while accounting for gzip.
It's best to account for cascading and take advantage of it when suitable. But sometimes a project can just get away from you doing that and you may be better off doing what you're saying. It all depends on the project.
Most of the talk on this page about styling components would result in mass duplication of code. But that might be best for their project.
while at the same time you maintain the cascading disadvantages. You can't prevent CSS from cascading unless all your styles are inline, or you've OOCSSed your project so thoroughly that you've used classes to recreate inline styles.
Regardless, I'm not a huge fan of these CSS-in-JS techniques anyway (although I don't mind Styled Components if I have to use it). CSS Modules, to me, is a far better approach and it sits there in the middleground between 'Pure CSS' and 'CSS-in-JS'
> OOCSS, SMACSS, BEM, ITCSS, and ECSS.
The beauty of CSS Modules is that it basically merges _naming conventions_ like BEM into CSS 'master'. You don't need a convention because the language just sorts it out for you.
Imagine arguing against variable scope in any other language with just saying "hey, just manually namespace your variables!"
Here is a talk he did on his reasoning - https://www.youtube.com/watch?v=MT4D_DioYC8
IMO - Use the tools/tech that make you happy.
The problem is where that ideal meets reality. Few developers bother learning CSS in depth to avoid spaghetti and poor practices, so whether we like it or not - that is a fact and a reality we have to deal with.
That's solved by tooling and/or better languages and better abstractions - which is what css-in-js is aiming to do. Coding standards like naming conventions aren't enforceable enough to scale in real life :(.
With the exception of a few elements that don't really change at all from one page another like buttons, doing a little bit of copy pasting or search and replace between files is easier.
Sure, you might forget to update one page or component here and there, but at least it won't be broken. Better a component is inconsistent in style but functional than broken.
Using a few variables for things like color and spacing can also help minimize this problem.
Keeping most of my CSS components encapsulated and "namespaced" has worked a lot better in practice than trying to make everything reusable and coupled together in ways that you'll forget about when you have to come back to that project a few months later.
It's the best of both worlds: you don't have to give up CSS tooling like Sass or postcss, but you gain modularity (which is really the only problem CSS-in-JS solves).
I've been writing CSS since IE6 and I was a big proponent of BEM for a long time. In the end it didn't cut it and CSS-in-JS is the first time I've actually felt that the CSS problem is solved. To hear "you should be using BEM instead" feels like someone telling me to go back to ES5.
Don't understand why people will willingly do far more work, with more risk, and more prone to error and bugs, than "learn" (using that liberally given how trivial it is to pick up) a modern approach that solves problems for you, so you can get back to making features, rather than dealing with quirks of older approaches.
Everyone who is confused: HTML, CSS and JS are not concerns. They do not represent an intelligent way of separating your application code. Every time you write the ID of an HTML tag, or a component- or feature-specific class name, you are violating "separation of concerns."
I always hear things like separating everything out that way can make it easier for non-technical people to edit the HTML which is rarely going to be a practical idea.
> Every time you write the ID of an HTML tag, or a component- or feature-specific class name, you are violating "separation of concerns."
Yes, you can separate out a lot of the behaviour and presentation between HTML, CSS and JS but there's always some overlap you just can't get away from. Frequently you want to change the structure of the HTML just to make the styling easier for example because there isn't a practical alternative. Jumping around between files to edit the HTML, add a class, styling the class in CSS, modifying the HTML to help with the styling and then adding click behaviour in JavaScript, then trying to figure how it all works again later involves a lot of context switching.
The appeal of CSS in JS to me is one less language to think in -- one less syntax to worry about and format and lint and forget semicolons in. Also, modules and defining constants. Most web developers seem to use a compile-to-CSS language and a module system these days anyway, rather than vanilla CSS.
The only thing that intrigues me is that you can make pretty website for the paranoids who run hard script blockers.
It is currently the best of both worlds, you can control it with JS in a proper semantic way (through class setting) while keeping 0% replication and loose coupling between concepts.
It also is easily extensible and composes very well. The downsides are that your CSS file is going to be a bit bigger than usual (tachyons.io with all modules goes about 84KB uncompressed, 17KB gziped). But that can be quite irrelevant in big JS oriented projects where most of the size is occupied by big libs.
If you assume an average of 2.3MB[0] on the common page, that is about 3% of your project size for CSS that will not grow past that (atomic approach implies that you won't change it as we add more styles to your page(s)).
[0] https://www.keycdn.com/support/the-growth-of-web-page-size/
Just make sure everybody else in the company is on board with that thought.
A single thing covered in names.
1) A style guide or component library that is used by both design and engineering for any commonly-used component. In some projects this could just be vanilla Bootstrap.
2) An inline style strategy -- there are now several good options to choose from (Styled components, glamorous, etc). A cool idea here that an engineer on my team implemented recently is using a webpack loader to convert our SASS variables into javascript variables so they can be shared with your styled components.
What I do is set my variables in a YAML file and inject those into both my JS and CSS files at build time.
In the real world, people will migrate to what works for keeping people inline. Appealing to better practice will be mowed down by actual practice. Instead write tools which encourage better practice.
This is incorrect. Even if you're using JS for styles you still follow best abstraction practices -- just instead of importing your colors and mixins from another LESS file you're importing them from another JS file. It's no different then designing a styling framework in pure CSS.
What the author is missing here is the biggest single problem with pure CSS -- reusability. Frameworks like React make it incredibly easy to reuse a widget's logic, but what happens when I want to change the styles? JS-in-CSS allows you to do that as part of the widget's API.
Not since the 1990s has it been feasible to write a nontrivial app in which javascript doesn't impact the appearance of a web application.
The real choice is whether one does 50% of the "graphical stuff" in CSS and the other 50% in javascript... Or, instead, one just does 100% of the "graphical stuff" in javascript (independent of the merits of either approach- It may still make more sense to leverage CSS as much as possible, though I'm a skeptic of that viewpoint as well.)
These practices sound a bit outdated to be recommended to someone new to the space. Forget any of these and just use CSS Modules, it guarantees you not only namespacing but explicit dependency between your CSS, which most of these conventions -- which require developer effort and compliance -- can't really offer.
http://caniuse.com/#search=css%20modules
I don't need any fancy tools or precompilers/processors/etc to use BEM or SMACSS, so I think you may be mistaken about how Css Modules are comparable to the list given.
Structural/Behavioral Vs Graphical
The introduction of component based tools changes how we design and build our application. No longer is the fact that you can wireframe your whole application valuable instead being able to build individual components and later compose those is valuable. This means that the graphical properties being tightly coupled to a component is actually good.
Loose coupling vs tight coupling
Component based systems can be built with loosley coupled components, but that doesn't mean the components themselves should loosely coupled to their own implementation. This is more analgous to the native platforms too.
Visual Consistency
Claiming that CSS in JS produces visual incosistency is about as true as claiming that CSS does the same. In both cases you can be more or less inconsitent based on your chosen implementation method. In both cases you can move the lowest level design tokens[0] to a single places/system. Arguably Javascript being a more expressive programming language is actually better at achieving consistency via the more powerful variable system.
Code Reuse
Again with a design token system in place changing the design language etc is as easy as changing a few variables.
Personally I think the more interesting problems with CSS in JS is the inability to extract the CSS out into css files to be shipped along the application and how that pertains to server side rendering.
0: https://developer.salesforce.com/docs/atlas.en-us.lightning....
Here's one of the premises on which the article was written - and I must wholeheartedly disagree.
If you're looking to write clean, maintainable CSS - you MUST consider DOM-structure of the thing you're styling as well. Too often, quirky CSS selectors are written, only because someone failed to foresee how HTML and CSS work together to create a visual.
This decoupling of the HTML that's written, and a CSS "theme" being written/applied after the fact, is also where things like negative margins (ugh) and the like tend to come from.
Now, I've been working on a very large component library in React, and keeping our CSS maintainable has not been an issue. We've got one (S)CSS file per component, and it resides in that component folder.
And while the file is separate, we absolutely do not allow anyone to develop any component anymore, without having any knowledge of how to style the thing.
We used to do exactly that: other devs would develop component, we would try to style them afterwards. This always results in either us writing messy CSS with crazy selectors or - and more often - we simply opted to re-write the entire HTML, to suit our styling needs.
At this point in time though, I would love to write some CSS-in-JS here. Too often we need to use variables based on JS logic; And it ends up as an inline style right now, anyway...
All in all, if the writer believes HTML and CSS can be written separately, without resulting in a terrible mess, I'm having a lot of difficulty accepting that they know what they're talking about. Sounds like they never had to work on, or maintain, a large application.
strikes a really nice balance here imo. I use Radium every day and in general it has been easier to maintain and use in comparison to all css but if I could do it again I would go with styled-components.
Ok, this kinda explains everything.
> Please enable JavaScript to view the comments powered by Disqus.
Instead of CSS-in-JS I think a better pattern for extending CSS with JavaScript is 'event-driven virtual stylesheets', which I call JS-in-CSS.
I'm writing a website dedicated to JS-in-CSS techniques, plugins, and theory. It's still a heavy WIP right now, but there are ~20 plugins that can be used and code samples and links to their documentation which is good to go already: http://responsive.style/
I'm trying to write down and share the results of what I've found trying to combine JavaScript styling with CSS for years, and the patterns and techniques that make the two useful.
You should be able to take full advantage of 100% of CSS's expressive power _and_ still augment it with JavaScript logic. You can have the best of both, and this JS-in-CSS pattern works in every browser you can imagine (I recently got it working in IE7 and IE6 just for fun!(
Is the browser being used to make dynamic "apps" instead of static web pages?
How do app frameworks/toolkits on other platforms style their apps?
And finally:
Do you think the people who designed all of those frameworks were stupid?
Seems to me like the web is finally catching up with the only sane way of styling the widgets in an app. It's done in the same language and it's per component/ widget.
We've done the same with CSS, and CSS modules work extremely well. For us, they've even eased the need for SCSS.
What we really need is a better way to style web apps.
[1] https://hackernoon.com/type-safe-css-modules-with-flow-dd95e...
There seems to be this trend to show off all the possible different ways you know of addressing a single element somewhere, by pointlessly combining them together in brittle ways that depend on each other and accidental document structure, using haphazard random inconsistent naming conventions.
If there's only one of them, then use a fucking id.
We have a company wide rule of no IDs in styles - we actually lint for them. As a front end team, we can't be certain that there will only ever be one of a component on a page at a time. Sometimes we can be mostly certain, but the content authors can theoretically do anything, and our job is to provide them flexibility whilst keeping the site looking good.
Modular CSS would be a God send for us, would be able to handle a lot of things much cleaner but sadly the current build of the CMS doesn't allow for it.
In small sites, or anything with static content, IDs are more than valid. But it becomes a lot harder when dynamic content, especially dynamic components, come into play.
This is not a real answer. It's an attempt to fix the broken screwdriver with ducktape, bird poo, and spit.
Don't get OP's analogy. Does he mean CSS?
While CSS can sometimes be nerve-racking it's the most modern layouting system. There was a reason that the React Native team chose CSS' Flexbox for their layouting system.
CSS-in-JS is more or less enforced-CSS-modules + some sugar + a different way to author your styles.
Most of the arguments there are against CSS modules, or “isolated styles”.
- CSS modules promote more re-use if structured correctly - BEM and the like exist to do the literal opposite, to isolate styles to minimise regression and site wide issues at scale.
- Visual consistency is enforced in CSS usually through variables to make sure spacing, colours etc. are the same, with a default set of global styles. There is literally no difference in a modular approach - you can easily have global styles to theme, and then isolate and import the more specific rules as needed.
This article reads as "I learnt how to do CSS this way so anything new is scary and wrong"
Yes. A little bit sad…
This is a process that takes about 1 day per product page. It's a horrible pain to clean up a site but the payoff is easier maintenance in the future and hopefully some acknowledgement that the page loads better. This skill can easily be trained in to developers. I hope this reminds everyone that computing is a skill that must be practiced.
It isn't normal to use tables for layout these days, just like it is no longer normal to use JavaScript for centering elements vertically. This is fixed with flexbox. Please learn and use it!
Then try adding an isolated component in a sidebar somewhere with 0% risk of visual regression elsewhere.