Re: [elm-discuss] Proposal for a 1st-class, officially-supported CSS package

2016-09-14 Thread suttlecommakevin
Thanks Richard, Could you elaborate on this statement? I'm having trouble understanding how the Elm compiler, known for it's awesome UX and errors, wouldn't help CSS. You even demoed it. https://www.youtube.com/watch?v=R121YzswY_4 * > I can't think of a time its existence would have saved me

Re: [elm-discuss] Proposal for a 1st-class, officially-supported CSS package

2016-09-14 Thread Richard Feldman
I agree with Noah. The class of errors language-level CSS value support would improve is so small, I can't think of a time its existence would have saved me a noticeable amount of debugging time. I value language simplicity, so by default any new language feature has a very high bar to clear to

Re: [elm-discuss] Proposal for a 1st-class, officially-supported CSS package

2016-09-14 Thread suttlecommakevin
Hey Nick, I linked to the source implementation in my original post, but it does overlap the API. Noah, > burdening the compiler with excessive language features. I don't see how supporting CSS via native primitives is burdening the compiler. "Excessive" seems diametrically-opposed to

Re: [elm-discuss] Proposal for a 1st-class, officially-supported CSS package

2016-09-13 Thread Noah Hall
elm-css doesn't need extra first class Elm support. It has first class Elm support - everything is a function. As Nick said, focus on how you _use_ elm-css. It's plenty first-class enough wihtout burdening the compiler with excessive language features. On Tue, Sep 13, 2016 at 7:17 PM, Nick H

Re: [elm-discuss] Proposal for a 1st-class, officially-supported CSS package

2016-09-13 Thread Nick H
Hi Kevin, As far as I can tell, the type alias you are quoting (Value, All, NumberedWeight) are not part of the elm-css API. I can't find them in the package documentation . Are you suggesting a change to the *implementation* of

[elm-discuss] Proposal for a 1st-class, officially-supported CSS package

2016-09-13 Thread suttlecommakevin
*Preface* Saying Elm is a language for front-end apps, but leaving out 1/3 of the stack isn't confidence-inspiring. Between our collective experience, I think we can make something awesome and fun to use, while leveraging the features that make Elm a great language. *Problem to be solved*