I don't really know Windows 10 but apparently it's available on ARM processors. The version available on the website will only work on x86-64 processors. Could that be the reason why it doesn't work?

Don't think so, I am running 32-bit Windows on a x64-based processor.

Ideally, Skov would need an integrated version control system that understands the visual code.

But now, all you can do is export your code to text files (Ctrl+S) and use traditional text-based diff/merge/version control tools.

This is the right answer, at least for visual dataflow. It should be done by diff/merge of graphs, displayed visually, not by converting it into a text-based format and using something like git, Perforce, or cvs. Dataflow can be expressed textually, but you'd have a hard time following the code.

No, I just looked at the translations for "tree" and "forest" in many languages and I chose the one I preferred.

I have just tried it on my older Mac that still runs El Capitan. I downloaded the image from the website, opened it and copied the folder to the desktop. I had the same error as you ("Skov is damaged and can't be opened"). Then I went to System Preferences > Security and Confidentiality and I saw that "Allow applications downloaded from" was set to "Mac App Store and identified developers". I selected "Anywhere" and tried again: it worked. So the problem was really Gatekeeper.

Shouldn't right click and "Open" work? It doesn't work and I don't know if I want to disable gatekeeper.

Other people have helped me identify the cause of the problem (quarantine attribute on the app folder). I've uploaded a new dmg image. If you try to download it again it should work this time (I hope).

Doesn't work. Same problem.

But thanks for the tip about quarantine. I removed it from the folder and app with xattr and now I can start it.

(1) & (2) The code is compiled using the Factor compiler so it really works like Factor (3) Dynamically typed, type errors will be caught at runtime (4) You use "while" and "until", you can see an example in the last screenshot in the web page (5) There is a lambda. There are several examples of this on the web page, including a lambda inside a lambda

It's quite different then, despite the superficial similarities.

(1) Full Metal Jacket is explicitly dataflow - that's how the interpreter works. How to compile it (and to what) is an open problem for me, but there are a number of options. I won't release it until I have a working compiler.

(2) It's not a visual version of any existing text-based language. It is implemented in Lisp, and you can mix the two languages, but it's nothing like Lisp.

(3) It's very strongly statically typed, with type inference. Type errors are prevented by the editor. Run time errors are simply unacceptable.

(4) Iteration is done two different ways: using a feedback mechanism, and using emitters and collectors.

(5) Lambdas, including non-local capture of values, are built into the language.

More information here, including papers and tutorials: http://web.onetel.com/~hibou/fmj/FMJ.html