DevelopmentFrontend Development

What are the best solutions to "The JavaScript Problem"?

37
Options 
Considered
0
User 
Recs.
Last 
Updated

Elm vs Typescript vs Haste

 vs ClojureScript vs PureScript vs Idris vs Reason ML vs GHCJS vs Haxe vs Dart vs Fay vs Ceylon vs Brython vs C++ vs F# Fable vs Blazor vs Scala.js vs Utrecht Haskell Compiler vs JavaScript vs PharoJS vs CoffeeScript vs Mint vs Vue.js vs transcrypt vs Kotlin vs What problem? vs Amber vs Imba vs Web Components vs RapydScript vs WebAssembly vs flow vs Roy vs F* vs asm.js vs JSX vs ECMAScript 6 vs flOw vs Flow

Specs

Current stable version

0.19.1

Platforms

Windows Linux Mac Web

GZipped size

23.2 kB

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

3.7

Platforms

-

GZipped size

-

IDE Support

Very good

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

1.9

Platforms

-

GZipped size

32 kB

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

0.15.4

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

3.6.0

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

Web, iOS, Android, Blackberry, Windows, OSX, Linux

GZipped size

-

IDE Support

-

Version

-

Supported languages

C++, C#, Java, Javascript, PHP, Lua, Python, Actionscript

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

2.1.0

Platforms

-

GZipped size

-

IDE Support

Good quality IDE plugins for Jetbrains IDEs and Visual Studio Code

Version

-

Supported languages

-

Standard

ECMA

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

1.3.2

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

2.4.22

Platforms

-

GZipped size

-

IDE Support

Yes

Version

2.4.22

Supported languages

-

Standard

-

License

MIT

Site

https://fable.io/

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

Windows, Linux, Mac

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

1.13.1

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

V8/ChakraCore

Author

Ryan Dahl/Joyent

Version(Latest)

12.x

ECMAScript Modules

Available (as a flag) (only on Node 8.x-10.x)

Minimum Supported ECMAScript Version

ECMAScript 6 (Node v4.x-v10.x)

Version(LTS)

8.x

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

2.3.2

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

MIT

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

0.5.0

Platforms

Mac Linux Web

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

https://www.mint-lang.com

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

Open Source

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

~30KB

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

https://github.com/vuejs/vue

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

1.3

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

Windows Linux FreeBSD

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

https://html.spec.whatwg.org/multipage/scripting.html#custom-elements

Shadow DOM v1

http://w3c.github.io/webcomponents/spec/shadow/

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

-

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

-

File Size

-

Required Android Version

-

Dark Theme

-

In App Purchase

-

Multiple Accounts

-

Widget

-

Inline Media

-

Multireddit

-

Mod Tools

-

Current stable version

-

Platforms

-

GZipped size

-

IDE Support

-

Version

-

Supported languages

-

Standard

-

License

-

Site

-

Engine

-

Author

-

Version(Latest)

-

ECMAScript Modules

-

Minimum Supported ECMAScript Version

-

Version(LTS)

-

Price

$ 4.99

Repository

-

Custom Elements v1

-

Shadow DOM v1

-

Publisher

Deepak Manoharan

File Size

1.8M

Required Android Version

2.2 and up

Dark Theme

Yes

In App Purchase

None

Multiple Accounts

Yes

Widget

No

Inline Media

Yes

Multireddit

Yes

Mod Tools

No

Pros + Cons

Pro
 Clean and elegant

The Elm language is carefully thought out to be as simple and clean as possible while still being very expressive. The end result is that the language itself encourages and often enforces good programming practice.
Comment

Pro
 Designed around high-level front-end development

As Elm was designed as a front-end langauge, it has out of the box support for things like DOM-element creation, letting programmers focus on their application logic, rather than implementation details specific to the web.
Comment

Pro
 Fearless refactoring

Due to Elm's strong type system and friendly/helpful compiler, refactoring is often as easy as making a change in one place and then simply following compiler error messages to see what else needs to be changed.
Comment

Pro
 Growing community

Elm is gaining popularity, somewhat faster than many of the other solutions here. This translates to more code examples, more documentation, and more libraries.
Comment

Pro
 No run-time exceptions

Lack of run-time exceptions makes it easy to produce large swathes of reliable front-end code without drowning in tests.
Comment

Pro
 Haskell-like modules

Elm uses easy to use Haskell-like modules. Use: import List import List as L import List exposing (..) import List exposing ( map, foldl ) import Maybe exposing ( Maybe ) import Maybe exposing ( Maybe(..) ) import Maybe exposing ( Maybe(Just) ) Creation: module MyModule where
Comment

Pro
 Fast HTML rendering

The Elm virtual DOM-based rendering system is very fast.
Comment

Pro
 Purely functional language

You get to use a 100% pure functional mind-set. No side effects when calling your functions.
Comment

Pro
 Static module system

Elm uses easy to use modules. Use: import List import List as L import List exposing (..) import List exposing ( map, foldl ) import Maybe exposing ( Maybe ) import Maybe exposing ( Maybe(..) ) import Maybe exposing ( Maybe(Just) ) Creation: module MyModule exposing (foo, bar)
Comment

Pro
 Package manager enforces semantic versioning

The Elm package manager actually checks for API changes between package versions, classifies them as major/minor/patch, and will enforce proper version numbers appropriately. This means that you can safely update from (e.g.) version 3.1 to 3.2 of a package knowing that it won't break backwards compatibility.
Comment

Pro
 Inferred static typing

ML static typing is great because it's always there, you just choose how explicit you want to be and how much you want the compiler to do.
Comment

Pro
 Easy to code review

The lack of side-effects and simple, consistent language semantics make it easy to quickly review incoming changes.
Comment

Pro
 Great and simple way to learn Purely Functional Programming 

You can try to apply some functional programming ideas in other languages that have an imperative basis, but you haven't seen the real power unless you tried it in the environment of purely functional programming. Elm is a simple language with great learning resources and easy graphical output, which makes it easy to explore the power of functional programming. Plus programming in Elm is very readable.
Comment

Pro
 Good documentation 

Elm is gaining popularity, somewhat faster than many of the other solutions here. This translates to more code examples, more documentation, and more libraries.
Comment

Pro
 Super easy refactoring with very helpful compiler errors

In no other language you can refactor so easy without any worries, since the compiler will guide you through. It is like TDD but than compiler-error driven.
Comment

Pro
 Awesome tooling

Elm Auto-completion is available for most editors. With Atom, for example, Elm plugins are available for linting, formatting, make/compiler support, auto-creating case statements, type-aware auto-complete, refactoring tools, and Elmjutsu will simply overflow you with super useful functions, like navigate to a referenced definition and show expression type. Plus the basic compiler messages.
Comment

Pro
 High-level Functional-Reactive Code

Build animations, games, and interactions with an incredibly small amount of terse, readable code.
Comment

