4 ms·

> and there's no choice And this is the thing that many web developers miss. As they've begun to creep into the mobile and desktop space, intent on replacing n

> and there's no choice And this is the thing that many web developers miss. As they've begun to creep into the mobile and desktop space, intent on replacing native experiences with a continual barrage of non-native, bespoke apps, each with their own design, they've mistaken widespread availability with quality and utility — that HTML/CSS UIs are widely available is all to do with ubiquity and lessening an otherwise not-at-all steep learning curve, not technical merit. Give me springs and struts, Autolayout, or PowerApp's style declarative positioning any day.

aphextron 8y ago
>Give me springs and struts, Autolayout, or PowerApp's style declarative positioning any day. Positioning is one thing, but CSS really shines in it's graphical abilities. Autolayout is fantastic, but have you tried writing the custom CoreGraphics code that is required to do anything outside of standard UIKit visuals? Not fun [0]. Being able to just type `background: linear-gradient(orange, green)` is a godsend compared to that stuff. [0] https://github.com/amraboelela/myos.examples/blob/master/CoreGraphics/Gradients/gradients.m https://github.com/amraboelela/myos.examples/blob/master/Cor...
- zapzupnz 8y ago
  Then I guess my dream system marries the two concepts, somehow. I don't think we should accept CSS just because it's what we have; far too many people find it confusing and dislikable. At this point, I'm starting to look into things that "transpile" to CSS.
  - alexis_read 8y ago
    IMHO I think that one of the main problems with CSS is that it doesn't have an explicit model of text. If you have that, then a constraint-based designer can take you through wizards to ask to to consider eg. When there's more text than space. Springs, struts etc. Can take care of layout. Controversially I think we should replace/remove div tags as they don't make all their behavior explicit vs flexbox/ cssgrid etc. Every object should have explicit layout behaviors defined. Then you can compose them or create new objects for undefined cases.

aphextron 8y ago

>Give me springs and struts, Autolayout, or PowerApp's style declarative positioning any day. Positioning is one thing, but CSS really shines in it's graphical abilities. Autolayout is fantastic, but have you tried writing the custom CoreGraphics code that is required to do anything outside of standard UIKit visuals? Not fun [0]. Being able to just type `background: linear-gradient(orange, green)` is a godsend compared to that stuff. [0] https://github.com/amraboelela/myos.examples/blob/master/CoreGraphics/Gradients/gradients.m https://github.com/amraboelela/myos.examples/blob/master/Cor...

zapzupnz 8y ago
Then I guess my dream system marries the two concepts, somehow. I don't think we should accept CSS just because it's what we have; far too many people find it confusing and dislikable. At this point, I'm starting to look into things that "transpile" to CSS.
- alexis_read 8y ago
  IMHO I think that one of the main problems with CSS is that it doesn't have an explicit model of text. If you have that, then a constraint-based designer can take you through wizards to ask to to consider eg. When there's more text than space. Springs, struts etc. Can take care of layout. Controversially I think we should replace/remove div tags as they don't make all their behavior explicit vs flexbox/ cssgrid etc. Every object should have explicit layout behaviors defined. Then you can compose them or create new objects for undefined cases.