I think all modern system even scylla db do commit batch no fsync on every write, you either need throughput or durability both cannot exist together. Only thing what redpanda claim is you have to do replication before fsync so your data is not lost if the written node is dead due to a power failure. this is how scylla and cassandra works, if iam not wrong, so even if a node dead before the batch fsync, replication will be done before fsync from memtable,so other nodes will bring the durability and data loss is no longer true in a replicated setup. single node? obviously 100% data loss. but this is the trade off for a high tps system vs durable single ndoe system brings. its how you want to operate.
I tried Motiff and penpot, to be framk Motif was way superior than both figma and penpot in terms of rendering and performance with large design files. unfortunately they shutdown due to lawsuits. Went back to figma.
Quoted from Article: If we can understand what’s driving it at the molecular level, we can start to understand what goes wrong in dementia and eventually use that knowledge to guide new approaches to treatment.
Hopefull.
Suing someone because your product doesn't work correctly is diabolical. Instead of filing a lawsuit, they should have acknowledged the issue and released an upgrade to their locks.
Not related to this directly, but shadcn drawer is built on the top of vaul which is unmintained, so who ever use this in production, keep this in your mind.
reply