tasn

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.

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.

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.

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.

2: https://www.standardwebhooks.com/

Dupe: https://news.ycombinator.com/item?id=49098965

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.

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).

It has build.rs, which has essentially the same problems.

How is that different (in this sense) to any "slower" rewrites or other significant changes?

I wasn't comparing to Iran, I was just saying that putting an F-35 and a $2m drone on the same list and same count was funny.

As for the $40m number: I also saw this number, but I don't think it's correct. E.g. Germany recently bought 140 of them for $165m. Ref: https://www.i24news.tv/en/news/israel/defense/1649255166-ger...

Sure. But looking at all of the downed Israeli crafts, they are all $2-5m drones (all 18 of them).

For perspective: Patriot missiles cost $4m each.

It's a bit weird counting drones in the same list as expensive fighter jets (and other expensive planes).

I use bbwrap to sandbox Claude. Works very well and gives me a lot of control and certainty around the sandbox.

Just buy the family pack and get your wife and kids on it too.

As for traveling to the future: that sounds like fun!

Tip: if you implemented support for Clerk, you also support all the rest of Svix customers, and compatible with https://www.standardwebhooks.com/

So you support many more than you realize!

Cluely is not YC.

These are two sides of the same coin. Go has its quirks because they put things in the standard library so they can't iterate (in breaking manners), while Rust can iterate and perfect ideas much faster as it's driven by the ecosystem.

Thanks for the context!

Very cool, thanks for sharing! Please let me know if you end up open sourcing this!

Very interesting that they opted for a rewrite in Rust instead of adjusting the existing codebase.

I wonder how long it'll take them writing a compositor from scratch.

Pixels are pretty weak hardware wise in the areas people care about (heavy, relatively slow charging, big, etc.); I'd probably recommend people buy Samsungs which also get long term software updates nowadays.

How did you implement this runtime check? Is it a lint rule, or using the type system?

I think this framing is a bit backwards. Many C programs (and many parts of C programs) would benefit from being more like Go or Python as evident by your very own sds.c.

Now, if what you're saying is that with super highly optimized sections of a codebase, or extremely specific circumstances (some kernel drivers) you'd need a bit of unsafe rust: then sure. Though all of a sudden you flipped the script, and the unsafe becomes the exception, not the rule; and you can keep those pieces of code contained. Similarly to how C programmers use inline assembly in some scenarios.

Funny enough, this is similar to something that Rust did the opposite of C, and is much better for it: immutable by default (let mut vs. const in C) and non-nullable by default (and even being able to define something as non-null). Flipping the script so that GOOD is default and BAD is rare was a huge win.

I definitely don't think Rust is a silver bullet, though I'd definitely say it's at least a silver alloy bullet. At least when it comes to the above topics.