Pro
 Batteries included

The Elm Architecture means you don't need to spend valuable time and effort choosing the right frameworks, state management libraries, or build tooling. It's all built in.
Comment

Pro
 Higher confidence in code correctness and quality

Pure functions, immutable data structures, amazing compiler, clean and homologous syntax used for HTML, logic, and optionally to replace CSS, elimination of entire classes of bugs so you don't even need most unit tests. These factors lead to better code, better programs, higher confidence, and ultimately, more satisfaction.
Comment

Con
 Still young

The language is (as of this writing) at version 0.17, so the set of available libraries is still sparse compared to other languages and there are occasional compiler bugs to watch out for (usually solved by a clean rebuild).
Comment

Con
 Lack of typeclasses

Elm doesn't have typeclasses which means some code needs to be duplicated. A fix in a function that needs typeclasses means all of the duplicates need to be fixed too.
Comment

Con
 Bad documentation

Although language is already 4 years old, syntax and features are still in motion. So there is no good documentation, nor "how-to" examples that are not already outdated.
Comment

Con
 Missing syntactic sugar ('where' clauses, pattern guards)

Elm is missing a lot of syntactic sugar that Haskellers may consider core, such as 'do' notation, 'where' clauses, pattern guards, and operator sections.
Comment

Pro
 Interactive Programming and Hot Swapping

Support for hot swapping and interactive programming is included.
Comment

Pro
 Missing Syntactic sugar

Easy to learn, most functions have only one way, not 5 alternatives where you must study where to best use what.
Comment

Con
 FRP is no longer part of Elm

