rvitorper

Nice. Do you have any resources on the latter? I'd really like to see how much easier is a data driver state machine

Hey, thanks a lot for the comment! The supervisor I added - which is a super simple one - ticks using the time.Ticker, which I assume only works with regular intervals. I think adding the built-in exponential backoff would be a nice thing to add, maybe making it go back to the node in a subtick manner. I haven't tested a super large tree or a combination thereof, but I think if the nodes can behave properly with respect to waiting some IO, it can definitely handle quite a large tree. It would be nice to add the capability to handle several trees, though. What do you think?

Hey, thanks a lot for commenting. That seems like a nice way to encode state. Did you ever have issues with multiple states being activated at the same time? I'll take some time to explore the hierarchical state machine, as I haven't seen an example of this short of HTN. Making it data-driven seems a nice and easy way to tackle the complexity. I like that

Hey, thanks a lot for the comment. I'd love to see some code about the "express state machines as data". I always had a hard time with state machines, because every time I needed to add a new node, I had to reason about too many transitions, especially when the number of states was enormous. I like the BT structure because of the modularity, but it would be nice to see some other way to implement things - always a welcome addition. Regarding the BTs with channels, I'm very curious about it. Will check the article, for sure

Hey, thanks a lot for the comment. I was thinking about the parallel composite nodes and I was wondering what would make good additions to the project. What do you think? I was going to start implementing something like RequireAny and RequireAll. I was also wondering about the "parallel" side of these nodes. Does it mean they tick all children nodes or does it mean that I spawn one goroutine for each child in a wait group and wait? Would like to hear your thoughts

Somebody, somewhere tried to rollback something and it failed

Exactly

Amen, brother

It’s a bot responding. That much I can tell

Yes

I can’t unsee it either. Will try it later

Right?? Omg, I felt the same way!

They are still high on their power trip. They say creators will have an “opportunity” because creators “think YT might have made a mistake”. What a huge ass announcement

Makes sense. Thanks for the comment

Postgres. It was also a single instance, which made it significantly easier. But nice to know that this is an issue on SQL Server

Does anyone have performance issues with uuidv4? I worked with a db with 10s of billions of rows, no issues whatsoever. Would love to hear the mileage of fellow engineers

As an outsider, I have two questions: - why is Shopify kind of hated in the comments? - what is it DHH said?

Hoping for some context

I like it. Simple, easy, htmx and Flask, batteries-included. Exactly what I was looking for

I’ve heard of a major fintech in South America that stores all the client state on the backend. Millions of users daily and it works

Next.js is still missing lots of backend stuff. Background jobs, cron jobs, queues, etc.

Scala mentioned

I like Caddy. Good to see it evolve. Hope it works well

We all love a vendor lock-in, don’t we? Until it backstabs us and we go back to VMs

Looks premium, eco-responsible, powerful, just like the M4. And the M3. And the one before. Does anyone know what exactly changed this year?

Even in the “low-performing” zone of the single threaded SQLite and Turso, we are still talking about 50k rows per second and 1000 microseconds, aka 1 ms. It is insanely fast. 1ms is just the round-trip for my Postgres on RDS. It is amazing that SQLite is so awesome. I understand it is not for every use-case, but still awesome

BEAM for the win

I can relate to this

Can’t argue with that. Machines are pretty capable, and elixir is awesome as well

I thought capitalism was about adding value, not conflict of interest

I like it. It solves a few issues I have with JSON. The quotes on the keys, the commas, etc. nice work. Keep them coming