If you got upset at me for pointing out that more people died of Covid under Biden than Trump, in large part because Biden rolled back common sense restrictions that were in place under Trump...
Then you'll hate me pointing out that Trump introduced a 25% tariff on Chinese EVs, and Biden is upping that to 100% tariff.
You canโt beat this 1:35 minute crash course on how our economy works. It voodoo, not a dark art, not medieval knowledge. Just plain and accessible economics.
This course should be taught in high schools.
You can then nicely progress to various books and textbooks if you want.
@Migueldeicaza I don't understand the dispute here. Orthodoxy seems to say that we have to pay the debt through taxation. MMT seems to say you could also print dollars. But both agree that printing is limited by inflation. So there's only a difference at ZIRP, which is not around anymore. So what's new?
@Migueldeicaza ok, but we are currently in a world of full resource utilization, which is why inflation is above target. So this insight was useful 4 years ago, but not useful now.
@Migueldeicaza yeah โsupply chain reasonsโ meaning thereโs not enough supply. Thatโs what โresource limitationโ means. Whether or not interest rates alleviate the pressures is not relevant to whether there is enough productive capacity
And, most importantly, many apps in languages like C# still have some objects that live from session to session (caches, etc). So while the gen0 hypothesis is modally true, there are enough corner cases to mean you still have to handle them well, and regular generational GC does so without special cases in the GC.
Maybe languages like Erlang that have a much more fine-grained and structurally enforced lifetime boundaries can do something more specific, but languages like C# have to deal with a bit more imperfection.
@yminsky .NET has always had a similar story, but more explicit. There are two kinds of types in .NET: value types and reference types. Locals and parameters of value type are always stack allocated. References are heap allocated. There's also a 'managed ref' which can point to either, and has a lifetime that is implicitly tracked.
This whole deal is much more implicit and has fewer safeguards, but generally works.
@yminsky the declaration of struct vs class means you choose up front the memory representation. But also structs can be boxed, so you can implicitly go off the rails. And managed refs can point to either, but they have hidden implicit lifetimes
@yminsky the effect for the user is I think that things seem very simple: just struct or class. And with careful programming you can go allocation free. But the rules for an expert are probably more complicated than judicious use of a proper type system