Samuel Lampa

@kwrobert So, I realize I should perhaps write up a few short notes on the design thinking for the current plans, which could be a starting point for new contributors...

> I was wondering what this IP stuff meant (Information Packet, right?). Yes, a slightly awkward bit of flow-based programming lingo. > So I can kind of imagine where this...

> Absolutely, I'm totally open to changing the name from "Resource" to "Executor", and I agree the term "Resource" feels somewhat ambiguous. Now that we're on the same page about...

@kwrobert And, to clarify, refactoring to enable custom executors, should not clash too much with my work on refactoring the IPs, as we now figured these are different concepts :slightly_smiling_face:...

JFYI: Just found in my notebook now I have some sketches on an API for this, (from January or so I think :P): Something like: ```go helloWorld := myWorkflow.NewProc("hello_world", "echo...

Many thanks for the detail input @kwrobert ! Being able to distribute work among multiple executors would indeed be cool! I still think one needs the ability to quickly switch...

There's now more than one Go-based Jupyter kernels: - [gophernotes](https://github.com/gopherdata/gophernotes) - [lgo](https://github.com/yunabe/lgo)

Partly addressed now in 3974b3cbae20e1efb25d42d2e34927f562b2bdb9 , with new place holder: ```go myProc := wf.NewProc("myproc", "echo $(cat {i:infile}) {k:infile.gene} > {o:outfile}") ``` (We haven't yet renamed from "Keys" to "Tags"). This...

> (We haven't yet renamed from "Keys" to "Tags"). Now it is renamed, so the pattern is also `{:t:..}` instead: ```go myProc := wf.NewProc("myproc", "echo $(cat {i:infile}) {t:infile.gene} > {o:outfile}")...

Hi again @ASVBPREAUBV and again, an excellent idea ... been annoyed by these multiple times as well :D