61–70 of 80 posts
Have not had time to try Elm yet but Elixir is such a pleasure to use, it's painful going back to JS :)
Hopefully something grows out of https://github.com/bryanjos/elixirscript so far it seems very actively developed.
Saying all of that, Elm is pretty nice and I really enjoy using it for some of the same reasons I enjoy Elixir.
Sorry Vincent, you lost me there. Elm is interesting for sure, but it's far from having a low entry barrier. Something has basic has having a button play a sound takes forever to figure out. You almost have to learn everything all over again. It's a cool project and I'm glad it's working out well for you, but Elm has a serious learning curve.
Earlier quoted context omitted.
Hopefully something grows out of https://github.com/bryanjos/elixirscript so far it seems very actively developed.
If issues such as source maps are figured out, I would feel better about people using it. Also, I would like to work on its user friendliness. Saying all of that, Elm is pretty nice and I really enjoy using it for some of the same reasons I enjoy Elixir.
Elixir and Phoenix are stable and by now they're a solid choice (more than enough warranted praise on HN), but I'm still skeptical about Elm from a "platform" perspective. From what I can tell, Elm apps are a single blob of JavaScript that either loads or doesn't (e.g. you can't read the Elm site without JavaScript enabled), while the JavaScript ecosystem is moving towards server-rendering, dead code elimination, and…
Hardly. Server rendering remains at best a novelty, and "progressive web apps" are not coming back anytime soon.
Chiming in with Elixir+Clojurescript. It's what I've been using for most of my projects these days and absolutely love it. Pure functional programming on both, server and client, with the server concentrating on well distributed concurrency and parallel processing with GenServers and the client on immutable front-end code while using Go-blocks for async stuff.
Earlier quoted context omitted.
If issues such as source maps are figured out, I would feel better about people using it. Also, I would like to work on its user friendliness. Saying all of that, Elm is pretty nice and I really enjoy using it for some of the same reasons I enjoy Elixir.
Source maps does seam to be the biggest issue to solve before people can start truly experimenting. But huge congrats on starting and moving forward this amazing project.
> As a business owner/recruiter, I wanted something with a low entry barrier for my future hirings. Elm has a low entry barrier, the JS ecosystem/fatigue/mess doesn't. This is nonsense. There's a much greater pool of talent familiar with javascript than Elm. Using Elm might be marketable ("come work with Elm here!"), but it's a riskier bet for a developer given it's relative immaturity and adoption.
Nice writeup. Elixir definitely seems like a solid language for web dev. For the frontend, I prefer Scala.js since I'm kind of a Scala fanboy, but I've heard great things about Elm. One little comment. At the beginning of the post, you make it seem like the app needs to scale with the number of viewers, when in fact it doesn't. I think you should clarify this to avoid confusion.
We are doing a fairly large Elm app right now. And especially the refactoring reasons and static type system are appealing to us when you work in a team. Also being a functional language it is easy to crank out features in an afterthought, e.g. we added an Undo/Redo feature for operations the user does in this single-page client app. And being side-effect free this "merely" boils down in wrapping function calls in an…
Do you miss this in the backend with Elixir?
the guests were Nicolas Sarkozy (12 millions viewers), Arnaud Montebourg (9 millions) and lately Alain Juppé (13 millions). I would like to see the results of the two other guests.
At work I don't see it happening though, we're a PHP shop now addind nodejs (to my despair) and maybe some Go. I think there is a Haskell fan and that's it.