231 karma · joined March 29, 2016
They clearly addressed this option in the post, under sufficient social engineering pressure these settings will easily be circumvented. You'd need at least a 24h timeout or similar to mitigate the social pressure.
This can already be done with LE audio, support is coming slowly.
Why do you think that? The upstreaming efforts are more fruitful than ever.
Why would you think that? They're working hard on upstreaming all patches ATM, adding new hardware support will be much easier afterwards.
No, terraform passes AWS complexity 1:! onto you, it just allows you to tackle it in an ordered fashion.
Any sources for that? I'd be quite surprised if Apple had radically altered the architecture.
I have to say the architecture blog post is very leightweight on details, which makes it hard to judge so you have to dive into the docs for the spicy details and I see abig showstoppers for our usecase:
1. Workflow versioning: It seems currently impossible to properly upgrade inflight workflow without manually forking the workflow
Also the marketing material and docs aretoo handwavy on the idempotency and determinism constraints, which makes them dbos seem to good to be true. I'd also love to see higher level abstractions around message sending. Temporal's signal, query and update are essential building blocks for our use cases and allow some quite interesting use cases as you can really view workflows as actors.
I hope you can keep innovating as temporal really is too heavy for a lot of use-cases.
See: https://docs.dbos.dev/production/self-hosting/workflow-recov... https://www.dbos.dev/blog/handling-failures-workflow-forks
https://peps.python.org/pep-0723/#why-not-use-possibly-restr...