plugin-baby

> It is uncertain when it went from purple to red, but it's likely a practical reason: when going outside you don't wear slippers but leather boots, which were very easy to get in a red color, purple? Not really. You can easily find purple used anywhere in clothing, but not shoes.

Wasn't the point of regal colours that they were scarce/expensive?

There are a few mentioned in the footnotes.

> In text I can't do justice to the facial expressions of cryptographers when you mention Telegram's protocol, so just believe me that it's weird.

Seems like a red flag.

> Is someone actually mad prettier is changing their single quotes to double quotes? Are they mad some line is breaking at some word?

Yes, both of these.

Obviously there are huge benefits to auto-formatting in large teams and popular open source projects, but some people also find benefit in having control of alignment, line breaks, indentation etc.

This isn’t likely though, is it? The device is unlikely to be running NodeJS and playwright.

Based on how hackable their infra is?

> The author of DOOM for SNES, Randy Linden, did not have access to any documentation about the GSU chip or even DOOM source code. He reverse engineered all of it

Technically this is impressive, but why was it necessary?

> Git is not your backup solution.

Yes it is. What am I doing wrong?

Spanish: jodido

I haven’t had similar issues with React, and I been using it much longer - Next.js is a special case.

Are you recommending Next.js for its longevity? My experience over the last 18 months is that every new version introduces breaking changes. I wouldn’t want to come back to a Next.js project in 5 years and have to deal with migrating to Node.js v32 and whatever Next.js has broken in the meantime.

Apart from speed, what advantages does ripgrep offer over git grep when searching git repos?

> what I call HN driven development: k8s, microservices, cloud

I’ll give you cloud, but my takeaways from HN in the last few years have been things like:

* Postgres is a reasonable choice for a job queue * SQLite is a valid choice for server db at quite large scale * k8s makes sense once you have 50+ devs * microservices address issues of team scale, not traffic scale