Elm Europe will be a two-day conference dedicated to Elm, taking place at the EFREI Engineering School in Villejuif on June, 8-9th 2017.
The event is organized by the Elm community, for the Elm community, with the willing of sharing knowledge, news about the language, and meeting interesting people.
If you need Elm developers, please go to our job board : elm.jobboardmaker.com/job_offers
About the problem of fitting the lables into the canvas when the canvas' size is changing per render frame. This problem can be solved by using uniforms as width and height of the canvas. So we can calculate the text scale by the math if we know the ratio.
I've been trying to tidy up an existing, large Vue codebase by adding Typescript, ESLint rules, prettier, and written programming guidelines; yet no matter how many rules I add, our programmers are to come up with the most insane patterns that makes the app hopelessly difficult to maintain. I am curious if an Elm app would scale better with a large team.
I think you should focus on libraries like react-native and weex. They are two gross niches indeed: iOS and Android is much more productive for you than scientific computations and data visualization.
I am tired of all these stupid toy Elm demos. If nobody can build a beautiful fully functioning website (using rich UI) with it, then throw it in the garbage. Why should have waste my time with Elm, when I can directly use Haskell and even Rust or Julia. If you guys want to convince folks to move to Elm, your demos have to be more convincing than numbers incrementing in a browser. JavaScript (ES 3) has been doing this for almost 3 decades now.
Go, Evan! Love the sensible opinions on solving difficult problems and release cycles. I came to find the gen on elm update frequency - I found so much more.
At 34:54, it looks like Richard has built a finite state machine but missing vectors. Why not just create a state machine with proper transitions? I'm not being critical; I am genuinely ignorant and curious. It's possible to do in Elm, yes?
Did the v0.19 release help with compile times? It's just a quarter of a second on my 10k v0.19 codebase, but I'd be uneasy if 10x the code means much much longer compile times.
No COVID -- I love it! 21:50 Dict -- wait until you hear "hairy" FYI -- you may wanna go full Category Theory with Dr.Bartosz Milewski ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-I8LbkfSSR58.html
Neat talk, I like the approach of getting something going as quickly as possible like this. It seems like you need to have a strong vision of what you want it to be, which is tough from the getgo.
It looks great. But I didn't got how can you write type signature for clearUser user = clearContact user >> clearAddress user ? In Haskell rio style there is a way to intersect type-classes. But how do you intersect extensible records in Elm?
Not sure I understand why you'd need to reverse a list after a map... I mean, isn't it simply: If you have an empty list, return it. Otherwise apply the transformation to the head, map the function to the tail, and cons the two ? Also, it's unclear to me how these collections are "persistent."
What a great talk. My experience has been very similar: Elm is like a secret super-power. (And we used Elixir on the backend, another secret super-power.; )
That feeling when the video is zoomed in on the speaker and multiple slides go by that you CANT SEE.... arghhhh!!! Why oh why don't the people that film these talks learn not to do that?!?!?
I’m very curious about Elm, it’s so different to anything I’ve been used too. Would you say testing is mostly not necessary with Elm? As in, once you’ve validated a fundamental concept in your app, it works as intended and you don’t need to revisit it.
