4 ms·
GC compactions were indeed a problem for a number of systems. The trading systems in general had a policy of not allocating after startup. JS has a library, c
by rauljara 1y ago
GC compactions were indeed a problem for a number of systems. The trading systems in general had a policy of not allocating after startup. JS has a library, called "Zero" that provides a host of non-allocating ways of doing things.
- jitl 1y agoCouldn’t find this after 6 seconds of googling, link?
- jallmann 1y agoThe linked podcast episode mentions it.
- notnullorvoid 1y agoThere's no mention of a library called zero, or even JavaScript.
- garbthetill 1y agoIm assuming the JS refers to Janes street
- notnullorvoid 1y agoThat makes sense, I guess I've got web tunnel vision.
- sheepscreek 1y agoI was bit by the same spider that gave you web tunnel vision. In any case, I find OCaml too esoteric for my taste. F# is softer and feels more..modern perhaps? But I don’t think GC can be avoided in dotnet.
- debugnik 1y agoYou can avoid GC in hot loops in F# with value-types, explicit inlining, and mutability. Mutability may not result in very idiomatic code however, although it can often be wrapped with a functional API (e.g. parser combinators).
- jallmann 1y ago> This is what I like to call a dialect of OCaml. We speak in sometimes and sometimes we gently say it’s zero alloc OCaml. And the most notable thing about it, it tries to avoid touching the garbage collector ...
- deleted 1y ago[deleted]