swgillespie

5 ms·

1.
by swgillespie 1y ago
Yeah - I worked on that build team probably at the same place you did! I think for a lot of users it's more important that the monorepo devenv be reproducible than be specifically local or specifically remote. It's certainly easie
2.
by swgillespie 1y ago
thanks!
3.
The Ingredients of a Productive Monorepo(blog.swgillespie.me)
2 points by swgillespie 1y ago|0 comments
4.
by swgillespie 6y ago
It is. A few key assumptions are based into the runtime, namely that the GC is a generational GC with contiguous regions and that the GC doesn't need a read barrier, among many other things. There's a bunch of assembly in the runt
5.
by swgillespie 8y ago
There are a couple of projects that do this for Rust, depending on what your inputs and outputs are: * https://github.com/rust-lang-nursery/rust-bindgen - Inputs are C/C++ headers, outputs are Rust type definition
6.
by swgillespie 8y ago
[Disclosure - I'm a Pulumi employee] There is a top-level CLI verb called `refresh` that explicitly checks Pulumi's idea of the state of the world against the actual state of the world. If there's a diff, Pulumi reconciles th
7.
by swgillespie 9y ago
The .NET GC hands out "allocation contexts" to every thread. An allocation context is little more than two pointers: the bump pointer and the bump pointer limit. If the runtime allocates too much and exceeds the bump pointer limit
8.
by swgillespie 9y ago
This /is/ geared heavily towards improving the .NET Core story. The purpose of this spec is to provide library authors with a set of APIs that they can expect will exist on .NET Standard 2.0-implementing runtimes (a list of which
9.
by swgillespie 9y ago
The ".NET Spec" doesn't have the name ".NET" in it anywhere - .NET has always been the name of Microsoft's implementation of the Common Language Infrastructure spec ( https://www.ecma-international.or
10.
by swgillespie 11y ago
When you throw an exception on the CLR, it will 1) walk the stack looking for candidate catch blocks, and 2) if it finds one, it will long jump to that catch block, destroying all stack frames between the frame that threw the exception and