Comment author: gjm 21 May 2015 02:38:48AM 2 points [-]

What more useful thing would you be doing with that time, if you weren't wasting it on pushing buttons?

Comment author: kpreid 21 May 2015 02:26:14PM *  0 points [-]

Good question.

I could spend it looking at other parts of the world around me, something I don't do as much of as I ought. I could spend it thinking about whatever I was thinking about before that moment. (Of course, it's possible to do these things while still pushing the button, but as we know human brains aren't perfect multitaskers.)

(The cost is also not just in time: it also wears out the button and my hands a tiny bit more than necessary.)

Comment author: CBHacking 05 May 2015 07:52:18AM 4 points [-]

You're also talking about fundamentally different kinds of rocket boosters. The Space Shuttle used solid fuel boosters, which are basically nothing except a tube packed full of energetically burning material, an igniter to light said material, and a nozzle for the generated gases to come out. They couldn't throttle, couldn't gimbal, couldn't shut off or restart, didn't use cryogenic fuel so didn't need insulation, didn't rely on pressurized fuel so they didn't need turbopumps... In fact, as far as I know they basically didn't have any moving parts at all!

You ever flown a model rocket, like an Estes? That little tube of solid grey gritty stuff that you use to launch the rocket is basically a miniature version of the solid fuel boosters on the Space Shuttle. The shuttle boosters were obviously bigger, and were a lot tougher (which made them unacceptably heavy for something like the Falcon 9's first stage) so they could survive the water landing, but fundamentally they were basically just cylindrical metal tubes with a nozzle at the bottom.

Despite that, reconditioning them for re-use was still so expensive that it's unclear if the cost was worth it. Now, of course, they cost a lot less to build than a Falcon 9 first stage, but every one of the Falcon 9 first stage's nine Merlin 1D engines is many times as complicated as the entire solid booster used on the Space Shuttle. Even the first stage tank is much more complicated, since it needs to take cryogenic fuels and massive internal pressurization.

Comment author: kpreid 21 May 2015 01:43:17AM 2 points [-]

This isn't all that relevant, but the Shuttle SRBs were gimbaled (Wikipedia, NASA 1, NASA 2).

(I was thinking that there is probably at least a mechanical component to arming the ignition and/or range safety systems, but research turned up this big obvious part.)

Comment author: kpreid 21 May 2015 12:40:57AM *  0 points [-]

I've decided to work on getting rid of a trivial useless habit: pushing pedestrian crossing buttons more than once.

Now, there's an argument that it's not completely worthless to do so: the typical button has no feedback whatsoever that it's recognized my push, so if it is at all unreliable then an extra push reduces the chances of a complete extra cycle wait at little cost to me since I have nothing else to do.

But the failure case has never actually happened in recent history, so I'm spending too much time pushing buttons.

So far I have remembered to push only once out of about ten times (2-3 per day). Of course, I immediately remember this resolution right after pushing twice.

Comment author: gjm 05 April 2015 08:47:53PM 0 points [-]

I agree that a cache can be thought of as involving names, but even if -- as you suggest, and it's a good point that I hadn't considered in this context -- you sometimes have some scope to choose how much information goes into the keys and hence make different tradeoffs between cache size, how long things are valid for, etc., it seems pretty strange to think of that as being about naming.

Comment author: kpreid 06 April 2015 02:02:57PM 0 points [-]

Well, as iceman mentioned on a different subthread, a content-addressable store (key = hash of value) is fairly clearly a sort of naming scheme. But the thing about the names in a content-addressable store is that unlike meaningful names, they say nothing about why this value is worth naming; only that someone has bothered to compute it in the past. Therefore a content-addressable store either grows without bound, or has a policy for deleting entries. In that way, it is like a cache.

For example, Git (the version control system) uses a content-addressable store, and has a policy that objects are kept only if they are referenced (transitively through other objects) by the human-managed arbitrary mutable namespace of “refs” (HEAD, branches, tags, reflog).

Tahoe-LAFS, a distributed filesystem which is partially content-addressable but in any case uses high-entropy names, requires that clients periodically “renew the lease” on files they are interested in keeping, which they do by recursive traversal from whatever roots the user chooses.

Comment author: gjm 30 March 2015 12:40:16AM 1 point [-]

At least one of us is confused. It never occurred to me that the original comment was intended as a joke (except in so far as it's a deliberate drastic oversimplification) and I don't think I understand what you mean about cacheing being subsumed by naming (especially as the alleged hard problem is not cacheing but cache invalidation -- which seems to me to have very little to do with naming).

I'm probably missing something here; could you explain your interpretation of the original comment a bit more? (With of course the understanding that explaining jokes tends to ruin them.)

Comment author: kpreid 05 April 2015 07:49:24PM 1 point [-]

cache invalidation -- which seems to me to have very little to do with naming

I don't agree with Douglas_Knight's claim about the intent of the quote, but a cache is a kind of (application of a) key-value data structure. Keys are names. What information is in the names affects how long the cache entries remain correct and useful for.

(Correct: the value is still the right answer for the key. Useful: the entry will not be unused in the future, i.e. is not garbage in the sense of garbage-collection.)

Comment author: iceman 24 March 2015 09:05:28PM 1 point [-]

To speak to the second of naming things, I'm a big fan of content addressable everything. Addressing all content by hash_function(<the content>) has major advantages. This may require another naming layer to give human recognizable names to hashes, but I think this still goes a long way towards making things better.

You might find Joe Armstrong's The Mess We're In interesting, and provides some simple strawman algorithms for deduplication, though they probably aren't sophisticated enough to run in practice.

(My roomate walked in while I was watching that lecture when I had headphones on, and just saw the final conclusion slide:

  • We've made a mess
  • We need to reverse entropy
  • Quantum mechanics sets limits to the ultimate speed of computation
  • We need Math
  • Abolish names and places
  • Build the condenser
  • Make low-power computers -- no net environmental damage

And just did that smile and nod thing. The above makes it sound like Armstrong is a crank, but it all makes sense in context, and I've deliberately copied just this last slide without any other context to try to get you to watch it. If you like theoretical computer science, I highly recommend watching the lecture.)

Comment author: kpreid 05 April 2015 07:39:38PM 0 points [-]

To speak to the second of naming things, I'm a big fan of content addressable everything. Addressing all content by hash_function(<the content>) has major advantages. This may require another naming layer to give human recognizable names to hashes, but I think this still goes a long way towards making things better.

It also requires (different) attention to versioning. That is, if you have arbitrary names, you can change the referent of the name to a new version, but you can't do that with a hash. You can't use just-a-hash in any case where you might want to upgrade/substitute the part but not the whole.

Conversely, er, contrapositively, if you need referents to not change ever, hashes are great.

Comment author: Bill_McGrath 10 March 2015 08:59:58PM 6 points [-]

Does anyone have any good web resources on how to be a good community moderator?

A friend and I will shortly be launching a podcast and want to have a Reddit community where listeners can interact with us. He and I will be forum's moderators to begin with, and I want to research how to do it well.

Comment author: kpreid 15 March 2015 02:22:39AM *  1 point [-]

Here is a thing at Making Light. There are probably other relevant posts on said blog, but this one seems to have what I consider the key points.

I'll quote some specific points that might be more surprising:

\5. Over-specific rules are an invitation to people who get off on gaming the system.

 

\9. If you judge that a post is offensive, upsetting, or just plain unpleasant, it’s important to get rid of it, or at least make it hard to read. Do it as quickly as possible. There’s no more useless advice than to tell people to just ignore such things. We can’t. We automatically read what falls under our eyes.

\10. Another important rule: You can let one jeering, unpleasant jerk hang around for a while, but the minute you get two or more of them egging each other on, they both have to go, and all their recent messages with them. There are others like them prowling the net, looking for just that kind of situation. More of them will turn up, and they’ll encourage each other to behave more and more outrageously. Kill them quickly and have no regrets.

Comment author: maxikov 05 February 2015 07:12:15PM 2 points [-]

If the effect of RF doesn't go beyond thermal, then you probably shouldn't be concerned about sitting next to an antenna dish any more than about sitting next to light bulb of the equal power. At the same time, even if the effect is purely thermal, it may be different from the light bulb since RF penetrates deeper in tissues, and the organism may or may not react differently to the heat that comes from inside rather than from outside. Or it may not matter - I don't know.

And apparently, there is a noticeable body of research, in which I can poke some holes, but which at least adheres to basic standards of peer-reviewed journals, that suggests the existence of non-thermal effects, and links to various medical conditions. However, my background in medicine and biology is not enough to thoroughly evaluate this research, beyond noticing that there are some apparent problems with that, but it doesn't appear to be obviously false either.

Comment author: kpreid 07 February 2015 05:47:37PM 2 points [-]

next to an antenna dish any more than about sitting next to light bulb of the equal power.

Nitpick: A dish antenna is directional, a typical light bulb is not. For a fair comparison, specify a spotlight bulb.

Comment author: solipsist 02 February 2015 03:03:35PM *  10 points [-]

A lot of math and physics definitions feel like they have weird dross. Examples:

  • The Gamma function has this -1 I don't understand
  • The Riemann Zeta function ζ(s) negates s for reasons beyond me
  • cosine seems more primitive than sine
  • The gravitational constant looks like off by a factor of 4π
  • π seems like half the size it should be

After years of confusion, I was finally vindicated about π. That π is not 6.2831853071... is mostly a historical accident. Am I "right" about these other definitions being "wrong"? What are other mathematical entities are defined in ugly ways for historical reasons?

Comment author: kpreid 04 February 2015 04:43:41AM 4 points [-]

I'd like to put in a word for sine:

sin(0) = 0
sin(x) ≈ x

These are highly useful properties in some contexts. That said, cos(0) being the unit prior to any rotation is also nice. (But the definition of a rotation in Cartesian coordinates contains exactly as many sines as cosines; and that generalizes to 3 dimensions where complex numbers do not.)

Comment author: Vaniver 22 January 2015 05:33:30AM 6 points [-]

It is 11:30 by my clock, so published on Wednesday, though perhaps not at the time I had in mind ;)

Thanks again to Ari Rabkin, Peter McCluskey, Christian Kleineidam, Carlos Serrano, Daniel Light, Harsh Pareek, and others for helpful comments on drafts.

An amusing typo I discovered while proofreading one of the new parts of this post: one sentence originally read "when presented with a choice, it is often better to make out than not make one." Words to live by.

Comment author: kpreid 23 January 2015 04:38:55PM 1 point [-]

Another typo: first paragraph, “effect used” → “effort used”.

View more: Prev | Next