The most "Wow-able" feature of Elm - Functional Reactive Programming (FRP) - is no longer part of Elm. It got removed in version 0.17 (http://elm-lang.org/blog/farewell-to-frp).
Comment

Con
 Breaking API changes

Migrating an application from 0.18 to 0.19 can be pretty hard due to breaking API changes. On the positive side, though, the language author(s) want to keep the language and the platform clean and concise and don't want to leave any room for dragging old patterns along. But if you have a large codebase then well... You might have to bite the bullet and spend a few days migrating your code. It's just something people should be aware when adopting Elm.
Comment

Con
 No classes and instances

No classes and instances like Haskell has.
Comment

Con
 No higher-kinded types

Comment

Con
 Package manager is strictly controlled

If one wants to publish a native package that can handle some things elm simply can't, one would have to persuade the maintainer since package management is strictly under his control.
Comment

Con
 Looses features because they are used "wrong"

Elm's use case is under strict control of the main developer. If things are done he does not deem right he goes as far as removing language features. As has been the case with infix operators or native packages.
Comment

Con
 Communication with userbase is restricted and often seems to be snippy

Evan the main dev of elm is against roadmaps and announcing what will happen up front. If he answers questions it is often in a bad tone. i.e: https://groups.google.com/forum/#!msg/elm-dev/kNKilHjUYqo/3mTObqyGAgAJ
Comment

Con
 Missing some basic operations, like focusing a field

Comment

Con
 Not quite Haskell semantics

Elm is a strict language, semantically different from Haskell. Elm also borrows a lot from OCaml and F#. While this makes for a nice syntax, it does mean that, for the Haskell programmer, there may be some surprises when it comes to semantics or function names.
Comment

Con
 Using the JS ecosystem is often tedious to impossible

Since Elm's quasi FFI is very limited it often becomes hard to interoperate with js, most libraries cannot really be used in a full blown elm SPA, those that can often need a lot of adaptercode.
Comment

Con
 Huge overhead of code compiled to Javascript

Elm is not for small code injections, project has to be done in Elm alone.
Comment

Pro
 Time-travelling debugger for the frontend

Comment

Pro
 Missing syntactic sugar

Easy to learn, most functions have only one way, not 5 alternatives where you must study where to best use what.
Comment

Con
 Missing some basic operations, like no simple way to focus a field

Comment

Pro
 Time-travelling debugger and Hot-swapping of code

Elms purity and high-level FRP primitives allow for similarly higher-level tools that other languages can only dream of.
Comment

Pro
 First class FRP and Reactive DOM

FRP is at the core of Elm philosophy, thus FRP constructs are really clean and simple to use and integrates really well with the rest of the others libraries. FRP in Elm feels like Reactive Extensions (ReactiveX), so if you are used to this, Elm is probably the easiest way to go.
Comment

Con
 Not self-hosted

This is very important for the maturity of the language but can it be self hosted at all (if not it will be a fat valid con).
Comment

Pro
 Good tooling

All major editors have great support. With Atom for example, Elm plugins are available for linting, formatting, make/compiler support and Elmjutsu will simply overflow you with super useful functions, like navigate to referenced definition and show expression type.
Comment

Pro
 Supports explicit typing

Comment

Pro
 Acts as a transpiler for ES2015/16 features

Comment

Pro
 Compiles to plain Javascript

Every existing Javascript program is already a valid TypeScript program giving it the best support for existing libraries, which is particularly useful if you need to integrate with an existing Javascript code base.
Comment

Pro
 Actually used by large projects in the real world

For instance, Angular 2 is written entirely in Typescript.
Comment

Pro
 Can incrementally convert codebase to Typescript

Comment

Pro
 Optional static typing

Typescript has optional static typing with support for interfaces and generics, and intelligent type inference. It makes refactoring large codebases a breeze, and provides many more safeguards for creating stable code.
Comment

Pro
 Closely tracks ECMAScript standards

Comment

Con
 Syntax is too verbose

Comment

Pro
 Easy to learn for JS/C#/Java Developers

Comment

Pro
 Polyfill for ES6 fat-arrow syntax

Typescript implements the fat arrow syntax, which always maintains the current context for this and is a shorter/more convenient syntax than traditional function definition.
Comment

Pro
 Has a repository of high quality TypeScript type definitions for popular libraries

There are many ready to use and high quality TypeScript definitions for popular libraries including jquery, angular, bootstrap, d3, lodash and many-many more.
Comment

Con
 Less Creativity... If you visualize code execution process in your mind , TS will disrupt it...

Comment

Con
 Removed at build time... so in development, IDE + LS + Ai runtime in background can do better .

Comment

Con
 Is not necessary.. won't work in JS easily, unless you use JS Docs which pollutes code.

the claimed maintainability only applies when a simple/careless developer can't visualize, read and write code correctly, and mess up the code. choose better Devs, in interview ask them to visualize and describe your code. problem solved.
Comment

Con
 Not a language..., is just a tool which must work in background, yet it pollutes your source code logic.

Comment

Con
 Awful error messages

Comparing to Elm or Rust for example, TypeScript's error messages won't say you very much. For example if you change method of interface which your class implements it won't say your class have incorrect implementation. Instead it'll show error in usage of instances of class. In some cases it can spoil hours of your work trying to figure out why your parameters are incorrect.
Comment

Pro
 Low number of logical errors brought in by built-in type annotations

TypeScript's built-in type signatures allow developers to fully document interfaces and make sure that they will be correctly compiled. Therefore, cutting down on logical errors.
Comment

Pro
 Strong typed language

Lots of benefits of it, you can read this.
Comment

Pro
 Works well with existing Javascript code

Can both call Javascript code and be called by Javascript code, making transitioning to the language very easy.
Comment

Pro
 Great support for editors (Sublime, Code, Vim, IntelliJ...)

Comment

Pro
 Strict superset of Javascript

Every existing Javascript program is already a valid TypeScript program giving it the best support for existing libraries, which is particularly useful if you need to integrate with an existing Javascript code base.
Comment

Pro
 Built and supported by Microsoft

Being built by Microsoft, TypeScript is much more likely than most other similar open-source projects to receive continued long-term support, good documentation, and a steady stream of development.
Comment

Pro
 Great support for React, integrated typed JSX parsing

Strongly typed react components, so UI "templating" automatically gains type safety.
Comment

Pro
 Adds support for object-oriented programming

Typescript enables familiar object-oriented programming patterns: classes, inheritance, public/private methods and properties, et cetera.
Comment

Pro
 Clear roadmap

TypeScript has a clear and defined roadmap with rapid and constant releases.
Comment

Pro
 Compiles to very native looking code

Compiles to simple looking Javascript making it easy to understand what is happening and learn the language (if you already know Javascript).
Comment

Pro
 First party Visual Studio support

As a Microsoft developed project, it has first party Visual Studio support that's on par with its C# support with features like syntax sensitive statement completion.
Comment

Pro
 Works well with Angular 2

Angular 2 is built using TypeScript and applications built using it can make use of that (or not).
Comment

Pro
 Ability to do functional programming

Comment

Con
 Less functional

Not too many functional feature when compared to Elm or ClojureScript.
Comment

Con
 Type inference coverage is incomplete

The default type when declaring and using a variable is any. For example, the following should break but does not: function add(a:number) { return a + 1 } function addAB(a, b) {return add(a) + b} addAB("this should break but doesn't :(", 100) In order to avoid this, you have to declare type signatures for every variable or parameter or set the flag --noImplicityAny when running the compiler.
Comment

Con
 No option to declare that a function throws errors

Comment

Con
 Too similar to Javascript

Presents some advantages compared to Javascript, but because it is designed to be a superset of Javascript, it means all the bad parts of Javascript are still present.
Comment

Con
 Unsound type system

Static type checking is for safety, but when the TypeScript type system is designed to be unsound, the safety guarantee is gone. See "A Note on Soundness".
Comment

Con
 Microsoft hand

As TypeScript is developed by Microsoft employees ( = employees of Big Stable company), it has tendency to over-complicate things and advocate bad programming patterns, compensating its weaknesses by encouraging teams to assign more developers onto projects.
Comment

Con
 Interfacing with non-Typescript libraries requires installation of library-specific "definition files"

Comment

Con
 It is not Dart

Use Dart. Dart is a much better language, simpler to understand, better dependency management, static analysis, multi-platform, higher performance across multiple platforms, well designed core libraries, awesome asynchronous features, etc , etc. Use Dart!
Comment

Pro
 Client and Server as the same application

Haste was designed to allow both the client and server to be written as parts of the same, type-safe application. This is in stark contrast to most other options, where the client and server are considered two separate entities, resulting in extra manual validation code and more chances for type errors.
Comment

Pro
 Almost full power of Haskell

Haste supports most all of Haskell except for Template Haskell, including even most GHC extensions.
Comment

Con
 Not widely used

Comment

Pro
 Generates small, reasonably performant code

Comment

Pro
 Automatic, type safe program slicing

Haste lets you write client and server as a single program, automatically generating code for the server as well as the client, giving you full type safety even across the Internet.
Comment

Con
 Lacks some minor Haskell functionality

Lacks support for Template Haskell.
Comment

Con
 Not widely used

Comment

Con
 Not widely used

Comment

Pro
 Immutable persistent datastructures

When DOM is represented with immutable, persistent datastructures, rendering/re-rendering becomes highly optimized (e.g. React.JS, which borrowed ideas from Clojurescript/OM/Reagent).
Comment

Pro
 Pragmatic functional programming

Emphasizes the clarity of functional programming while allowing concessions where necessary to best capture a problem (see STM state management).
Comment

Pro
 Excellent tools for web development

ClojureScript has superb wrappers around React.js (see Reagent) that make building single-page apps a breeze. With figwheel, it's a web dev experience unlike any other -- hotloaded code, repl interaction, and instantly reflected changes make good development fun and fast. You can add things like Garden to make CSS-writing part of the same holistic experience and suddenly all development is a pleasant, smooth process.
Comment

Pro
 Homoiconicity

Code is data and data is easily and directly representable in code.
Comment

Pro
 Macros

Comment

Pro
 Pervasive lazy sequences

Comment

Pro
 STM for deliberate management of state

Software Transactional Model causes global state to be possible but clean, managed in a way like SQL databases with ACID guarantees.
Comment

Pro
 Live interactive programming with figwheel 

Figwheel builds your ClojureScript code and hot loads it into the browser as you are coding! Every time you save your ClojureScript source file, the changes are sent to the browser so that you can see the effects of modifying your code in real time.
Comment

Pro
 Namespacing emphasized

Namespacing is emphasized, something google itself saw as a crucial absence in Javascript. All forms of clojure place a heavy emphasis on the value of namespacing.
Comment

Pro
 Share application logic between browser and Clojure server 

Clojure is also able to run web servers, so one can reap similar benefits to NodeJS in terms of sharing code between client and server.
Comment

Pro
 Targets Google Closure-ready JavaScript for immense optimizations

Google's Closure Library converts regular JavaScript into a highly optimized form - including dead code analysis/elimination. It can even remove pieces of unused code from 3rd party libraries (eg, if you import jQuery but only use one function, Google Closure includes only that piece).
Comment

Pro
 Easy to use existing JavaScript libraries 

Clojure and ClojureScript are designed to be able to interact with their host. So the language by design makes it is easy to use existing JS libraries.
Comment

Pro
 Simple syntax

Lispness makes ClojureScript trivial to comprehend after an initial learning overhead.
Comment

Pro
 Can be used with React out of the box

Comment

Pro
 The Spec core library

From the creator of Clojure: Spec is a new core library (Clojure 1.9 and Clojurescript) to support data and function specifications in Clojure. Writing a spec should enable automatic: Validation, Error reporting, Destructuring, Instrumentation, Test-data generation and Generative test generation.
Comment

Pro
 Dynamic Types

The dynamic typing allows coffee to be written quickly and, as necessary, dispatched on the actual properties of the data (see the Spec pro). This is excellent way to deal with the JSON problem because you can easily consider the shape of the data you're working with, without the overhead of a system-wide type system.
Comment

Pro
 Excellent build tools

Both Leiningen and Boot are great build tools that manage code dependencies and deployment.
Comment

Con
 Dynamic types

But specs are starting to compensate for this.
Comment

Pro
 Has Typeclasses and RankNTypes

Comment

Pro
 High performance FFI code

The Eff monad, which is used for FFI code, optimizes out calls to bind, and supports tail call optimization, resulting in clean, efficient Javascript. The psc compiler also specifically recognizes the ST monad, and transforms scoped variables into mutable Javascript variables, for even more efficient code.
Comment

Pro
 Modules can be compiled to CommonJS

Modules compiled to CommonJS can be included with 'require', making it incredibly simple to call Purescript code from Javascript.
Comment

Pro
 Thorough documentation

The Purescript website has fairly thorough documentation for all of the language's features, and the Purescript blog contains several examples of practical usage, and Pursuit contains the reference documentation.
Comment

Pro
 Multiple (experimental) compilation targets

Experimental backends exist for C++11 (pure11), Lua, Python and the JVM, and PureScript has been used successfully on iOS and Android (via React Native) and AWS Lambda.
Comment

Pro
 Has row polymorphism and extensible effects

Comment

Con
 Missing debugging tools

PureScript does not have the concept of breakpoints and the available debugging tools are restricted to console logging and tracing.
Comment

Con
 Error reporting

PureScript error reporting is not so fancy, requiring some effort to understand what's going on.
Comment

Con
 Not widely used

Comment

Pro
 Pure functional language

You cannot have side effects, unless a function is explicitly defined as so.
Comment

Pro
 Awesome web frameworks

Thermite (React) Halogen (VDOM, similar to ELM) Deku (featuring pursx, JSX like alternative) And hit these up with Signals, Isolated/(Managed?) Components, powerful functions and FFI
Comment

Pro
 Type safety

Compiling should be your first unit test. A tight type system (static and hopefully strong) will catch many logic errors that are often difficult to spot through debugging. In languages like PureScript, if it compiles, it often runs properly.
Comment

Pro
 FFI

FFI system is quite good and easy to use. You can import functions curried or not curried. Records and arrays use native JS objects and arrays.
Comment

Pro
 Higher kinded types

Has Typeclasses and RankNTypes.
Comment

Con
 Lots of dependencies needed to get started

PureScript is written in Haskell, but meant to be used with Node.js. As a result, to get started, users must install Node.js (the PureScript compiler itself can be installed via NPM). In addition, PureScript has different semantics from Haskell, and so even after installing, there's still some overhead to getting productive with PureScript.
Comment

Con
 Restrictive FFI

Functions exported are all curried, and must be called as such from Javascript. The FFI syntax for importing Javascript functions, while slightly simpler and more readable than UHC/Fay's, means that calls to methods on objects must be wrapped to pass the object explicitly as a parameter.
Comment

Pro
 Full dependent types

Idris not only has support for type classes, but is a fully dependently typed language, giving you the full power to statically verify your code.
Comment

Con
 Not widely used

Comment

Con
 Not widely used

Comment

Pro
 Domain driven design and type driven development

Because of full dependent types in Idris, the programmer can focus more on modelling the domain with types and waste less time fixing common bugs that the type checker will catch. Dependent types help apply type driven development and a lot of code auto generation, making the compiler and type checker an ally in developing working software instead of just getting in the way.
Comment

Con
 Weaker type inference

As type inference is undecidable for dependently-typed languages, Idris cannot offer the full type inference that Haskell supports, and so more type annotations will be needed.
Comment

Con
 Different semantics from Haskell

Idris, while similar to Haskell, has strict semantics, which may cause some confusion if your backend is done in Haskell. If using Idris, it would make sense to do the backend in Idris as well, if not for the fact that Idris currently has fewer libraries available for web development than Haskell.
Comment

Pro
 Uses the excellent Bucklescript Ocaml to Javascript transpiler

Comment

Pro
 Has built-in support for React

React components in ReasonML even have a reducer element that can eliminate the need for redux.
Comment

Pro
 Aims to make the transition from Javascript easier

Despite being a completely different language Javascript programmer will find that the syntax of ReasonML has many familiarities with Javascript.
Comment

Pro
 Immutability with escape hatches

Reason includes true immutability, but it has escape hatches to let you use mutations in exceptional cases.
Comment

Pro
 Compiles to JavaScript or assembly (ocaml)

The same reasonml code can compile to js (eg. run on browsers or node.js, use any lib in npm), or compile to assembly through ocaml (unless of course you load js externals), running on any device, with C-comparable (or better) performance.
Comment

Pro
 Backed by Facebook

Comment

Pro
 JSX syntax natively supported

Reason was created by the creator of React, for developers already using JSX to template web or native UIs this is very familiar.
Comment

Con
 A standard async syntax is pending

Async syntax is not standard across native/js projects and in both cases a bit awkward for non-ocaml devs. Currently this is reasonml most voted issue in their GitHub repo so hopefully, there's news soon.
Comment

Pro
 Uses established compiler technology from Ocaml with a tweaked syntax that leans more towards Javascript

Comment

Pro
 Uses established compiler technology from Ocaml with a tweaked syntax that leans more towards Javascript

Comment

Con
 Large runtime

GHCJS supports the entire Haskell runtime, the Javascript it outputs tends to be quite large. This is in contrast to options such as Fay, which save some overhead by not supporting some features such as multi-threading.
Comment

Pro
 Full Stack Code Sharing

With a Haskell backend, GHCJS enables code sharing. In combination with the power of Haskell as a language, this enables an extremely tight integration of the client side with the server side, where all the communications take place in a type-safe manner and even transparently if desired.
Comment

Pro
 All of Haskell, with the same tools you're used to

No need to learn new syntax or semantics, and no need to install and learn a bunch of new tools - it's just GHC.
Comment

Pro
 Mature language and community

Comment

Pro
 Terse

Haskell is a very terse language, particularly due to its type inference. This means there's nothing to distract from the intent of the code, making it very readable. This is in sharp contrast to languages like Java, where skimming code requires learning which details can be ignored. Haskell's terseness also lends itself to very clear inline examples in textbooks, and makes it a pleasure to read through code even on a cellphone screen.
Comment

Pro
 Quick Feedback

It's often said that, in Haskell, if it compiles, it works. This short feedback loop can speed up learning process, by making it clear exactly when and where mistakes are made.
Comment

Pro
 Outputs efficient Javascript

Superior typed language.
Comment

Pro
 More language and compiler features, such as powerful macros

Comment

Pro
 Can also compile to C++, PHP, Python, Lua, Java

Comment

Pro
 Syntactic macros

Syntactic macros allow you to extend compiler features at the syntax tree step. Macros come into play after code is parsed into the abstract syntax tree, and macros allow you to transform it before the rest of the compilation completes. This provides for immense power, while at the same time scoping the extensibility at a level that is powerful, but well constrained.
Comment

Con
 Lack of learning resources

Haxe is only for people who already know ActionScript and have followed the project from the beginning. All the textbooks are out of date, as is the official documentation. There's no way to bring in new team members. Nov./2018 : This must be a very outdated CON, notable efforts have been made to make it more accessible. Some level of programming know-how is required to enter Haxe development, such is true. https://haxe.org/videos/
Comment

Pro
 Easy to learn when coming from Java or Javascript

Dart syntax compared to Java, JavaScript, Python, and C#.
Comment

Pro
 Easy to architecture and design large web/server applications

Dart contains all the wanted features to design and architecture large application as class, inheritance, interface, type.
Comment

Pro
 Good dependency management

Easy dependency management using pub.
Comment

Pro
 Better static analysis

Makes IDEs more effective, and finding bugs easier.
Comment

Pro
 Fast development cycle, no compilation needed

Thanks to Dartium, a browser running the dart VM, you can run dart code directly without compilation.
Comment

Pro
 Robust and comprehensive core library

Comment

Pro
 Worry-free, easy code refactoring

Dart's optionally typed language combined with the Dart sdk plugin for most modern IDEs makes refactoring easy! Make a change in one place and then just check out any error messages to see what else needs to be changed.
Comment

Pro
 Has healthy and strong, and even active, community

Dart community is healthy and strong, not very big compared to JavaScript's but sometimes active.
Comment

Pro
 Multiplatform : web, server, script, mobile (see flutter.io)

Comment

Pro
 Great async language support

Dart is a single threaded programming language. So if any piece of code blocks the execution of the program, the program practically freezes. To avoid this Dart makes use of asynchronous operations which let your program run without getting blocked. This is done through Future objects. A Future is an object which represent a means for getting a value at a certain point in the future. A function may invoke a Future and when that happens, two outcomes can be achieved: The function is unable to return a value, so it queues up work to be done and returns an uncompleted Future object. Or later when a value is available to be returned, the Future object completes with that value.
Comment

Pro
 Transpiled JavaScript code works on all browsers

In Dart many browser differences (subtle differences and also missing features) are abstracted away or polyfilled. When Dart is transpiled to JS the output works on all supported browsers. There is usually no need to load polyfills or to consider browser differences during development. No need for libraries like jQuery to make the same code work the same on all browsers.
Comment

Pro
 Easy prototyping

Dart has an optional type system which makes Dart a great language for prototyping. It encourages developers to gradually evolve their programs without worrying about types first.
Comment

Pro
 Can compile to efficient machine code

Dart was designed to be as expressive as possible. Ahead-of-time compilers can compile Dart code to efficient machine code. This is especially important when deploying to mobile where you don't want (or can't) use a JIT.
Comment

Pro
 Actively developed and maintained

Dart is actively developed and maintained by Google and used by the company, ensuring good project health (even if their plans for the language have changed slightly).
Comment

Pro
 Many platform targets

Dart targets the browser (after it's transpiled to JS), the server (Dart's VM can be run on Linux, Windows, OSX (Both on Intel and ARM architectures), Android and iOS (work in progress) and embedded systems via Dartino (support is experimental).
Comment

Pro
 A very clear well thought standard library

Out of the box, the developer gets core libraries to help with async, collections, strings, regexps, conversions, formats, file I/O, math, typed data, and more. This reduces the need to pull in various 3rd-party utilities and ensures that all Dart code looks and feels the same.
Comment

Pro
 A lot of tools are available to help in developing with Dart

Dart has a lot of tools available which help with developing Dart applications. Some examples of those tools include: pub - package and dependency management and build tool analyzer - static syntax analysis with linter, quick fixes, autocompletion support for easy IDE integration test - powerful and flexible testing framework and test runner dev_compiler - generate reusable JS instead of tree-shaken minified JS output (work in progress) dartfmt_ - source code formatter server-side VM observatory - a powerful tool for profiling and debugging running Dart code (for Dartium and Dart server code)
Comment

Pro
 No compile time in development

Dartium (Chromium derivative) is a browser with integrated Dart VM, which allows you to run and debug native Dart code during development for short edit-reload cycles. Only for testing on other browsers and deployment is transpiling to JS necessary.
Comment

Pro
 Great standard library

Dart includes a truly comprehensive core library, making it unnecessary to include disparate, external resources for basic functionalities Other than reducing the need to pull in various 3rd-party utilities this also ensures that all Dart code looks and feels the same. Out of the box, the developer gets core libraries to help with: async, collections, strings, regexps, conversions, formats, file I/O, math, typed data, and more.
Comment

Pro
 AngularDart 2.0 support

Comment

Pro
 Will be familiar to Java developers

The language will look familiar to Java developers, easing the learning curve. And yet, while it's similar, it has some nice syntax facilities to avoid common boilerplate code found in Java. Code is terser, yet readable.
Comment

Con
 Dart Dev Compiler is at a very early stage today after 33 months of the development

Very sought-after tool which (for reasons unknown) is not ready for real use. Despite the fact that it is developed by the professionals from Google on a reimbursable basis.
Comment

Con
 Community isn't very healthy

One or so posts a day on the mailing list; 800ish github stars vs Purescript's 2800 and elm's 3190. Not a lot of developer impetus.
Comment

Con
 Small community, little momentum

Comment

Pro
 Angular 2 as native framework

Comment

Con
 Large overhead of code compiled to Javascript

That makes it not suitable for small code injections or standalone webpages. Typically whole project has to be done in Dart.
Comment

Con
 Lack of libraries

In comparison to Java and/or Javascript the amount of libraries is very small.
Comment

Con
 No backwards compatibility with JavaScript

Even though you can use some JavaScript libraries together with Dart, it is not possible to execute JavaScript code in DartVM. This means JavaScript libraries would need to be refactored from scratch.
Comment

Con
 Not different enough from JavaScript to be worth the learning curve

While it's goals are noble to fix browser APIs it's feels like it's just JavaScript with types and the browser APIs moved all over.
Comment

Con
 No operator function overloading

Using the same operator with different argument types is not possible.
Comment

Con
 No typeclasses

This can cause some overhead.
Comment

Pro
 Small output

Fay produces smaller output than pure Haskell compilers such as GHCJS; It does not need to include the whole Haskell runtime, as it drops support for features such as multi-threading, giving it fewer dependencies.
Comment

Pro
 Simple, flexible, hackable FFI

As with UHC, the FFI to Javascript works with printf-style format: max = ffi "Math.round(%1,%2)" This can simplify code needed to make calls to methods on objects, in contrast to e.g., Purescript's FFI, which requires that methods be wrapped in Javascript. Similarly to UHC, Fay also supports the use of %*, for javascript functions with arbitrary numbers of parameters, such as concat, though they must expose an explicit number of parameters to Fay.
Comment

Pro
 Easy to set up, with packages available on Cabal

Fay is available on Cabal, as are Fay packages, so getting up and running is as simple as typing 'cabal install'. Happstack, Snap, and Yesod packages are available on Hackage, as are bindings for JQuery and Backbone.
Comment

Pro
 Subset of Haskell - nothing new to learn

Since Fay is a subset of Haskell - Lazy, statically typed, and pure by default. There's no new syntax to learn, and no surprises when it comes to the semantics of your code. This extends into function names as well - Fay programmers can use familiar functions such as putStrLn to output to the console, rather than Javascript-specific versions.
Comment

Pro
 Write server side and client side in the same language

Ceylon compiles to multiple backends: JavaScript, the Java Virtual Machine, and hopefully soon Dart as well. This allows you to write server-side and client-side code in the same language, reusing code between the two sides as appropriate.
Comment

Pro
 Good IDE support, fast compiler

Ceylon has its own SDK compiled to JS so it's really multi-platform.
Comment

Pro
 A great module system that interoperates with npm

Modularity is integrated into the language and tooling.
Comment

Pro
 Interoperation with native JavaScript

Even though it's primarily a statically-typed language, Ceylon has special language-level support for interoperation with dynamically typed languages like JavaScript.
Comment

Pro
 Huge language supports most everything

C++ is a large language with an even larger community and following. It has libraries for every kind of task that is possible to do with C++.
Comment

Pro
 Universal, portable, best complexity/efficiency trade-off

Used from browser and games to systems and compilers, too many things been made and working.
Comment

Pro
 Interacts seamlessly with other JavaScript libraries

Comment

Pro
 Works in normal flow with webpack and babel

Comment

Pro
 Works directly on F# source code

No compilation to .NET bytecode needed.
Comment

Pro
 It is mature and proven

Not vaporware or a 0.x version.
Comment

Pro
 Works directly on F# source code, no compilation to .NET bytecode needed

Comment

Pro
 JavaScript interop

Call JavaScript APIs and libraries.
Comment

Pro
 Use existing .NET libraries

Allows to use .NET Standard libraries.
Comment

Pro
 Free and open source

Comment

Pro
 Implements a mature language

In contrast to other options, Scala.js is a compiler plugin for an already existing and mature language: Scala. As such, it benefits automatically from the existing compiler, from the language design choices made for Scala, which exists and is established in the industry since years.
Comment

Pro
 Easy, type-safe, interop with JavaScript

The JavaScript-interop of Scala.js is very direct and lightweight.
Comment

Pro
 Crossbuilding

Keeps your client and server sources in sync.
Comment

Pro
 Excellent tooling (IDE) support

The same good and mature tooling that can be used for Scala can be used for Scala.js out of the box (code-completion, refactoring, immediate feedback, etc.).
Comment

Pro
 Extensive standard libraries

Scala.js implements most of the Scala standard library and many parts of the Java one. Among others, it supports Scala's rich collection library.
Comment

Pro
 Type inference

Scala offers type inference, which, while giving the same safety as Java's type system, allows programmers to focus on the code itself, rather than on updating type annotations.
Comment

Pro
 Immutable values

The immutable values make it perfect for working with concurrency.
Comment

Pro
 The strength of Scala on the server

The strength of Scala (JVM) on the server can not be underestimated, and is probably superior to any other choice listed here (where applicable; many have no server-side equivalent). Being able to use such a powerful language (and ecosystem) on the server AND on the client, and sharing code between the two, is a big advantage.
Comment

Pro
 Multiparadigm

Scala supports both Functional and Object Oriented styles of programming. Beginners can learn both paradigms without having to learn a new language, and experts can switch between the two according to what best suits their needs at the time.
Comment

Pro
 Dead-code elimination

Scala.js performs dead-code elimination out of the box (when running in the "fullOpts" mode).
Comment

Pro
 Incremental compilation

Through SBT, Scala.js supports incremental compilation out of the box. That is: SBT automatically picks-up the changes (think "watch" in other tools) and only recompiles what is needed. This makes the development cycle fast and very pleasant to work with.
Comment

Pro
 Simple build system compared to Javascript

While SBT is arguably not as simple as Maven, it beats the chaos of the JavaScript build ecosystem.
Comment

Con
 Always one File result

You produce one big file that is hard to split to smaller one (this is one of core decisions that gives you a lot of opportunities but it cannot be changed in future). If You starts with it, you ends up with one file.
Comment

Con
 A complex language with a lot of incidental complexity that results in significant mental overhead

Comment

Con
 Can be intimidating for beginners

Scala is an industrial language. It brings functional programming to the JVM. All books/tutorials cover friendly aspects of Scala, but there are corners of the language that one can wander into that are not friendly to beginners.
Comment

Pro
 Macros

Because Scala.js is a plugin to the Scala compiler, the whole power of the Scala language is available at compile-time. Which includes macros. Very expressive things can be done, in a type-safe way, which are difficult or impossible in other languages.
Comment

Con
 No support for Language Extensions

No support for things like Arrow Syntax - this is particularly a disadvantage when compared to options like Elm (which was designed around good syntax for Arrowized FRP), if you're looking to do Functional Reactive front-end development.
Comment

Pro
 It's just Haskell

No need to learn any new semantics, it's just a switch to a different compiler.
Comment

Pro
 Flexible FFI

UHC uses a printf-like syntax for its FFI, which is flexible enough to minimize the need for wrapper functions, when, e.g., calling methods on objects. It also supports %*, for working with functions that take arbitrary parameters, such as concat. UHC also has support for wrapper imports and dynamic imports, for passing Haskell functions as callbacks to Javascript, or dealing with curried Javascript functions, respectively.
Comment

Pro
 Several Platforms to use the web stack and JS to create multi-platform apps

Opens the door to native application development as well as just websites. Use with React Native, Weex or Quasar (Vue), PhoneGap or Cordova, NativeScript... (etc) to build native apps. Use mostly the same code base for multi-platform and web.
Comment

Pro
 Prototype based Object Oriented System

Being object oriented, it supports the predominate and powerful programming approach. Being prototype based, it provides an intuitive approach to OOP. Whereas other popular languages use classes, which focus on thinking in the abstract, Javascript's prototypes allow you to focus on thinking in the concrete. For example, in a prototypical language, you think of a rectangle, and define it. You now have a rectangle. Let's say you want a red rectangle, you copy the rectangle and give it the property red. Want a blue one? Copy rectangle again give it a blue. Big blue rectangle? Copy blue rectangle and make it big. In a class-based language, first you describe a rectangle, describe a red rectangle as a type of rectangle, describe blue and big blue rectangles, and now that you have described them, you must create instances of them, and only then do you have the rectangles. Essentially: Classes are factories for objects, prototypes are objects themselves, and the latter method was created to be more intuitive, which is particularly advantageous to beginners.
Comment

Pro
 Modern ESNext is far better than the JS of days past

Modern JS has made great strides, and can be targerted to older (or non-standard) browsers using Babel. There are new language constructs that can make programming in JS comfortable.; e.g.: async / await ( <3 ).
Comment

Pro
 Integrates very well with UE4

Coding an immersive 3D game can retain the attention of new programmers. ncsoft/Unreal.js.
Comment

Pro
 Can be very simple (teachable)

By setting a few ground-rules (effectively coding in a subset of JS), JS is one of the simplest languages to learn (requiring very few must-learn prerequisite concepts).
Comment

Pro
 JSON is native to JS

JSON is arguably a "must-learn". With JS, that's one less additional syntax to learn.
Comment

Pro
 Atwood's Law "Any application that can be written in JavaScript, will eventually be written in JavaScript."

May also be a con.
Comment

Pro
 Great tools for development

Flow, JSHint/ESLint, Babel, npm, etc.
Comment

Pro
 High demand for JavaScript developers

If you're looking for a career as a developer, JavaScript is the place to focus your attention. There is a huge demand for good developers especially in frameworks such as React and Angular.
Comment

Pro
 Complete dev stack can be run online

With codepen.io and other prototyping tools, you can learn Javascript from a mobile device. You don't even need a computer. It can be learned from an internet cafe or public library.
Comment

Pro
 Very good debugger

Has a built in debugger with break points, watches that work on local values, and a console that you can use to edit anything at any time. Both in the browser (eg: Chrome), and server (eg: Nodejs).
Comment

Pro
 C-like syntax

After learning Javascript, you will feel at home in other languages as C-like syntax is very common.
Comment

Pro
 Instant gratification

While it's easy to argue that Python will give you instant gratification, JavaScript is far better in this regard. Make a small change to a page and it's immediately visible in the browser. You can throw in a JavaScript library like jQuery with minimal fuss.
Comment

Pro
 Massive ecosystem

JavaScript has one of the largest programming ecosystems, as shown by the being the most popular language for projects on GitHub. As there are so many projects written in JavaScript there are lots of libraries available to build off of and many of them are written to be easy to use and integrate into other projects. There are also lots of resources available for learning JavaScript. Other than traditional tutorials, language learning sites such as Codecademy have JavaScript courses. The Mozilla Developer Database also serves as a great resource for learning about the standard libraries built into JavaScript.
Comment

Pro
 Easy to build an application

By using the UI capabilities in HTML and CSS you can develop substantial applications with graphical interfaces more quickly and with less effort than in other languages which would require you to learn a windowing library. Building a useful application is one of the best ways to learn a new language and because of the low learning curve for creating applications you can create more substatial programs and learn more practical programming priciple faster.
Comment

Pro
 First-class functions with lexical closures

While certainly not the only language with these features, this pro alone is so powerful that it compensates for most of JavaScript's problems. You'll learn to use closures and higher-order functions well in JavaScript, because you have to. And then you can generalize this knowledge to any other language that has these, and the good ones do.
Comment

Pro
 Runs on both the browser and the server

With Node.js, it is now possible to run JavaScript as a web server. This would allow you to be able to create server based applications sooner than would if you had to learn a separate programming language as well for server side code. As JavaScript is the only language supported by web browsers it puts it in the unique situation of being the only programming language that's available on both the client side and server side.
Comment

Pro
 No installation required

If you run a web browser you already have JavaScript installed and can get started right away. Modern browsers such as Chrome also have very powerful programming consoles built into them. Aside from the browser console, you can also use online Javascript playgrounds such as JS Bin and JS Fiddle. Even from a tablet.
Comment

Pro
 Required for web development

If you are looking to create web projects, you will have to learn Javascript in order to develop the client side code. If you learn the foundations of programming in JavaScript you can reapply that education later in building web applications.
Comment

Pro
 Speed (most implementations)

JS/ES is in the running for the fastest interpreted language given the optimizations and JIT integration of popular implementations. On the other hand, it fails utterly when compared with compiled (to native or VM code) languages.
Comment

Con
 Limited community

There's limited community, because of being a fairly recent solution: it's currently in Beta.
Comment

Pro
 Interoperates with native Javascript code

Naturally access Javascript object fields and call function/methods
Comment

Pro
 Implements almost full Smalltalk

Limitations: Limited numeric stack No become: Strings/Symbols/Characters all strings Limited reflection support
Comment

Pro
 Develop/debug/refactor in Pharo with rich IDE and seamlessly deploy in Javascript

Virtually any Smalltalk class can be exported as part of the solution. Code running in Pharo can access the Javascript/DOM environment and then move over once all is functioning. The only non-portable code are primitive methods without Smalltalk fallback code, but those are mostly already implemented.
Comment

Pro
 Interactive development for multiple browsers plus NodeJS

Comment

Pro
 Clean, concise syntax

Code in CoffeeScript is much cleaner than in ES5, and new ES6+ features didn't change that, even though ES6 imported some ideas of CoffeeScript.
Comment

Pro
 Compiles to readable Javascript

Resulting JS code size is comparable to CoffeeScript, overhead is tiny.
Comment

Pro
 Supports new ES6+ features

Even though CoffeeScript originally was aiming compilation of all it's fanciness into strict ES3, it supports ES6+ generators and modules.
Comment

Pro
 Everything is an expression

Even for loops and if statements. For example, to get mapped array, you don't have to use any Array methods, just the language features: food = ( stuff for stuff in fridge when stuff.isEatable() )
Comment

Pro
 Off-side rule

Blocks are defined by their indentation, similar to Python.
Comment

Pro
 Lightweight syntax

Javascript is a very verbose language so CoffeeScript's goal is to lighten it to make it less tedious. Various design choices are built around making CoffeeScript more terse with things like optional parenthesis in function calls, cleaner function declarations, no curly braces, and significant white space. Because Javascript can get pretty deeply nested at times, having a lightweight syntax helps with readability. The result is a language with a minimalistic syntax with lots of syntax sugar.
Comment

Pro
 Syntax for humans, not compilers.

CoffeeScript adds syntax that is not only more terse than javascript, smoothing over the rough edges, but also enforces a more human readable syntax to the point where a non-programmer can understand some logic. Many programmers that are not use to coffeescripts syntax will find it foreign if they don't read the single page API, but generally it is quick to understand and although self documenting code is a myth coffeescript is definitely very close. if hungry then eat food for food in fridge when food isnt poison and it isnt bedtime Seems a lot more concise and comprehensible to many programmers and most others than the alternative syntax: var food, i, len; if (hungry) { for (i = 0, len = fridge.length; i < len; i++) { food = fridge[i]; if (food !== poison && it !== bedtime) { eat(food); } } }
Comment

Pro
 It's just JavaScript

The golden rule of CoffeeScript is: "It's just JavaScript". The code compiles one-to-one into the equivalent JS, and there is no interpretation at runtime. You can use any existing JavaScript library seamlessly from CoffeeScript (and vice-versa). The compiled output is readable and pretty-printed, passes through JavaScript Lint without warnings, will work in every JavaScript runtime, and tends to run as fast or faster than the equivalent handwritten JavaScript.
Comment

Pro
 Maintainable code

Easy to read and easy to work with structures like list.
Comment

Pro
 Significant whitespace

Having indention-based code blocks is particularly helpful in JavaScript because of its functional callback based nature. In JavaScript you find yourself writing functions within object and passing functions to functions. You can find statements ending with a confusing melange of braces like )}})}). With significant whitespace, most of the needs for braces go away.
Comment

