futhark VS koka

Why Futhark? (futhark-lang.org)

There is no on-going work to support Metal apart from the work done by Miles. There's an old issue about it: https://github.com/diku-dk/futhark/issues/853#issuecomment-5...

Functional programming can be a great way to handle parallel programming in a sane way. See the Futhark language [1], for example, that accepts high-level constructs like map and convert them to the appropriate machine code, either on the CPU or the GPU.

[1] https://futhark-lang.org/

Futhark - use a functional language to program the gpu

You might want to look into Futhark, although it's mainly designed for writing GPU code.

Futhark https://futhark-lang.org/

This post by the Koka-author is an update about what's currently being worked on: https://github.com/koka-lang/koka/discussions/339

Some programming language like JS, use path-based imports, that's not good for making a stabel API.

See https://api-extractor.com/pages/setup/configure_rollup/#:~:text=(The%20API%20Extractor,with%20that%20effort.)

And https://github.com/koka-lang/koka/issues/31#issuecomment-1482200826

It also offers a great Inversion of Control mechanism where everything is customisable, and, unlike Capability Objects, AESs also offer compatibility with type inference (you can pass functions doing IO to map, and it Just Works(TM)) and first-class control over stack frames (because really a continuation function is just some stack frames, which you can manually move to the heap if you want a closure; which means async is an effect!). It also is composable in ways Monads are not.

Koka and other languages implementing Algebraic Effect Systems make everything a user-defined case of coroutines: async is just another effect/Monadic type. Zig does something similar by having first class stack frames, making all function calls possibly asynchronous.

Super interesting, there is a proposal to add this to JavaScript and several languages that use this, unison, koka & eff. I had no idea this was even a thing!

Koka, already cited in this thread, early 2010s. Koka's first claim to fame was a usable effect system (at the type were, basically, effect systems were not usable in practice; in fact few languages have managed to do as well as Koka since). Now its author is working on cool implementation strategies for functional languages as well.

I'm a software engineer with 3 years of professional experience. I worked for 2 years at Microsoft on Azure Compute and now work at Google, working on improving Google search. I am the sole maintainer of the popular open-source library microlens with 80k downloads. I've also contributed to the Koka programming language developed at Microsoft Research.

By implementing all of those optimizations in the Koka programming language, they achieved GC overhead much less and execution time faster than the other languages including OCaml, Haskell, and even C++ in several algorithms and data structures that frequently keep common sub-structures of them, such as red-black trees. For more information, see the latest version of the paper.