I don't like CSS
-
Aside from the usual gripes about the over complicatedness of CSS from a usability standpoint, I have problems with it from an implementation standpoint. CSS requires a DOM, just like JS does. With JS it's understandable. With CSS it's because they added a lot of more or less quasi-useful "convenience" features to their selectors. If you could only do class and id based selectors your entire document could be parsed top-down, which is much more efficient than loading it all into RAM. Why does it matter? Because embedded things exist, and HTML is so prevalent. If it wasn't for CSS a lot more devices could render a reasonable subset of HTML5. I think they should at least come out with a standard like say eCSS (for embedded) that's a subset for forward only processing. CSS is illustrative of what happens when you give a standards committee nothing better to do for decades.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
Aside from the usual gripes about the over complicatedness of CSS from a usability standpoint, I have problems with it from an implementation standpoint. CSS requires a DOM, just like JS does. With JS it's understandable. With CSS it's because they added a lot of more or less quasi-useful "convenience" features to their selectors. If you could only do class and id based selectors your entire document could be parsed top-down, which is much more efficient than loading it all into RAM. Why does it matter? Because embedded things exist, and HTML is so prevalent. If it wasn't for CSS a lot more devices could render a reasonable subset of HTML5. I think they should at least come out with a standard like say eCSS (for embedded) that's a subset for forward only processing. CSS is illustrative of what happens when you give a standards committee nothing better to do for decades.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
I think you are not the only one :rolleyes: :-D
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
Aside from the usual gripes about the over complicatedness of CSS from a usability standpoint, I have problems with it from an implementation standpoint. CSS requires a DOM, just like JS does. With JS it's understandable. With CSS it's because they added a lot of more or less quasi-useful "convenience" features to their selectors. If you could only do class and id based selectors your entire document could be parsed top-down, which is much more efficient than loading it all into RAM. Why does it matter? Because embedded things exist, and HTML is so prevalent. If it wasn't for CSS a lot more devices could render a reasonable subset of HTML5. I think they should at least come out with a standard like say eCSS (for embedded) that's a subset for forward only processing. CSS is illustrative of what happens when you give a standards committee nothing better to do for decades.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
I have a love/hate relationship with CSS. I love what it enables me to do (layout and styling), but I hate having to google the selectors/syntax when it gets complicated...however there's certainly no shortage of references to anything you need to do. As for html/css/javascript, I chose this combination recently to render scorecard style reports in a winforms project. Build a webpage bit by bit and throw it into a browser control...it takes me back to the late 90's when I was building webpages with classic asp! :laugh:
"Go forth into the source" - Neal Morse "Hope is contagious"
-
I have a love/hate relationship with CSS. I love what it enables me to do (layout and styling), but I hate having to google the selectors/syntax when it gets complicated...however there's certainly no shortage of references to anything you need to do. As for html/css/javascript, I chose this combination recently to render scorecard style reports in a winforms project. Build a webpage bit by bit and throw it into a browser control...it takes me back to the late 90's when I was building webpages with classic asp! :laugh:
"Go forth into the source" - Neal Morse "Hope is contagious"
I think really, just paring down a standard for things like embedded and formalizing the pared down "standard" for e-readers (it already sort of defines a subset depending on the format) it would open it up to a lot more hardware. And frankly, it's so sprawling at this point that a cleaner, lighter version wouldn't hurt.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
Aside from the usual gripes about the over complicatedness of CSS from a usability standpoint, I have problems with it from an implementation standpoint. CSS requires a DOM, just like JS does. With JS it's understandable. With CSS it's because they added a lot of more or less quasi-useful "convenience" features to their selectors. If you could only do class and id based selectors your entire document could be parsed top-down, which is much more efficient than loading it all into RAM. Why does it matter? Because embedded things exist, and HTML is so prevalent. If it wasn't for CSS a lot more devices could render a reasonable subset of HTML5. I think they should at least come out with a standard like say eCSS (for embedded) that's a subset for forward only processing. CSS is illustrative of what happens when you give a standards committee nothing better to do for decades.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
Look at `CSSStyleSheets`. ```js const rules = new CSSStyleSheet(); rules.insertRule("selector {rules}"); document.adoptedStyleSheet.push(rules); ``` This provides some separation and you can replace all `` tags with `<script>`.</x-turndown>
I mean, that's javascript though. I'm more talking about parsing and interpreting CSS properly on embedded systems, no JavaScript. Think a stripped down webkit for small embedded devices. CSS as it stands requires the DOM. There's a reasonable subset of it in terms of selector syntax that wouldn't require a DOM and could be forward only parsed.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix