Elm (programming language): Difference between revisions

Content deleted Content added
Dukese805 (talk | contribs)
m fix broken link
Dukese805 (talk | contribs)
m fix dead links
Line 24:
 
== History ==
Elm was initially designed by Evan Czaplicki as his thesis in 2012.<ref>{{cite web |url=https://elm-lang.org/assets/papers/concurrent-frp.pdf |title=Elm: Concurrent FRP for Functional GUIs}}</ref> The first release of Elm came with many examples and an online editor that made it easy to try out in a [[web browser]].<ref>{{cite web |url=https://elm-lang.org/try |title=Try Elm |website=elm-lang.org |access-date=2019-07-24|archive-url=https://web.archive.org/web/20170521144831/http://elm-lang.org/try|archive-date=2017-05-21 |url-status=deadlive}}</ref> Czaplicki joined [[Prezi]] in 2013 to work on Elm,<ref>{{cite web |url=https://elm-lang.org/news/elm-and-prezi |title=elm and prezi |website=elm-lang.org}}</ref> and in 2016 moved to [[NoRedInk]] as an Open Source Engineer, also starting the Elm Software Foundation.<ref>{{cite web |url=https://elm-lang.org/news/new-adventures-for-elm |title=new adventures for elm |website=elm-lang.org}}</ref>
 
The initial implementation of the Elm compiler targets HyperText Markup Language ([[HTML]]), [[Cascading Style Sheets]] (CSS), and [[JavaScript]].<ref>{{cite web |url=https://github.com/elm/compiler |title=elm/compiler |website=GitHub|date=16 October 2021}}</ref> The set of core tools has continued to expand, now including a [[read–eval–print loop]] (REPL),<ref>{{cite web |url=https://elm-lang.org/news/repl |title=repl |website=elm-lang.org}}</ref> [[Package management system|package manager]],<ref>{{cite web |url=https://elm-lang.org/news/package-manager |title=package manager |website=elm-lang.org}}</ref> time-travelling debugger,<ref>{{cite web |url=https://elm-lang.org/news/time-travel-made-easy |title=Home |website=elm-lang.org}}</ref> and installers for [[macOS]] and [[Microsoft Windows|Windows]].<ref>{{cite web |url=https://guide.elm-lang.org/install.html |title=Install |website=guide.elm-lang.org}}</ref> Elm also has an ecosystem of community created [[Library (computing)|libraries]],<ref>{{Cite web |url=https://package.elm-lang.org/ |title=Elm packages |website=Elm-lang.org}}</ref> and Ellie, an advanced online editor that allows saved work and including community libraries.<ref>{{Cite web |url=https://ellie-app.com/ |title=Ellie |website=Ellie-app.com}}</ref>
Line 82:
Elm does not support [[Type class#Higher-kinded polymorphism|higher-kinded polymorphism]],<ref>{{cite web |title=Higher-Kinded types Not Expressible? #396 |url=https://github.com/elm-lang/elm-compiler/issues/396 |website=github.com/elm-lang/elm-compiler |access-date=6 March 2015}}</ref> which related languages [[Haskell]], [[Scala (programming language)|Scala]] and [[PureScript]] offer, nor does Elm support the creation of [[type class]]es.
 
This means that, for example, Elm does not have a generic <code>map</code> function which works across multiple data structures such as <code>List</code> and <code>Set</code>. In Elm, such functions are typically invoked qualified by their module name, for example calling <code>List.map</code> and <code>Set.map</code>. In Haskell or PureScript, there would be only one function <code>map</code>. This is a known feature request that is on Czaplicki's rough roadmap since at least 2015.<ref>{{cite web |title=Higher-Kinded types Not Expressible #396 |url=https://github.com/elm/compiler/issues/396#issuecomment-128190898 |website=github.com/elm-lang/elm-compiler |access-date=19 November 2019}}</ref> On the other hand, implementations of TEA pattern in advanced languages like [[Scala (programming language)|Scala]] does not suffer from such limitations and can benefit from [[Scala (programming language)|Scala]]'s type classes, [[Type-level programming|type-level]] and [[Kind (type theory)|kind-level]] programming constructs.<ref>{{Cite web |title=The Elm Architecture |url=https://tyrian.indigoengine.io/03-documentation/architecture/the-elm-architecture/.html |access-date=2024-09-07 |website=tyrian.indigoengine.io}}</ref>
 
Another outcome is a large amount of [[boilerplate code]] in medium to large size projects as illustrated by the author of "Elm in Action," a former Elm core team member, in his single page application example<ref>{{cite web |title=Main.elm |url=https://github.com/rtfeldman/elm-spa-example/blob/23dee34dd7a8c26229a03bc8e9f0e034f6222f13/src/Main.elm |website=github.com/rtfeldman/elm-spa-example |access-date=30 June 2020}}</ref> with almost identical fragments being repeated in update, view, subscriptions, route parsing and building functions.