4 ms·
What do you want to do with the language?: Here are some choices I think are interesting as new languages: Elixir : interpreted / scalability / concurrency /
by rdtsc 11y ago
What do you want to do with the language?:
Here are some choices I think are interesting as new languages:
Elixir : interpreted / scalability / concurrency / fault tolerance/ friendly community
Rust : compiled / close to C speed / memory safety / concurrency
TypeScript : compiles to Javascript but with types / runs in the browser
Elm : compiles to Javascrtipt / functional / runs in the browser
- praveenster 11y agoYou can probably include Go alongside Rust.
- zeckalpha 11y agoOr TypeScript? Rust and Go are not much alike.
- krisdol 11y agoI'm not even remotely a front end guy but Elm looks so interesting. I really want to play with it
- ihsw 11y agoIt should be noted that there are some caveats to TypeScript, namely that it's type-safety is only compile-time and not at run-time. It is best-effort type-safety. That said, the edge cases are few and far between. TS is a fantastic language to work with.
- djur 11y agoI think the issue you're mentioning isn't so much that TS only enforces type safety at compile time, because that's true of Haskell, OCaml, C++, etc. as well, but that by its nature it can't enforce any type contracts with the large quantity of dynamically-typed JavaScript you're probably going to be dealing with. Of course, this is also an issue when safe Haskell, OCaml, etc. code interacts with compiled C code at runtime as well.