The criticism of Cloudflare here is reasonable, I think. I really like the CF building blocks - they're neat and conceptually useful and quite unusual. I think they could have a better developer experience though (though it probably is better than when I last tried it), and I also think they could have a little more confidence in their overall platform's usefulness and open up more of their model as open source. For example, I'd love to run my CF workers in CI locally without creating infrastructure (again, this may have changed since I last tried it).
I don't know if it is ai generated or at the opposite hand written a little bit fast but I find this article very hard to read despite the concepts in it being simple.
celld and workerd give you Durable Objects if you run another daemon. This is a library your app loads, with state stored in the SQL database you already have (Postgres, MySQL and SQLite supported). No daemon required, no new infrastructure and monitoring, no broker, and no vendor account.
Pre-1.0, MIT, TypeScript, in browser (with WASM SQLite), and Ruby too. Happy to answer anything.
This looms nice and I starred but you just want actors and there are other options for that you might want to compare, I like rika actors, or temporal (not actors exactly but durable state and workflows). This is a space where a few very similar technologies after looked from different lenses sell themselves widely differently. So if you know what you want and the names of the things you are searching for you can get a thing that looks 90% like te rest, sorry a bit rambly. But yeah it would be nice to add some comparisons against these technologies as well.
7 comments:
The criticism of Cloudflare here is reasonable, I think. I really like the CF building blocks - they're neat and conceptually useful and quite unusual. I think they could have a better developer experience though (though it probably is better than when I last tried it), and I also think they could have a little more confidence in their overall platform's usefulness and open up more of their model as open source. For example, I'd love to run my CF workers in CI locally without creating infrastructure (again, this may have changed since I last tried it).
Why chose the Solid- line of naming, considering that's the rails provided naming. I makes it look like this is official.
I don't know if it is ai generated or at the opposite hand written a little bit fast but I find this article very hard to read despite the concepts in it being simple.
I couldn't parse "Getting that model has meant taking on something else."
The article is 1000% ai slop
Author here.
celld and workerd give you Durable Objects if you run another daemon. This is a library your app loads, with state stored in the SQL database you already have (Postgres, MySQL and SQLite supported). No daemon required, no new infrastructure and monitoring, no broker, and no vendor account.
Pre-1.0, MIT, TypeScript, in browser (with WASM SQLite), and Ruby too. Happy to answer anything.
This looms nice and I starred but you just want actors and there are other options for that you might want to compare, I like rika actors, or temporal (not actors exactly but durable state and workflows). This is a space where a few very similar technologies after looked from different lenses sell themselves widely differently. So if you know what you want and the names of the things you are searching for you can get a thing that looks 90% like te rest, sorry a bit rambly. But yeah it would be nice to add some comparisons against these technologies as well.