Con
 Codebase is barely actively maintained anymore

Comment

Con
 Codebase is barely actively maintained anymore

Comment

Con
 Terse syntax can lead to ambiguity

It can sometimes be hard to be sure of what CoffeeScript will compile down to because of the optional parentheses and significant white spacing. Over multiple lines the same statement can be written in many different ways, and it's not always clear what the intended interpretation is. For example: foo bar and hello world can compile to either: foo(bar) && hello(world) foo(bar && hello(world))
Comment

Con
 Initializing a variable and assigning it are essentially the same thing

Because of how variables are initialized and reassigned in CoffeeScript, it becomes very easy to accidentally overwrite a variable as the codebase increases. As complexity increases, the only way to safely create a variable is by pressing Ctrl + F and by examining the current file to ensure that there's no conflict.
Comment

Con
 Not better enough, too many gotchas

Comment

Con
 Weak typing, as in JS

Although CoffeeScript introduces classes, all types are weak, as in JS.
Comment

Pro
 Introduces classes and class inheritance

The most disputable missing feature of Javascript is lack of classes. CoffeeScript solves the issue.
Comment

Pro
 Everything is typed

Everything is typed using a simple type system.
Comment

Pro
 Good error support

200+ unique error messages to help you on the way.
Comment

Pro
 HTML and CSS integration

