@hrefna right! And like tutorial sites are like, here is this simplified thing that you don't want to learn. We learn best by seeing how others do it. Sidenote: good gods software *engineers* are scary. build systems and test cases and dependency management and release tagging and shit, where we're from you're lucky if you get a `cc -o dothething -I./src/common -I./src/thinglib thinglib_core.c thinglib_tui.c dothething.c dothething_plugins.c`

@hrefna we're a software hacker in the 1980s unix sense. It plays right hell with our atempt to get a job, too

@12 My first language was hypertalk, which is a bizarre language but also a very cool one.

It's _really_ hard to shake early paradigms with languages. I'm generally of the view that languages are easy, but learning the ecosystem is difficult and learning paradigms is difficult

I've seen programmers with decades of experience segfault entirely when running into a different paradigm.

So you aren't alone in that, and in this case they picked up none of the things that makes that pattern… work.

@12 Oh, and one more note on this, in the languages with operator overloading this becomes downright _clean_. It becomes something like:

RunSomething >>| do_something_with_result >>| do_another_thing >>= deal_with_errors |> add_callback

Now it can even be concurrent and still nice and clean, with no changes to the code.

Which is why a lot of people like this pattern, but it does involve a different way of thinking, and I'd argue its absence from go is keenly felt.