On Mon, Sep 19, 2016 at 3:08 PM, Peter Damoc <pda...@gmail.com> wrote:

> Middle Phase
> Once the build environment was set up, things started to move a little
> faster. I then ended up needing CSS and after playing a little bit with
> elm-css and hitting several missing properties I decided to implement my own
> library, taking inspiration from all 3 libraries that were dealing with
> style (rtfeldman/elm-css, elm-style and massung/elm-css). In hindsight this
> might have been a rather bad idea for productivity reasons but I have
> learned a lot.

elm-css is a complicated project. It's mostly complicated because of
_how big css is_. Reimplementing your own is not a reasonable idea for
getting things done :) A much better idea would've been to do one of:
1) fork, add the missing keywords, commit upstream
2) fork and add the missing keywords to your local copy
3) just use 
to achieve this without wasting any time messing around.

> Conclusions
> - Elm is an amazing language. I've had countless moments of sheer pleasure
> programing in Elm for this app.
> - Elm lacks the full story. My main hope was that I could implement the app
> even if I had very little CSS or JS knowledge. I could not do this. Elm does
> not have yet something that would allow someone to stop touching CSS.

Elm hasn't considered this a goal since elm-html has existed. The
graphics library allowed you to forego CSS. Nobody uses the graphics
library in production (though many in academia (did)do, that's what I

> - I would not recommend webdev beginners to take the approach I took. It is
> better for now to stay the tried and proven path and just use Elm to
> implement smaller components in another web framework.

There isn't any reasoning here other than you tried to re-invent the
wheel a few too many times. I would also recommend to those trying to
solve a production problem to do the same ;). I would agree though,
that if you are intended to rely on the existing JS/CSS libraries out
there, you are probably better off investing time in making Elm part
of your site, not making Elm your whole site. You will spend too much
time like this otherwise

> - The tooling around producing a deliverable elm webapp are simply not ready
> yet.

You haven't provided an example of any tooling that "isn't ready yet".
You said you used gulp and there were no issues there. What were these

You received this message because you are subscribed to the Google Groups "Elm 
Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elm-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to