HN user

Shish2k

4,237 karma
Posts8
Comments1,230
View on HN

I'm am curious how you used satisfactory trains - I always found the satisfactory stations to be so overwhelmingly huge that they basically didn't fit anywhere (unless I build a layer of foundations a couple of hundred feet in the sky, which feels like cheating)

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"...

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)

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

I tried Sapling (Facebook's fork of mercurial with more polished git-compatibility layers) and never looked back for any of my own projects.

I recently started a new job where the vanilla git CLI is the only git frontend installed on company servers, and the regressions in user-experience are painful :(

Funnily enough I'm looking at getting a new phone because my pixel 6 battery no longer lasts 9am until 6pm without a mid-day charge -- I looked at the latest pixels (10) and they looked neat, but expensive; so took a look at the 9's, and saw they're basically exactly the same at 60% the price; then looked at the 8's and they're basically the same except 40% the price...

When every variable that represents a byte quantity ends in _size and every item count ends in _count, a reviewer can spot dimensional mismatches almost mechanically

At that point I'd rather make them separate data types, and have the compiler spot mismatches actually-mechanically o.o

I do love jetbrains for its nice-to-have features (eg highlight a few lines in the middle of a spaghetti function -> right click -> extract to new function) and was paying for it out of my own pocket for several years; but had to switch to vscode for a couple of required features that jetbrains was missing (remote dev over ssh, and devcontainers); and now switched to zed for being "like vscode but faster"

Each planet has its own gimmick which throws a spanner into standard builds in its own unique way - one planet is essentially a farm where your factory is growing and processing fruits, which will rot and spoil if they aren't processed immediately -- so you need to design a factory which processes small packets at high speed without any buffering.

I've been using the Sapling CLI frontend with GitHub as a backend for all my open source projects for a few years now (I've also used mononoke and eden at work, but IMO those only apply to people with hundred-gigabyte monorepos). So speaking based on my open source work:

- I am absolutely loving the improved UI/UX for common operations - being able to do the same actions with fewer commands and fewer concepts to understand, and much more helpful error messages when I try to do something invalid

- The existence of some unique features (`split`, `absorb`, and `restack` being particular favourites -- IIRC people have created third-party scripts to replicate these commands for git, but last I checked they weren't as good, and they aren't installed by default)

- Having the commit log integrated with github (being able to see which of my branches match to which PRs, and whether the PR is unreviewed / accepted / rejected / merged)

Sapling supports cloning, pushing, and pulling from a remote Git repo. jj also does, and it also supports sharing a working copy with a Git repo, so you can use jj and git interchangeably in the same repo

As a minor update - sapling now also supports the .git on-disk formats so that you can use git and sl interchangeably in the same repo

Hack is only PHP in a very ship-of-theseus sense - it has PHP _vibes_ but they replaced the language, the runtime, the standard library, and all of the infrastructure

(and all of them much improved over PHP IMO - especially XHP [equivalent to JSX, where HTML is a first-class citizen in the language syntax])