tasn
Joined 12 years ago
Karma
1,902
Submissions
638
Member since
Oct 4
Recent submissions
Comment · 2 months ago
It's a matter of expressiveness, Rust expresses more.
E.g. make a table that's 3x3 is easier to read (Go), but the equivalent line in Rust would also include material, angles, height, etc. because the type system encodes much more information.
Though I always found Go to be significantly harder to read than Rust. Sure Rust has some crazy syntax at the edges, but Go makes it very hard to know where imports come from (and thus what they do), and the imperative style + lack of clarity about mutability makes code much harder to reason about.
Comment · 2 months ago
I know (from our customers) that some of their customers make buying decisions based on the availability of webhooks. I'm unaware of anyone doing it based on the availability of our other functionality (but it could be I just don't have the data).
Though the data I do have: how many people adopt these advanced endpoints in practice (as we offer these), and it's less than webhooks.
Comment · 2 months ago
We (Svix, webhooks infra) actually help our customers directly write to Kafka topics, S3 buckets, SQS, etc. and have for a few years now. There are definitely people that adopt that, but receivers as well prefer the simplicity of webhooks.
Comment · 2 months ago
Webhooks are simple and ubiquitous, and that's both a weakness and a strength. It's also why they are used for a lot of things, even things they are not great for (state sync).
These weaknesses are why we[1] added FIFO endpoints, Polling Endpoints, and what we call "Svix Stream" as ways to do ordered state synchronization (each with its own tradeoffs). This lets people consume the events in the way that best fits their use-case. We are working on more things to make the state sync even easier. I'd love to hear about more challenges people are facing with webhooks, as we want to make these things better.
OP: I'd love to hear more about your thoughts there, and will send you an email in a moment.
P.S, if you're unfamiliar, please check out Standard Webhooks[2]. It's a spec we created to help with signature verification that has been adopted by OpenAI, Anthropic, Google, and many others. We are chipping at one webhook challenge at a time. :)
1: I'm the founder of Svix (mentioned in the post), we do webhooks infrastructure as a service.
Comment · 3 months ago
Comment · 3 months ago
I've lived both in the US and the UK.
The US has the 5th amendment protecting you from self-incrimination, while in the UK you can go to prison for not divulging your encryption password (even if you forgot it!).
The US doesn't have ISP/DNS level blocking for all I'm aware of, but there's the ultimate blocking that sometimes does happen (FBI raiding your servers, even if outside of the US).
The US has the 1st amendment protecting speech, while in the UK people routinely get arrested for social media posts.
Maybe there are areas where the UK is better about privacy/freedom than the US, but no examples immediately come to mind.
Comment · 3 months ago
This, and other similar legislation, serve as a constant reminder of why the American founding fathers had to revolt against tyranny, and why constitution amendments like the 1st and 4th exist. The 4th in particular was written as a response to a British law similar to Chat Control (writs of assistance).
Comment · 5 months ago
It has build.rs, which has essentially the same problems.
Comment · 5 months ago
How is that different (in this sense) to any "slower" rewrites or other significant changes?
https://stosb.com
https://www.etebase.com
https://www.etesync.com
https://github.com/tasn
https://mastodon.social/@tasn
https://twitter.com/TomHacohen
Contact: at tom @ any of the domains above.