hanikesn
hanikesn on Hacker News
Not everyone is a supporter of capitalism unconditionally and they did great for more than two decades.
Because a lot of people enjoy the process. Why do you think people so wood working as hobby or the whole demo scene?
You'll quickly realize PCI mainly applies to the credit card industry and not to something like Europe's psd2 and sepa instant.
Most payment methods in the world don't support separate authorization and capture.
What's bad about it and what's a better one?
How is this related to kubernetes?
Why would you use the horrible GHA cache and not a much more efficient registry based cache?
Yep and have to pay for public IPs, which can become quite costly on it's own. Can't wait for v6 to be here.
>instead require the user to manually go into settings to turn them on, but if they do then it's still possible
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.
How does this require a whole team? Unless you're working at a hyperscaler
Delta Encoding is the common term
>this project appears to be on life support
Why do you think that? The upstreaming efforts are more fruitful than ever.
>I'm not really sure what to do. Maybe this MacBook Pro was just a one-off, and I have to go back to buying Windows laptops and putting Linux on them. But they just aren't as nice.
Why would you think that? They're working hard on upstreaming all patches ATM, adding new hardware support will be much easier afterwards.
In my experience Apple clients have been incredibly clingy to 6ghz bands, while much better 5ghz was available.
>Terraform is there specifically to solve the Aws infrastructure complexity
No, terraform passes AWS complexity 1:! onto you, it just allows you to tackle it in an ordered fashion.
Why 5h a week? Just for hardware?
Renovatebot would solve this consistently and is more broadly applicable.
>The M3+ GPU is also very different.
Any sources for that? I'd be quite surprised if Apple had radically altered the architecture.
First: It's great to have some serious competition in the durable execution market! You build some impressive tech already! It took me a decent time to investigate before pulling the trigger on temporal at my current PSP fintech as you'll end up with a pretty hard vendor lock-in which has to be worth it.
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
Yeah storage appliances predate public clouds fo at least a decade. Not even talking about mainframes etc.
It works well enough. When you need to signup for a new service on the go, you can add your backup key when you get to it. Having the backup key in a safety deposit box hardly accessible seems like a non-goal given you protect it with a pin with a very limited number of retries.
It works great with physical keys. Just need one as backup you leave at home.
What when is this going to be finally removed? I'm still reverting back to the old dialog on every machine.
How often did you access a nil pointer and caused a panic?