I don’t let Claude touch git at all, unless I need it to specifically review the log - which is rare. I commit manually often (and fix up the history later) - this allows me to go reasonably fast without worrying too much about destructive tool use.
> India is the world's largest provider of generic medicines by volume, with a 20% share of total global pharmaceutical exports. It is also the largest vaccine supplier in the world by volume, accounting for more than 60% of all vaccines manufactured in the world.
They clearly had enough access to capture and spot-check some of this data against previous leaks. The fact that this is not mentioned doesn’t inspire much faith in this being something new and newsworthy.
We have, and I won’t lie, it’s kinda a pain. The reality we discovered is that async flows are second-class citizens in otel tracing.
We essentially propagate the context manually between APIs and lambdas, through HTTP headers, SNS/SQS and even storage. We also ended up pulling Tempo’s Parquet files (we’re self-hosting the grafana stack) into Redash to be able to do real analysis. We got a lot of great insights and were able to do a lot of tuning that would have been impossible otherwise, but it was quite an investment. Would love to know if there is anything out there that would have made this less painful.
Agree - playing Path of Exile 2 at the moment. I think they are co-located with the Geforce Now servers for my region (Frankfurt) as I have 1ms ping from Nvidia->PoE. 20ms from my house to Nvidia, so I’m not sure my experience is much different from what one would get with a gaming rig.
And if you do the math on what one would cost - by the time the subscription cost catches up, it’s time to upgrade the rig.
To be fair, the sub-prime lending crisis had its roots firmly in Clinton-era repeal of Glass-Steagal, so it’s not all so easy.
No particular love for the Republican Party, but it’s a problem created by the Democrats, which they then patched with the inferior Frank-Dodd. Plenty of stupidity to go around, I would say.
Glass-Steagal was repealed by a GOP Congress. And the 2009 bailouts were Obama’s implementation of a plan devised by the Bush administration.
That said in economic and trade policy there’s not much difference between Reagan/Bush/Clinton/Bush/Obama. All support free movement of goods and labor. The only difference was in how big of a welfare state to have to mitigate the negative effects.
> the sub-prime lending crisis had its roots firmly in Clinton-era repeal of Glass-Steagal
Not really. You'd just have very highly correlated financial entities that would have collapsed the exact same way. AIG received the largest bailout and wasn't even a bank.
> they then patched with the inferior Frank-Dodd.
Dodd Frank is why the finance sector was stable despite all the volatility introduced by the pandemic and inflation. The culture of banking has significantly shifted to being more conservative now, and risk has moved to the buy-side of trading, which is easier to let go of. Trump partially rolled back regulations such that banks under $250 billion no longer had to had to conduct stress tests, and bank collapses occurred all the way up to that threshold.
You know, on Saturday I generally spend my day with my family rather than answering snarky comments. But since I have some time now let's get down to the answer:
> Runes Only Work in Svelte Components or .svelte.ts Files
Yes and this is actually a positive thing: you want the compiler to touch a very contained part of your application, when you know you can expect magic. This also allow us to be more "aggressive" in the transformation since we know regular js libraries will not be affected by it.
> Hooks Using Runes Must Wrap State in Functions
This is true for svelte, Vue, solid and whatever signal based framework: the difference? Other frameworks can't deal with primitive values so you feel like you have to do extra work in svelte. In reality you can actually build both Vue and solid styles in svelte (the opposite is not true). $state({ value: "myval" }); if basically Vue ref.
> Classes as First-Class Citizens for Runes... or Not?
You start talking about classes and then complain that pojos don't have the same treatment? Those are two very different things, and again, it was a specific design choice...it might be a quirk that you have to know about (that the compiler literally highlight for you) but it serves as a guardrail for you to write less bug prone code. P.s. as said above you can actually build a ref function a la Vue pretty easily and you can use your ref function just like in Vue if you really want this behavior.
> Svelte Templates Include Features That Cannot Be Implemented in JavaScript
This is just blatantly false: you can test a bindable props by passing in state as props and that's literally it. If you want you can do
```ts
const props = $state({ value: "" });
render(Component, { props });
```
or if you want to have a literal prop you can just use getters and setters
```ts
const value = $state("");
render(Component, { props: {
get value(){
return value;
},
set value(new_value){
value = new_value;
}
}});
```
> Form Components Are Uncontrolled by Default, Which Can Cause Issues
As you've said this isn't specific to svelte...the controlled nature is specific to react. Why this would be the right thing? Most of the times having an uncontrolled form is much better and you can sync the state on submit or even better just use normal forms with enhance and sync the state on the server by getting progressive enhancement for free. And if you need it to be controlled, you have the tools to do it.
> Small Ecosystem
If you search for svelte specific packages you will certainly find less than react...but you can literally just use any JS package with ease in svelte. That said even for the things you describe in the post it seems you are a bit nitpicking: there a router but not an in memory one, there's shadcn/svelte but it has problems with shadow Dom...the rest you probably just need to search better: `virtua` is a wonderful virtual list, LayerChart a wonderful chart library.
> Community Response
We are definitely trying to work to reduce the apparent complexity...a lot of people looked at svelte 5 superficially and deemed it too complex. The same people after trying it for good agreed that is not complex at all and a huge step forward for composability and performance. Just try it out, trust us.
That said: despite almost all the point being imho invalid this is still a good post because it show us where we can improve the docs and the explainers to ease out this experience.
Yes you are right that this is nonsense. They have clearly already been doing this for years on the backend at a minimum to power the Google Photos search functionality, and who knows what else.
