This doesn't prevent overrunning the buffer -- it means that when you do overrun the buffer, it does less damage

They stopped getting new features a few years ago, and existing features have been gradually removed...

People within Meta have been campaigning for this for _years_; even people as high up as John Carmack were pushing for open bootloaders on deprecated hardware (and he achieved that on the Go headset, but not as a general policy)

> It is sad that it takes a Meta developer having some fun to realize they should open up ADB.

I'm not even sure if the motivation is as positive as that - the video, blog, and dev docs read more like a sales pitch for meta's AI tools...

(I'm glad they did it, the portal is great hardware; but I don't expect that this will be a pattern of opening up old hardware unless it provides tangible benefits to the AI department)

javascript uses floats as its own default numeric data type; but other languages do have integers, and might want to convert those integers into a JSON (string) representation

FWIW you can still have a staging-area-like workflow with JJ - it's just that while git has "commits", "the staging area", "the working directory", and "stashes" as four separate concepts with four separate toolkits, in JJ all of those things are "commits" and a single toolkit works with all of them :)

I hoped that would be possible but wasn't sure, thanks.

Last I checked (2 years ago) Meta was using Sapling, a very heavily customised open source Mercurial frontend with proprietary backend.

FWIW the Sapling frontend can also be connected to a Git backend, and I've been using that for all my open source projects to get the best of Mercurial's user experience niceness while collaborating via GitHub <3

Still Sapling + Eden to make local work on a sparse checkout viable.

Except if you're posting stories online, in which case it's most likely a gibimesh, though people use the terms interchangeably

In the circles where I hang out I think community opinion is that go is _fine_, but python has faster iteration speed for experiments, and rust has better correctness and performance for production, so there's less excitement around it

Facebook started out PHP; but they ship-of-theseus'ed it into Hack by replacing the standard library, the language, and the runtime engine, so now it's a totally different thing with only a few superficial similarities (FWIW IMO Hack is much better than PHP, I'm sad that it never gained traction...)

Much of what was good in Hack just got rolled into PHP.