I’m not sure why people are assuming I’m pushing for distributed OOP here. Wool is completely unopinionated about how you decide to architect your application - that’s the entire point.

So if you wanted to scale, say, a hyperparameter search across a cluster, what would you prefer?

It’s a good point. The Argo workflow/event set up I’m referencing isn’t for everything. It does distribute ELT pipelines rather well but I am not sure it was designed with that particular usecase in mind. Thank you!

Wasn’t previously aware of this opinion, but having read it, I can tell you I’m not actually committing this fallacy within the framework- I’m not forcing anyone into making their instance methods RPCs- I leave that up to my users. They are grown adults (presumably) and can commit whichever fallacies they desire.

Not on my watch

You mean the cadence where everything is presented in threes? Yeah I hate it too, but beats paying some blogger to do it

> You mean the cadence where everything is presented in threes? Yeah I hate it too, but beats paying some blogger to do it

You could also use your own words instead of an LLM. Would have been more interesting.

I think LLMs are incredible tools that I will continue to use unapologetically, but I’m also very particular and not going to be putting my name to AI slop. Those are my genuine thoughts on the matter, they just happened to be cleaned up by an automated stochastic parrot.

just disclose please. i churn on non-disclosed ai generated content as a matter of principle. i don't necessarily churn on other variants

Fair enough

Sure, my argument is that those concerns should be composable with the distribution layer, not defined by it. There are plenty of different ways to pass data across a network or between machines, I'm not going to reinvent them all. There are also plenty of ways to manage non-transient errors (and very app-specific), I'm not going to implement them all. I'm also not assuming you need or want object persistence and replayability of your workflows. If you do, then use the right tool for the job.

I agree

Yeah but... who does that?

To be clear, not all of your coroutines become distributed. You explicitly declare what you want executed remotely, and you'll probably want your workers running in a VPC - it's just a nifty way of scaling your app horizontally without sinking too much effort into how you choose to define your distribution boundaries. It wouldn't be any different than scaling any other service horizontally using something like Kubernetes (which is probably how you'd manage wool workers as well).

But seriously, I just wanted to have an easy way to parallelize my projects without a bunch of slow, bloated, boilerplate ridden frameworks, and I'm having fun building it. And I must not be the only to have had this desire considering there's way more than one solution to this problem out there already, so f*k it.

Fun is what its all about. You don't a reason other than that.