> Error resilience, crash resistance: When things go wrong, Blackjack will make an effort to respect your time as a user and not lose your work. Errors will be clearly communicated and fixing any bugs leading to a crash will take the highest priority.

I for one appreciate this and I wish every tool was designed with this as a clear objective. Thank you!

    PS I:\Projects\blackjack> git submodule update --init --recursive
 Submodule 'rend3' (git@github.com:setzer22/rend3.git) registered for path 'rend3'
    Cloning into 'I:/Unity Projects/blackjack/rend3'...
    git@github.com: Permission denied (publickey).
    fatal: Could not read from remote repository.

    Please make sure you have the correct access rights
    and the repository exists.

Git submodules are a PITA

To be honest, I'd much prefer to wait for a binary to try this out. I'm not (currently) a Rust developer and any project that requires compiling in an unfamiliar environment usually translates to "wave goodbye to your afternoon".

There's a ton of GAN projects I'd love to try out but the hellscape that is CUDA and Tensorflow means that I stopped bothering unless I'm really keen.

Running into the same issue on linux. No clue what's causing it, since the github repo for rend3 seems to be publicly accessible without any issues..

Edit: I managed to fix it by editing .gitmodules (changing the url line to `url = https://github.com/setzer22/rend3.git`) and then running `git submodule sync; git submodule update --init --recursive`

Likely you don't have SSH configured properly for use with GitHub -- you can either configure it or switch the subproject URL from SSH to HTTPS

As the sibling comment said, the problem is that the dev used the SSH form which requires me to authenticate with the repo (i.e. I need to be given explicit permission) whereas for public read access you want git submodule to use HTTPS

Very easy to forget this when you're the dev and you already have access. Is there a way to have both? How does one say "I want submodules to authenticate people where possible but allow public read-only access if not"?

You can clone any public repo through SSH, though -- I do that all the time. You still need to authenticate with GitHub properly though, unlike HTTPS where you can clone anonymously. Is your public key added to your GitHub profile?

Why the node-based interface? Doesn't this get overwhelming (too many nodes) when you do a serious project?

How about a purely textual approach?

Nodes offer a middle ground between pure text and purely visual.

To elaborate a little: in my experience code is great when you know exactly what you want, but nodes are better for exploration.