Followed the app's instructions to go to gate 15, sat there waiting for the gate to open, until eventually getting a notification that I'd missed the flight from gate 30. Went to the help desk, was told that since I was the only person who made that mistake it was clearly my fault rather than the app (which was still displaying the wrong gate, even while I was at the help desk). Got booked on a $400 replacement flight for a journey which was originally $50. In the queue to board the replacement flight, I meet around 20 other people who missed the same flight for the same reason, all being told "it's clearly your own fault, ryanair has no responsibility here"...
I've been caught out by that before - apps are not up to date. I wait at a spot in the terminal where there is a physical display for gates these days, not worth the risk.
I also hate Ryanair and will only fly it if there is no other option.
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 :)
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
reply