HTML can be written with minimal differences scoped. CSS can be written for elements in components.
Comment

Pro
 Easy to learn and write

Everything is an expression.
Comment

Pro
 Constructs for synchronous and asynchronous

Constructs for synchronous and asynchronous computations.
Comment

Pro
 Writen in Crystal (Language)

Crystal is one of the best languages and elegant.
Comment

Pro
 Easily adoptable

Comment

Con
 Poor typescript support

Very basic typescript support.
Comment

Pro
 Able to statically type check using mypy

Comment

Pro
 Uses Python

Comment

Pro
 Transpiler rather than interpretor in javascript

There is less code to transfer.
Comment

Con
 Denial can be risky

Denial is a psychological defense mechanism in which confrontation with a problem or with a reality is avoided by denying the existence of the problem or reality. Refusing to acknowledge the fact that javascript is a dysfunctional language puts developers at risk of wasting time and resources on non scalable and non maintainable projects.
Comment

Con
 Poor documentation

Comment

Con
 No longer open to the community

While it's still open source, the project maintainer moved off of github and onto a personal lolg.it domain for strange political reasons. Unfortunately, there doesn't seem to be any way to register an account on that site, since it never sends the confirmation email. This limits participation to only those few who already have an account.
Comment

Con
 Website abandoned

