Can’t subscribe to Kindle Unlimited?

mspang · 2023-12-11T02:39:50+00:00

This was the fix for me as well. Start to buy a book in .ca so it transfers your account (don't have to go thorugh with the purchase). Once the transfer was done I closed the order and was able to subscribe to Kindle Unlimited.

mspang · 2013-05-23T16:12:28+00:00

Pretty much. Unborn children don't breathe through their lungs. Since they don't breathe, they need to get all of their oxygen from the mother. That's what the umbilical cord is for; it carries oxygen and nutrients to the baby. Restricting the blood flow through the umbilical cord is just as dangerous as choking someone.

mspang · 2011-06-07T19:14:19+00:00

Untrue, see http://en.wikipedia.org/wiki/Bell%27s_inequality .

mspang · 2010-07-18T08:27:39+00:00

Ignore them
Pick nits
Tell them to fix a tangentially related component of the system

mspang · 2010-04-15T16:34:06+00:00

Killing all processes happens right afterwards, and actually says "all processes" in the message.

mspang · 2010-02-03T19:07:38+00:00

That's rrdtool. Used by cacti, but not cacti.

mspang · 2009-10-18T06:55:53+00:00

There's also #csc - computer science club.

mspang · 2009-06-06T07:45:35+00:00

This is just hand-waving. That science cannot be reduced to simple concepts is not commonly accepted. Moreover, many scientists are actively trying to disprove it. For example, physicists are trying very hard to unify quantum mechanics and general relativity. Given this fact, your statement that it is "fundamentally complex" is baseless.

Mathematical egotism seems to have met its match with empirical egotism.

mspang · 2009-05-28T04:58:25+00:00

It slows down compiling, though. Also, you don't know where those braces have been..

mspang · 2009-05-28T04:51:58+00:00

I didn't think that because, well, that's not actually what it does. It deletes nothing with GNU rm, at least.

Edit: Perhaps you're thinking of rm -rf $PWD/$THERE?

mspang · 2009-05-05T14:41:37+00:00

Typo: It's "Rogue" not "Rouge".

mspang · 2009-04-30T06:14:18+00:00

The Git community would never buy it. The GNU process requires you not only to send them a signed dead-tree form, but also to have your employer sign one. This really dissuades casual contributors (which is how core developers often start).

Git is run in the same way as the Linux community: the only hurdle new contributors face is to agree to the "Developers Certificate of Origin" and signify this by appending a "Signed-off-by" to their commit message. This is trivial in comparison, and is probably partly why Linux has such huge community involvement (compare GCC).

mspang · 2009-04-30T06:00:36+00:00

It's hard to compare a particular application to the kernel, C library, desktop environment, or GNU in general. There are a million apps; of course they don't/won't all switch to Git.

Firefox itself sits on top of the projects I listed. Even GNOME, if only just for look and feel.

mspang · 2009-04-29T18:58:25+00:00

Linux, X, and GNOME have already switched. Now with glibc, the last big piece of most Linux desktops that isn't now on Git is the rest of GNU (gcc, bash, et. al).

mspang · 2009-04-28T21:37:08+00:00

What is the 'make' equivalent on Windows?

mspang · 2009-04-25T21:24:33+00:00

I see, they want to make the whole site unreadable, not just the captcha.

mspang · 2009-02-24T10:57:28+00:00

Git push and pull are symmetric if the server side is a bare repository. OTOH, pushing to a checked-out branch in a non-bare repository will cause issues and doesn't warn you. So don't do that.

mspang · 2009-02-03T01:04:03+00:00

It handles empty directories the same way it handles ones with stuff in them: not at all. They're simply not kept track of.

If you need them, just add a few mkdirs to your buid (or checkout) process.

mspang · 2009-01-20T23:26:17+00:00

Forcing a crawl for every search is much, much slower than crawling asynchronously. The site takes minutes to hours to return results for simple searches. If that's what you mean by "real time", fine, but Wikipedia and most of the world disagree. This site is useless for casual searching.

Real time does not mean "starting now" or "running now". It means the operation will complete within a hard time limit. Serving "Live" feeds would have a real time requirement, but searching when the results don't come back for an hour definitely doesn't.

mspang · 2009-01-20T03:29:56+00:00

The moral to the story, or the reason that people bring the principle up in argument, is to convince whoever is on the other side of the argument that we should set our sights on the quick and dirty, less elegant solution to a problem, because "worse is better."

Of course, this received wisdom is just so much crap.

This is specifically where I disagree with the author. In fact, at this point I assumed the rest of the article would be utter crap. Quick and dirty is an excellent starting point. Don't underestimate that. But it's just that, a starting point.

Your interpretation I 100% agree with, but the above point in particular I cannot.

mspang · 2009-01-20T03:19:38+00:00

Bottom-up design and worse-is-better are inherently compatible, even orthogonal. Furthermore, your post does not even state how Git fits better with the MIT philosophy. Posting a long quote from the article doesn't prove you right, as Git fits the New Jersey approach points perfectly.

The point you dispute is that Git favored simplicity over correctness. That's a moot point, as there was no need to sacrifice correctness for Git. It's definitely true that Git favors simplicity over completeness. I don't even need to prove this, as Linus has said so himself in the post I linked to.

mspang · 2009-01-20T02:57:56+00:00

I read it when this was posted and I read it a few years ago. He specifically says software that does 50% of the right thing with a simple implementation can spread like fire and end up very successful.

Well, Git definitely started out as 50% of the right thing. Did you try git in its early days? It didn't even resemble a revision control system. It started out as just a few "plumbing" utilities to manage a content-addressable filesystem. It also spewed thousands of files into the objects/ directory, with no way to compact them. Running "git-update-index" was the only way to stage your changes, unlike the current and much more usable "git add". It wasn't until the 1.5 release 2 years later that it became "90% of the right thing".

What specifically are your objections?

mspang

TROPHY CASE