skysight-inc/HackerNews huggingface dataset:
there's nothing particularly magical and a lot the behaviors are actually similar to bazel, in ways. a version set is a directed acyclic dag of packages linked by dependencies. These edges comprise (more or less)

* normal deps

* compile/test deps (i.e. non-transitive)

* runtime deps

* tool deps (non-transitive, but also non impacting on the closure resolution algorithm)

version sets allow for multiple versions of the same package to exist in them (ex foobar-1.0 and foobar-1.1), which has some benefit but in practice is just painful.

dependencies are defined in a capital-c Config file. when you run brazil, it does a few things

* it resolves all of the tools and makes them available on your path

* it sets up some environment variables

* it invokes your a build command defined in the Config file

Config files can also declare outputs (there's also some canonical outputs), so you can use a query tool to ex.

* get all jars in the runtime closure

* generate a symlink farm of all client sdk configuration files

the results of your build go into a build directory, and when you want to generate the runtime for a particular package, it will symlink together the outputs of all packages in the deps + runtime closure, which you can do on demand.

version sets are updated by building new packages versions into them, which will rebuild the version set to make sure all builds pass. if they do, a new "commit" will be put onto the version set. you can also merge from one version set into another, where you can get packages and their associated dependencies merged in along with a full rebuild.
I’m a long time emacs and org-mode user but I switched to neovim for 90% of my development work. I still use emacs for org-mode and I doubt I would ever use org-mode in neovim because it relies on being implemented in the entire emacs system and the emacs lisp language . Nothing short of embedding emacs on neovim would make it tenable. I have the same problem in the other direction, viper is not a substitute for neovim.
Fair, and I appreciate your honest response! Life needs to see more positive discourse like this. :)
In the central valley of California, a house cost $130k in 1993 and today sells for $400k. In those 30 years you probably painted it a few times, changed the roof just recently, changed the kitchen, and so forth. Plus 30 years of property tax. So you're probably in for $200k on that $130k house. And that's not even counting interest on mortgages that most buyers had in 1993.

Doubling your money in 30 years isn't great at all. And this is within about 50 miles of tech jobs, although the drive will take 90 minutes in the morning and 60 minutes at night.
> There's only so far you can bus, train, drive, bike, walk, seaplane, helicopter, hyperloop, or transporter in to go to work. Canadian cities are, just like cities in the US, hitting this limit rather aggressively.

Canada's largest urban area is 5.6 million people. London, Paris and Seoul are around double that, NYC is 19 million and Tokyo is 37 million.

Why are Canadian cities hitting this limit at such a comparatively low population compared to other cities in the world? Why are all the major cities in the western world seemingly hitting this limit at the same time, even though they all have different populations?

It seems to me that we've just become less aggressive at building the infrastructure necessary to support population growth.
Leaving the philosophical issues out for a moment, this is a problem for me even as someone who had a Twitter account and wants to be signed in. Every time I click on a link to Twitter in the Reddit app on iOS it opens in the embedded browser where I'm not logged in and don't know how to open it in the Twitter app instead. It's a pain!
Something I still can't wrap my head around: are microplastics like these big/visible? The definition of microplastic is plastic < 5mm in length, but how big are the ones people talk about in articles like these? Is the implication that they're floating in the air and we just don't see them because they're too small? Or are they actually large enough to be visible but we somehow still get them into our bodies somehow?
The fun thing is I read the Sprawl and Bridge trilogies over the past year and oh my effing my how extremely accurate some of his extrapolations turned out to be. So rare and unusual, but post-2016 could not have turned out much different I guess
I agree so much! I was puzzled when Google introduced that feature to android and even advised it as the recommended way for apps to open links.

Can someone explain to me the reasoning behind that feature?

I mean, I can sort-of understand that individual apps want me to stay inside the app as long as possible. But why would the platform vendor actively support or even push that pattern?
Canada's immigration rate is over 1% it is very easy to get citizenship. There are already tons of front people with citizenship buying real estate on behalf of foreign investment pools. These measures are just PR, with 68% home ownership rate any measures that cooled home prices would be political suicide.
I'm a little removed from where I'd need to be to answer that very precisely, and probably shouldn't anyway.

They're not small- these are large, multitenant fleets handling huge numbers of NAT gateways all at once. The system has several layers, that scale on different dimensions and have different requirements. And those "requirements" can be very weird.

The part that actually moves packets around is probably mostly full-size c5n's, for the bandwidth.