listudy VS go-plugin

It comes with experience. There is a website called listudy.org that has a section called “Blind Tactics” that might help with visualization.

Listudy: Memorise openings with spaced repetition. Chess Endgame Training Chessercise: Practice chess with YouTube. Chess Madra: Build and practise an opening repertoire. Aimchess: Learn your strengths and weaknesses.

If you are trying to practice a certain opening, I would highly recommend listudy.org just to build that spaced repetition in your head.

I find https://listudy.org very useful for drilling lines. I don't see it mentioned often, but it allows you to import any lichess study (selfmade or other) into it and it'll pick a random line that's up to you to correctly play out until the end. Works very well if you do it enough

I use private Lichess Studies to store/build my repertoire. Start "choosing" your preferred responses to various opening moves and store them there. Start 1 move deep at a time and branch out slowly. At low level of play it's actually better to go just a few moves deep and have some canned responses to common bad moves from your opponents. You can import your lichess study into listudy.org which turns your saved opening prep into spaced repetition exercises to practice.

listudy.org

Second, you can check out https://listudy.org which can do this with lichess studies.

I am looking forward to a mix of both - I am hoping to add a concept called "operator" which would be a go-plugin [1], just like terraform providers, but build backends. So, someone would be able to, say, write a Slack plugin (in Go, or anything over RPC) which sends a message once a build is complete - like Jenkins/GitHub actions, or just scripts that we can reuse like GitLab CI through `modules`.

Perhaps a new registry where we can push custom modules and providers (operators in this case), I'm curious to know about if we have any existing implementations we could reuse for the registry.

[1]: https://github.com/hashicorp/go-plugin

I'd recommend looking into a different approach for plugins such as hashicorp/go-plugin (which uses multiple process PIDs and RPC communication between them) or traefik/yaegi (which implements a Go-compatible scripting language that can be interpreted at runtime and which still supports most Go modules).

You'll never fully protect your code from someone who's dead-set on reverse-engineering it, however, you can use https://github.com/hashicorp/go-plugin or a similar RPC technique, which will let you ship binary plugins and will also be less fragile and janky compared to something made with `-buildmode=plugin`.

The plugin system that hashicorp uses for all their projects works very well. It's essentially a local RPC implementation. https://github.com/hashicorp/go-plugin

can you try older go-plugin versions? The only major change in v1.4.4 was a bugfix for automtls. https://github.com/hashicorp/go-plugin/blob/master/CHANGELOG.md