smilliken

I've been using histre.com for years, which builds a personal search engine for the pages you visit by adding a browser extension. It's freed me from the habit of compulsively bookmarking everything in case I might need it again. I also keep a local text index for grepping which is plenty fast even with years of history and ripgrep, and comes in handy often.

That extrapolates to $87B per year for just the top spot on HN, more than all of Instagram's ad revenue, or about 40x Twitter's. Or $240M per day, about 1/3 of the ad spend on Superbowl, just for the top spot.

A literal toddler is one who can read.

I'm reminded of a Simpson's episode where Arnold Shwarzenegger is elected as President, given 5 stacks of papers with briefs of options, and he picks one at random without reading it saying "I was elected to lead, not to read!"

patchelf works on binaries. It's also possible to run a binary in a filesystem namespace with the dynamic libraries mapped.

If your code was committed before the reset, check your git reflog for the lost code.

If you're price conscious, buy the self-assembled framework kit. It's fun and takes half an hour to assemble.

I got a framework 16 with a handful of upgrades for $1400. I added 96GB of RAM purchased separately for $300 (before the shortage). I also got a 4TB NVMe for $300. What do those upgrades cost cost in a macbook?

I think most people care more about their OS than their hardware specs, so they defend their purchase like it's part of their identity and it's hard to have a rational discussion.

Edit: If you're talking about the Intel model, I agree with you. The Ryzens are fantastic.

Compress then encrypt is not an option because your encryption is broken if it can be compressed at all. Mathematically it's a near certainty that the compression would increase the file size when given an encrypted input.

That strategy may be cathartic, but it will have the opposite of the desired effect. If there's any hope of changing someone's mind, it has to start by respecting their opinion no matter how wrong you think it is. If you start a fight you'll get a fight.

You're going to look silly in 8000 years!

Practically speaking, it's impossible to roll 6 one hundred times in a row on fair dice. Not technically impossible, but we each get to calibrate our skepticism based on how far out the probabilities are.

In this case we can be sure the dice aren't fair because there's significant motivation for them not to be, or at least it's easy to imagine a manufacturing defect in the dice.

You can have this today or 15+ years ago using the excellent gevent library for Python. Python 3 should have just endorsed gevent as the blessed solution instead of adding function coloring and new syntax, but you can blissfully ignore all of that if you use gevent.

The best kind of documentation is the kind you can trust is accurate. Type defs wouldn't be close to as useful if you didn't really trust them. Similarly, doctests are some of the most useful documentation because you can be sure they are accurate.

The best way is to open a capsule for each batch you receive to test it by taste, then store in the fridge.

> Second: there is no CEO in tech taking a smaller salary than their employees.

That's not just false but very often false.