The project doesn't maintain their website for some reason. The latest Amber version on lolg.it is at least 0.18.4, but the amber-lang.net site still shows 0.14.16.
Comment

Pro
 Super super fast DOM implementation

The ‘imperative’ DOM from Imba is factors of magnitudes faster than most current virtual DOMs.
Comment

Pro
 Transpiles to very readable Javascript

Comment

Pro
 React inspired approach

Comment

Pro
 Close alignment between language and DOM

The DOM is a first class citizen of Imba and that allows for short elegant interaction.
Comment

Pro
 Ruby inspired syntax

Comment

Con
 Still a young language

But looks very promising.
Comment

Pro
 Great for small—likely published—reusable libraries

Very extendable as a single-import base layer for visual controls and probably also something like a react-redux Provider.
Comment

Con
 Not well-suited for application wiring

Having to serialize/deserialize data between components is not convenient. You'll probably still need a [light/simple] framework. Some things are still quite nice, such as using the light DOM -- think <option> with <select> and <datalist>.
Comment

Pro
 Works with any framework

Less recreation of the wheel and fewer wrappers.
Comment

Pro
 Fallback styling when not yet defined

Before a component's script defines the custom element—either as the page is loading or with JavaScript disabled—it can be temporarily styled via :not(:defined). This may prevent the need for SSR.
Comment

