Re: [elm-discuss] What Elm needs to move forward

Maybe the Elm Weekly newsletter, the ElmTown podcast, and the remote meetups would be useful additions to the http://elm-lang.org/community page? -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving

Re: [elm-discuss] What Elm needs to move forward

On Thursday, November 24, 2016 at 5:35:51 PM UTC, Nick H wrote: > > I found out about the 0.18 release and elm-conf EU via Twitter. Also lots > of announcements there about live coding sessions, local meetups, etc. > > I can try to echo some of that stuff here if the organizers don't do it, >

Re: [elm-discuss] What Elm needs to move forward

Also, I just sent a request to Elm Weekly to > post their newsletter here on the mailing list. Because everybody should > know about it! > Yes, Elm Weekly is ground-zero in Elm world. Subscribe, everyone!! -- You received this message because you are subscribed

Re: [elm-discuss] What Elm needs to move forward

@Max: I think Eve does, what you want. I mean uniting events, http requests, model access. They are all accessed by "search". Look at this page: http://docs.witheve.com/handbook/blocks/ (I know very little about Eve. I was just reading this page) On Thursday, November 24, 2016 at 7:17:27 PM

Re: [elm-discuss] What Elm needs to move forward

Regarding simple type systems, experiments, and language features for library authors -- finding the right abstraction is hard. In 0.18, there's an HTTP abstraction, so you can run requests in parallel (but not arbitrary effects: racing a file read and a file delete is a bad idea!). Then

Re: [elm-discuss] What Elm needs to move forward

I found out about the 0.18 release and elm-conf EU via Twitter. Also lots of announcements there about live coding sessions, local meetups, etc. I can try to echo some of that stuff here if the organizers don't do it, but I am only on Twitter sporadically. But there is a wealth of community

Re: [elm-discuss] What Elm needs to move forward

On Thursday, November 24, 2016 at 2:38:07 PM UTC, Rupert Smith wrote: > > On Thursday, November 24, 2016 at 8:54:33 AM UTC, Zachary Kessin wrote: >> >> I wish I could go to Elm-conf eu, but right now I don't have the budget >> to travel. >> > > Paris 8/9 June 2017 - https://elmeurope.org/ - Is

Re: [elm-discuss] What Elm needs to move forward

On Thursday, November 24, 2016 at 8:54:33 AM UTC, Zachary Kessin wrote: > > I wish I could go to Elm-conf eu, but right now I don't have the budget to > travel. > Paris 8/9 June 2017 - https://elmeurope.org/ - Is this the Elm-conf EU we are talking about? It says: CFP rules Elm Europe 2017

Re: [elm-discuss] What Elm needs to move forward

Let me quote some text from that post to be more precise about what I mean when i say "we need examples" *Why?* > Examples are lightweight and informal; they can often be made in a few > minutes; they lack the ceremony of polished graphics or official tools. Yet > examples are a powerful medium

Re: [elm-discuss] What Elm needs to move forward

Some of this makes me a bit twichy. I think one of Elm's great advantages is that while its type system is good it is also simple. Having tried haskell and quickly drowned I am in favor of keeping the types as simple as possible Zach On Thu, Nov 24, 2016 at 1:11 PM, John Orford

Re: [elm-discuss] What Elm needs to move forward

Something that I feel isn't acknowledged is that it's ok to have a language with more advanced features for library authors than library consumers. I don't see that it follows that having more advanced features makes the language harder to use for beginners (I'd argue the opposite even). I do

Re: [elm-discuss] What Elm needs to move forward

Oliver, I understand. But... we are swimming in a sea of imperative programmers. A lot of FP is not obviously better for them. >From my POV, this is Elm's greatest strength and weakness. It would be so easy to be a PureScript and corner a hardcore niche, where 'power' is everything. Elm has a

Re: [elm-discuss] What Elm needs to move forward

My learning curve has been similar to what Oliver describes. IMHO, there still a large gap between The Official Guide and the community platforms, that needs to be filled. The Official Guide is a great doc, but it has very few examples, and mostly entry-level and small. Outside the guide, the

Re: [elm-discuss] What Elm needs to move forward

I'm definitely still in the process of moving my thinking into a functional approach (currently working through Programming Haskell and Bartosz Milewski 's Category Theory series on youtube, both recommended by other Elmers so thanks!). The lack of

Re: [elm-discuss] What Elm needs to move forward

On Thu, Nov 24, 2016 at 11:17 AM, Oliver Searle-Barnes wrote: > The fact remains though that I don't feel I can offer a sound > justification as to why it's far more complicated to do these things in > Elm. Elm strives to be easy for users to understand, in this area it is >

Re: [elm-discuss] What Elm needs to move forward

I'm going to touch on a couple of sensitive areas here, hopefully you'll take my comments in the manner they're intended, to try and expose problems that newcomers from other frameworks face so that we can think about how we might improve the situation. I've been using Elm a good portion of

Re: [elm-discuss] What Elm needs to move forward

On Thu, Nov 24, 2016 at 11:01 AM, John Orford wrote: > On the perennial CSS-in-Elm topic - I think Elm's lack in this regard > reflects a general lack of being able to do CSS in an elegant manner > (correct me if I am wrong). > > I am pretty sure if there was a clear way

Re: [elm-discuss] What Elm needs to move forward

On Thu, Nov 24, 2016 at 10:54 AM, Zachary Kessin wrote: > What topics should we cover? > That's like putting the cart before the horses. We need first to develop a coherent vision to where do we want to take Elm. I'll reuse a map from a book that I'm reading now: [image:

Re: [elm-discuss] What Elm needs to move forward

On the perennial CSS-in-Elm topic - I think Elm's lack in this regard reflects a general lack of being able to do CSS in an elegant manner (correct me if I am wrong). I am pretty sure if there was a clear way to do CSS right generally, Elm would've jumped on that band wagon. Having said all

Re: [elm-discuss] What Elm needs to move forward

I'm having fun learning programming as a hobby and Elm is the most beautiful, friendly, clean and focused language that I've tried, including JS frameworks. I see it as a great solution for building logic and structure (HTML) of an app. It's true, styling (CSS) is almost completely absent. Elm

Re: [elm-discuss] What Elm needs to move forward

I had submitted a couple of talks on advance Elm usage for elm-conf, but sadly that never happened. I have however talked about this kinda thing in local meetups and in the remote meetup. Sadly the most interesting and relevant one (on how to not get blocked with Elm in production) failed to

Re: [elm-discuss] What Elm needs to move forward

I think we are only differing on the details. We could use talks / blogposts on all of those things. If you want to write a guest blogpost on any of the above I would be happy to put it on my blog. Zach On Thu, Nov 24, 2016 at 9:31 AM, Peter Damoc wrote: > I beg to differ. >

[elm-discuss] What Elm needs to move forward

I've seen a short blogpost by Zach http://get-finch.com/2016/11/23/what_elm_needs_to_to_move_forward.html and it got me curious. What do the rest of you think Elm needs to move forward faster? (it is already moving forward and will continue to do so but... maybe some things can accelerate the