Bramus is a frontend web developer from Belgium, working as a Chrome Developer Relations Engineer at Google.
Exactly.
However… CSS features are a W3C specification and are an early stage [1]. It’s a process that vendors draft and agree on and can terminate.
On top of that I wouldn’t characterise improving css with functions isn’t a _churnful trendchasing_. If anything this will improve accessibility because it’ll be easier to manage size, colour, and motion preferences with better abstractions than media queries everywhere.
Chrome, Chrome, Chrome, and Chrome?
Ironically, Apple's walled garden is the last thing standing between Google and total web dominance.
A CSS issue is not going to break any site unless it causes interactive elements to overlap or be hidden from view. Most sites do not implement bleeding-edge features for this reason. Those that want to set it up will do it in such a way that there's a fallback for browsers that don't support that function.
Custom functions have been a huge web developer request for a long, long time and is one of the remaining gaps between standard CSS and Sass/LESS, after variables and nesting shipped. Mixins are next, and they'll be good too.
Not every advancement in the web platform needs to be some kind of conspiracy.
- Google: It's implemented
- People: Screw Google and their monopolistic tactics
> If web developers would just focus on making simple
That boat is long gone. The people with money don't want that, they want a platform on which to shove ads down your throat. It's successful.
Mozilla has a revenue of like $600M. They should have no problem keeping up with popular w3c standards. Hell, even opera, with only a tiny fraction of users can keep up.