Pro
 Customizable templates via custom-recognized "slots"

slot="name" and <slot name="name"> for customizing a component's HTML in specific areas of its shadow DOM. Also fallbacks when not defined.
Comment

Pro
 Stylable via custom-exposed "parts"

::part(name) pseudo-element for styling elements within a component's shadow DOM.
Comment

Con
 SSR is potentially more difficult

…if you need more than CSS' :not(:defined), that is. Check out this video to see how the creator of SkateJS handled it: https://www.youtube.com/watch?v=yT-EsESAmgA
Comment

Pro
 It isn't just another Python-to-JS compiler, it is mix of the best of both languages

You write it like Python, but the output is clear JS-code as if it was written in pure JS. If you like JQuery or other JS-libs - just use it without any adaptors: foo = $('#foo') or even $foo = $('#foo'). It makes understanding and using prototypes easier, and offers an alternative to @decorator.
Comment

Pro
 Efficient

WebAssembly is encoded in time efficient format.
Comment

Pro
 Fast

WebAssembly runs fast.
Comment

Pro
 Open source

It can be accessed in a textual format for debugging, testing, optimizing, and other purposes.
Comment

Con
 Does not support garbage collection out of the box

It's more difficult to compile from the usual web languages like Javascript or Elm to WebAssembly.
Comment

Pro
 Robust subset of features

Comment

Con
 Does not use Haskell syntax

Comment

Pro
 Fast

The compiled code of asm.js can run really fast thanks to it being restricted in how it works.
Comment

Pro
 Easy debugging with source maps

Comment

Pro
 Compiler optimization

For better performance.
Comment

Pro
 Catches bugs at compile-time because of its static type system

Comment

Con
 Undefined

JavaScript's fundamental flaw. ECMAScript still has it. Instead of crashing at or near the problem with a helpful error message like any sane dynamically-typed language, it just returns a garbage undefined value until it finally crashes in some other unhelpful location. Or worse, it doesn't crash at all and just doesn't work.
Comment

Pro
 New features make JavaScript a bit less painful to use

Comment

Con
 Even more complicated

One of JavaScript's primary problems is that it's too complicated. Adding even more features is not going to fix that.
Comment
undefinedurl nextprice drop