Introducing the IBM Swift Sandbox

Re:Introducing the IBM Swift Sandbox by rdtsc on Friday December 04, 2015 @12:47PM (#10677791)

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

[ Parent | on HN ]

Re:Introducing the IBM Swift Sandbox by krisdol on Friday December 04, 2015 @01:38PM (#10678136)

I'm not even remotely a front end guy but Elm looks so interesting. I really want to play with it

[ Parent | on HN ]

Re:Introducing the IBM Swift Sandbox by praveenster on Friday December 04, 2015 @01:02PM (#10677894)

You can probably include Go alongside Rust.

[ Parent | on HN ]

Re:Introducing the IBM Swift Sandbox by zeckalpha on Friday December 04, 2015 @08:32PM (#10680386)

Or TypeScript? Rust and Go are not much alike.

[ Parent | on HN ]

Re:Introducing the IBM Swift Sandbox by ihsw on Friday December 04, 2015 @02:27PM (#10678480)

It 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.

[ Parent | on HN ]

Re:Introducing the IBM Swift Sandbox by djur on Friday December 04, 2015 @04:12PM (#10679161)

I 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.

[ Parent | on HN ]