Re: [elm-discuss] Re: Post mortem for my first attempt at using Elm in a real app.

Thanks for a very informative answer! I think this is a very important part of making an elm application work when it grows. I'm pretty sure that we should be very careful before breaking stuff "prematurely". I started writing an app breaking it up like i used to break up my react/redux -apps,

Re: [elm-discuss] Re: Post mortem for my first attempt at using Elm in a real app.

> - *Elm is an amazing language.* I've had countless moments of sheer pleasure programming in Elm for this app. Actually, this is *my* take away from the very nicely written, down to earth post-mortem. I've been hammering away at web-frameworks for 4 yrs (angular, blaze, react) and windows

Re: [elm-discuss] Re: Post mortem for my first attempt at using Elm in a real app.

> On Sep 20, 2016, at 3:46 PM, Peter Damoc wrote: > > As Richard pointed out, Elm is a great choice when the team is already > comfortable with web-dev. > I am a beginner in this field. I’m a front-end beginner too. I wonder how many of us there are, and how we might help

[elm-discuss] Re: Post mortem for my first attempt at using Elm in a real app.

On Monday, September 19, 2016 at 2:08:43 PM UTC+1, Peter Damoc wrote: > > I keep postponing this for a few weeks but today my partner decided to > stop the collaboration and I'll take advantage of this moment to write this > post mortem. > Di your 'collaboration' end because Elm turned out to

Re: [elm-discuss] Re: Post mortem for my first attempt at using Elm in a real app.

On Tue, Sep 20, 2016 at 5:18 PM, Lars Jacobsson wrote: > Peter - just out of curiosity: How did you split those 8000 LOC up? Did > you go for a structured component/react type splitup, or did you split > "organically" when the need occurred? > It was more of an

[elm-discuss] Re: Post mortem for my first attempt at using Elm in a real app.

SCSS helps 'some' of the CSS woes at least. I keep my CSS outside of elm and in SCSS and it works decently(ish). On Tuesday, September 20, 2016 at 7:20:32 AM UTC-6, Rupert Smith wrote: > > On Monday, September 19, 2016 at 6:18:33 PM UTC+1, Rex van der Spuy wrote: >> >> CSS is hell-on-wheels:

[elm-discuss] Re: Post mortem for my first attempt at using Elm in a real app.

Peter - just out of curiosity: How did you split those 8000 LOC up? Did you go for a structured component/react type splitup, or did you split "organically" when the need occurred? > > > Another large amount of time was spent trying to integrate a carousel. I > ended up reimplementing a bare

[elm-discuss] Re: Post mortem for my first attempt at using Elm in a real app.

Peter - just out of curiosity: How did you split those 8000 LOC up? Did you go for a structured component/react type splitup, or did you split "organically" when the need occurred? On Monday, September 19, 2016 at 3:08:43 PM UTC+2, Peter Damoc wrote: > > I keep postponing this for a few weeks

[elm-discuss] Re: Post mortem for my first attempt at using Elm in a real app.

On Monday, September 19, 2016 at 6:18:33 PM UTC+1, Rex van der Spuy wrote: > > CSS is hell-on-wheels: the most time I've spent debugging my Elm apps have > not been with my Elm code, but with the CSS. > > Hey, Elm Community, we've solved JavaScript now we need a real solution to > CSS! :) > I

[elm-discuss] Re: Post mortem for my first attempt at using Elm in a real app.

Thank you for posting this Peter! It's always informative to hear different perspectives. Sorry to hear yours wasn't positive. > -* I would not recommend webdev beginners to take the approach I took.* > This is my big takeaway here. At work we've had a great experience following the the

[elm-discuss] Re: Post mortem for my first attempt at using Elm in a real app.

Thanks for this great writeup! It really helps to read about other's experiences in an authentic and non-promotional way like this when making stack decision. On Monday, September 19, 2016 at 9:08:43 AM UTC-4, Peter Damoc wrote: > > I keep postponing this for a few weeks but today my partner