search

koudelka / visualixir

A process/message visualizer for BEAM nodes.💪👁
MIT License
1.32k stars 46 forks source link

move to elm? #6

Open koudelka opened 8 years ago

yordis commented 7 years ago

And then you will kill potential contributions because know people that know Javascript have to learn Elm for because "reasons".

I am not saying is bad to use Elm but keep in mind that some people (like me in this case) have no time for be driven by Javascript Community craziness and I would automatically dismiss any idea of contribution just because of that decision.

The same with move to React/Angular/[Insert "Hot Now" Company Driven Tech Here].

Fundamentally there is a lot of architecture decisions you could make and you wouldn't need to go outside of plain VanillaJS that we already know but that's another topic.

What is the current problem? Why should we use Elm? What is the trade off using Elm?

P.S: Please don't, for the good of future contributors

OvermindDL1 commented 7 years ago

As much as I like Elm, I also agree this repo should be kept minimal, I.E. without Elm.

EDIT: Maybe ElixirScript, just to show off more Elixir things, if anything...

codyjroberts commented 7 years ago

I think there's value in switching to Elm, and I have some doubt that it will cause a net loss in contributions. Learning d3 can be just as challenging as learning Elm. I think a non mission critical tool showing off the combination of both Elm and Elixir would serve the community well and may even increase contributions.