-
Notifications
You must be signed in to change notification settings - Fork 109
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
Would Microsoft's elm-json-tree-view package count as them using Elm in production? #36
Comments
@klazuka creator of https://github.com/klazuka/intellij-elm and https://github.com/klazuka/elm-json-tree-view works for MSFT. They might be able to offer some insight into MSFT's use of Elm in Production. 💡 |
I have been using Elm in production at Microsoft since 2016. It is the frontend for a customer support system. |
nelsonic
added a commit
to nelsonic/elm-companies
that referenced
this issue
Dec 10, 2019
…s a better suggestion) fixes jah2488#36
nelsonic
added a commit
to nelsonic/elm-companies
that referenced
this issue
Dec 10, 2019
nelsonic
added a commit
to nelsonic/elm-companies
that referenced
this issue
Dec 10, 2019
jah2488
pushed a commit
that referenced
this issue
Dec 10, 2019
* Add Microsoft to list under new section "Software" (unless someone has a better suggestion) fixes #36 * Add detail required by Pull Request Checklist to Microsoft entry #36 * Reduce heading size of "Planning" from H3 to H4 for consistency. All other sub-headings are H4. * Re-format GitHub link to be in parentheses for consistency with other entries * Add link to Elm Town Podcast episode 43 where "Elm at Microsoft" is discussed. #36 * fix typo "Elmtown" > "Elm Town Podcast"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Microsoft have published an Elm module: https://github.com/Microsoft/elm-json-tree-view, http://package.elm-lang.org/packages/Microsoft/elm-json-tree-view/latest.
Would that be enough to count Microsoft as "using it in production?"
If so, which section should it appear under?
The text was updated successfully, but these errors were encountered: