agocke

agocke, 11 days ago

@tojiro @mekkaokereke electric mini cooper

agocke, 25 days ago

All allocations start in Gen 0, also called the "nursery", which you can think of as arena allocation. Whenever you do a Gen 0 collection, the whole arena is freed, except that anything still alive is moved into the Gen 1 space. This actually maps pretty closely to the "request-based" model. If most of the allocation in your app is due to handling requests than the vast majority of Gen 0 will just be current requests.

agocke, 25 days ago

The pluses and minuses are that Gen0 collection may not happen at the end of a request and instead occur in the middle of the next request. But, 1) that means you do fewer collections overall and 2) Gen0 collection and Gen1 promotion aren't so bad, assuming your Gen1 isn't the same as your super-long-lived generation.

agocke, 25 days ago

@Migueldeicaza you mean the language feature that allows specifying a particular arena an allocation must occur in?

agocke, 23 days ago

@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

agocke, 23 days ago

@yminsky both :)

agocke, 23 days ago

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

agocke, 23 days ago

@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

agocke, 25 days ago

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.

agocke, 25 days ago

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.

agocke, 17 days ago

@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

agocke, 17 days ago

@Migueldeicaza what is commonly misunderstood? What misconception is MMT meant to correct?

agocke, 17 days ago

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

agocke, 17 days ago

@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?

agocke, 17 days ago

@Migueldeicaza does the movie have more than Keltons book?

agocke, 25 days ago

@bradwilson could be, not really meant for that. Dotnet-install script would probably work better. This is more for dev boxes.

agocke, 25 days ago

@bradwilson You might want to use https://dnvm.net if you need a wide range of SDKs to install and test against