loading...

Ask DEV.to : Why there is no CSS in the cloud

twitter logo ・1 min read

I did not found a single reason that there’s no reason CSS couldn’t be created dynamically through some third-party service.

If CSS would have been in the cloud, a designer could update the look of your site without having to push out new code, this would also solve the headache of cross-browser compatibility.

twitter logo DISCUSS (10)
markdown guide
 

Can you explain a bit more about your idea, I don't quite understand what you mean. What do you imagine?

 
 

So you are talking about a visual code editor for css only that resides in the cloud? You can log into it and make amendments to the styling of a given website?

I think most developers enjoy using IDE's text editors, source control and having the CSS in the same project in the same place for convenience.
The bigger issue to keep in mind would be security. As the cloud is just somebody else's computer it would potentially open up an attack vector.

The other things to consider, speed, remote code is slower, your CSS would need to be GET and downloaded cached, painted and so on. We aren't all blessed with fast internet, but okay edge caching helps and cdns do this.

A reasonable and more viable solution, have CSS on your local machine but have CSS variables hooked up to this cloud dashboard, get those values in JavaScript via fetch and then set those CSS variables via JavaScript also.

Imagine if a designer could modify your webapp etc.. without pushing out code ^

Because styling involves knowledge in more than just css it takes knowledge in UX and accessibility and also atleast in my experience, that most designers that know CSS are also developers as well, it's far more likely that this target audience doesn't exist yet, but by all means make it happen. Just because something isn't done that way doesn't mean it shouldn't exist. Maybe such a tool could give warnings around accessibility and poor UX in design.

 

Simple. CSS or styling is often a creative work, as creative as code writing, or software engineering, hence, leave it to the developers.
I guess we have to wait till we have a offering for code-as-a-service, and style-as-a-service will follow automatically.

 
 

Could you maybe explain a bit more how this should have an impact on cross-browser compatibility? Wouldn't it still be neccessary to write multiple CSS rules for browsers with missing features?

Classic DEV Post from Apr 3 '19

11 Awesome Resources for Building Your Applications in CI Using Azure DevOps Pipelines

This isn't your average article. It may be more accurate to classify this artic...

Saad Alem profile image