roc VS kuroko

Their FAQ is an eminently reasonable breakdown of their choices:

https://github.com/roc-lang/roc/blob/main/FAQ.md

I don't fully agree with all of the reasoning, but it's a reasonable position to stake.

If you forget what parametrisation and functions are, then Roc's modules look like they actually do that.

Reminds me of: https://github.com/roc-lang/roc/blob/main/FAQ.md#why-doesnt-...

> How would a user interface written in a functional language look?

Maybe you're not aware of Elm?

https://elm-lang.org

Elm is really functional, unlike the likes of React that are just partially, kind of functional.

There's an attempt at bringing Elm to the desktop, the Roc language... here's an UI example written in Roc:

https://github.com/roc-lang/roc/blob/main/examples/gui/hello...

What are your thoughts on the direct descendant, Roc? [0] I know it's pre v0.1 so maybe you don't have any, but as a fellow Elm lover it seems pretty compelling on the surface albeit less directly frontend-dev focused.

[0] https://github.com/roc-lang/roc

I might be misunderstanding something, but, for example, look at this "host"/platform: https://github.com/roc-lang/roc/blob/main/examples/cli/tui-platform/host.zig

You are not alone. The other day I was checking out a new programming language and the author rewrote the unsafe rust part to zig: https://github.com/roc-lang/roc/blob/main/FAQ.md#why-does-ro...

Check out Roc[0][1] by Richard Feldman; it's early-stages (perhaps earlier stages than Elm?) but from everything I've seen it looks a bit like a spiritual successor to Elm, though focused more on native applications (but still seems to have its sights set on webassembly support too)

[0] https://www.roc-lang.org

[1] https://github.com/roc-lang/roc

(kuroko)[https://github.com/kuroko-lang/kuroko] is basically Python, but C

Kuroko: Dialect of Python with explicit variable declaration and block scoping, with a lightweight and easy-to-embed bytecode compiler and interpreter.

I would say Kuroko makes more sense ;-P

Kuroko 1.3.0 gets a release candidate. Lots of big things since 1.2.5, like optimized method invocation, more operator overloads, better support for f-string expressions (format specs, =, faster constructions), a long type with my own bigint implementation (this was the last thing I was still regularly opening Python repls for, so a huge personal win). I also fixed a bunch of little things that have been nagging me, like the compiler can now compile expressions directly, which allowed me to remove the kludge that made the repl work previously. The WASM web repl also got some love with a port of the core of Hiwire from Pyodide, giving a very straightforward interface between JS and Kuroko in a browser - and I rebuilt the web IDE on it. I've also been working on a new compiler, which will hopefully form the basis of 2.0 - and this might be the last 1.x release (though I expect at least a few 1.3.x bug fix releases).

In case it's not clear, PonyOS is a joke reskin of my serious OS project, ToaruOS. PonyOS gets a new release every April 1st. All of the libraries and applications in ToaruOS are in-house things I built myself - the whole OS is "built from scratch". PonyOS adds ponysay, which is an external app originally written in Python - and in previous releases of PonyOS I shipped the Python version alongside a port of Python 3.6. This release, though, comes with a port to my own language, Kuroko, which is a dialect of Python - a lot of what went into building the PonyOS release this year was getting ponysay to work well.

Did this year's Advent of Code in Kuroko which sussed out some bugs and missing functionality. Better hashing for tuples, more builtins and methods on standard classes for improved compatibility with Python, general build cleanups. In the later problems, most suffering was caused by the GC, so I'd like to put more thought into collection strategies going forward.

Is it me you're looking for?