HN user

thefifthsetpin

557 karma
Posts0
Comments166
View on HN
No posts found.

That's harsh. I believe the author really does get questions from people who want to register a well known path, and probably some of them really failed to consider sites with ~user paths or whathaveyou and this post might push them to use a better solution.

And if you read that and still feel confident that you want a well known url, he links you to the registration process.

Same as a NSFW tag. It's not about adding to the discussion; it's a very brief warning to users who don't want to see that kind of content, and its brevity makes it come at almost no cost to users who don't care about SFW/NSFW or AI/OC distinctions.

That explains it for some people, but there's something more here.

Hell, I've personally mentored people who struggled with git and I could feel their struggle.

I'm not saying that learning git was an insurmountable task for them, but their struggle was not something that I had to go through.

I've long been facinated by how bimodal understanding of git is. I'm one of the lucky ones to whom it came naturally, but there's clearly a large population who finds git challenging even after investing significant time and effort into learning it.

I don't see this anywhere nearly as drastically with other tools.

I'm so stoked. Pebble was the only smart watch that I actually liked and used.

My apple watch just sits on a shelf. My fitbit I only wear when sleeping. My pebble unfortunately broke, but it also sits on a shelf as I haven't been able to admit to myself that I'd never get around to repairing it.

There might be someone hopelessly addicted to amateur astronomy, frequently disrupting their sleep schedule and taking out usurious loans to pay for their equipment. But, that's not happening on a scale that we need societal regulation. Gambling is a different sort of vice than many fun activities.

My ~/bin directory is not directly version controlled. It primarily consists of symlinks, often stripping file extensions from shell scripts (e.g., ~/bin/foobar links to ~/src/foobar.sh) I have just enough python scripts and go binaries to make me think it's worth separating src and bin.

~/src is a git repo. One script evolved into its own project and became a submodule within ~/src.

For configuration files like ~/.foobar_rc and directories such as ~/.vim/, they again are not directly version controlled but are symlinked into ~/etc which is. I don't see any reason that ~/.foobar_rc couldn't be a hardlink, but it's not in my setup.

I used to maintain a single repository at ~ that included ~/src and ~/etc as submodules, with a build script for setting up links. Always being within a git repository became cumbersome, so I moved the build tools into their respective directories (~/src and ~/etc) and now clone and build each repository manually.

Lastly, since private repos aren't (weren't?) free, those submodule repos are really just branches of the same repo that share no common ancestors.

You're perhaps confusing Colorado with a bunch of the states around it. Sure, its economy looks small compared to California's, but California's economy is mind-bogglingly vast. Not many companies are willing to write-off ~12% of California.

I have no credentials here, but I'm often working in this space and your take is the polar opposite of what I normally hear from the endos and diabetes researchers that I've worked with. More accurate terms might be diabetes and morbid diabetes.

That the cutoff for prediabetes is close to the median level is a statement that much of the population is actually unhealthy in this regard.

I can't speak to sheep specifically, but we use different species of goats and cattle and chickens when raised for meat vs for dairy or eggs.

Still, dairy cows do eventually become beef. If you ever see a cut of beef that's normally bone-in but the butcher chose to debone this one, then there's a good chance it was from a dairy cow whose bones were too calcified to saw through.

That was surprising to me so I dug into the citations [1][2] that correspond to that line in Wikipedia.

Citation [1] actually uses the "can and may" verbiage.

Citation [2] refers to the "will" verbiage as "now familiar verbiage" in a footnote, but it doesn't seem to be arguing that that verbiage is prescribed or accurate -- just that it's now familiar. It also incorrectly quotes that verbiage as coming from the original court ruling, so clearly they lost track of where they actually got it from (since it's not there).

I did find a quora answer [3] which gave an origin story for the "can and will" verbiage, but at this point I'm not ready to trust anything written on the topic that doesn't have solid references.

[1] https://www.law.cornell.edu/wex/miranda_warning [2] https://web.archive.org/web/20230513064943/https://scholarly... [3] look for Mark Tarte's answer to https://www.quora.com/Why-does-the-Miranda-warning-say-can-a...

The gap between "can and may" and "will" might seem a bit nit-picky, but vintermann's interpretation depends very heavily on that "will."

There's also nothing special about being arrested that makes it so that anything you say could be used against you in court. It's really a just reminder that your right to remain silent may have value to you.

The Russian government has recently shown itself to be willing and even eager to use coercive tactics against its own people.

The trust issues with software developed by Russians isn't that the engineers are Russian. It's that the engineers and their families are currently in Russia.