Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion: to elm or not to elm #39

Open
octopusinvitro opened this issue Jan 15, 2018 · 0 comments
Open

Discussion: to elm or not to elm #39

octopusinvitro opened this issue Jan 15, 2018 · 0 comments
Labels

Comments

@octopusinvitro
Copy link
Contributor

octopusinvitro commented Jan 15, 2018

See our contributing guides.

Discussion open on incorporating Elm or not:

Pros

  • As opposed to JavaScript, Elm is a proper programming language
  • Also proper functional language
  • The error messages and time travel make it easy to debug

Cons

  • An extra layer of complexity
  • An extra language to learn for beginners wanting to contribute to the repo
  • An extra language to learn for designers

I don't think we should incorporate the new shiny technology just because it's shiny, but because it will solve a problem for us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant