Earlier quoted context omitted.
Once it’s supported everywhere: https://caniuse.com/?search=nested%20css That’s a lot of red in usage-relative mode. I heard iOS updates are common even for older devices, but I do know macs can’t always update. So Safari Explorer might be a blocker for some time, once again.
> I heard iOS updates are common even for older devices, but I do know macs can’t always update. So Safari Explorer might be a blocker for some time, once again. Probably not. The oldest version of macOS that supports Safari 16.5 [1] which supports CSS Nesting is macOS 11 "Big Sur". Big Sur was released November 2020 and runs on Macs as old as the 2013 MacBook Pro. So even Macs that are 10 years-old running an operat…
Modern CSS for Dynamic Component-Based Architecture
21–27 of 27 posts
Re: Modern CSS for Dynamic Component-Based Architecture
#22Earlier quoted context omitted.
I don't want to make any judgements about you specifically, so this is more of a general observation. It's not meant to be personal or pejoritive. When the Web exploded onto us the first time (late 90s) html and css were limited, and JavaScript mostly unused, so the door opened to lots of "untrained" [1] people to make a living building Web sites. Explosion number 2 comes the the aughts, and is characterised by the s…
I’m used to programming being “pointer arithmetic, manual memory management, higher kinded types and monads” hard and still find CSS to be hard to understand and use, often going with trial and error.
Re: Modern CSS for Dynamic Component-Based Architecture
#23Sometimes I think I know everything that I need to know about web dev, but then I read something like this and learn about new features that I didn't know of. I hope they think about deprecating some features or slowing down on adding features. Letting developers rely on transpilers is great way to keep the core language simple while letting people do anything they want.
Transpilers add significant tooling complexity, so it's nice to not need them.
Things like linters, unit tests, and rules-based code standards would also be included. Development environments have gotten increasingly complicated because CPU time is cheaper than Dev time.
Re: Modern CSS for Dynamic Component-Based Architecture
#24Oh wow, i wasn't aware of nesting support in native css, with variables and nesting, there seems to be no real reason for using sass anymore...
Once it’s supported everywhere: https://caniuse.com/?search=nested%20css That’s a lot of red in usage-relative mode. I heard iOS updates are common even for older devices, but I do know macs can’t always update. So Safari Explorer might be a blocker for some time, once again.
As for Macs, it doesn't matter. You can, and people will, install Chrome on them anyway.
Re: Modern CSS for Dynamic Component-Based Architecture
#25Re: Modern CSS for Dynamic Component-Based Architecture
#26Re: Modern CSS for Dynamic Component-Based Architecture
#27Comprehensive article. I’ve long given up trying to keep up with everything added to the spec since about `display: flex`. There’s just too much stuff, and the shoehorning of features into a syntax/spec from 1996 doesn’t appear to me to be a sustainable long term strategy to facilitate increasingly complex web applications. Maybe it’s been considered, but some use of namespaces and modules in the syntax could at leas…
I’d recommend this article on recent CSS developments: https://developer.chrome.com/blog/whats-new-css-ui-2023/
Be aware of the support of each of them, it’s not 100%, especially depending on your use case.