We have a simple worker setup and temporal is pretty easy to setup
Out only issue is really needing an intermediary data store for task result storage
We are using DBOS in new projects as it's even simpler and the downside (task log interface behind saas) is easily remedied with a copilot generated task viewer
Possibly; I'm not going to hazard a guess on what the Supreme Court will decide the exact bar is. I just don't think it will be either extreme. "Nothing is copyrighted" is too damaging to the economy, "everything is copyrighted" has weird impacts on non-LLM copyrights that conflict with precedent.
> Are we supposed to expose all entities and relationships and rely on row level security?
Yes. This may feel foreign, but we think it's one the best ways to do permissions. We were originally inspired by Facebook's EntPrivacy. When you have permissions at the object layer, you can be more confident that _any_ query you write would be allowed.
Have you seen the meme with three spidermen, labeled "Designer", "Product Manager", and "Engineer" wherein each is pointing to the other two and saying "I don't need you anymore!"?
Most of the time, the person saying that is wrong.
I still prefer Deno because I don't need a separate npm install command, which makes running code that much easier
Being able to import from "https://my-vpn.com/mypackage@1.2.3" or "npm:package@1.2.3" and just running code without having to worry about scaffolding node_modules makes sandboxing code much easier
We have a simple worker setup and temporal is pretty easy to setup
Out only issue is really needing an intermediary data store for task result storage
We are using DBOS in new projects as it's even simpler and the downside (task log interface behind saas) is easily remedied with a copilot generated task viewer
reply