triplepoint217

If I remember correctly, they carry more fuel than they need in the first stage as a safety reserve, and the plan is to use that reserve fuel to land the stage. So they actually don't pay an extra weight cost, they simply make use of margin they were including anyway. If they end up having to use their safety margin, then the rocket can't land, but in the majority of flights where things run smoothly, they get to land it.

I sent a request to their feedback email seeing if they would be open to something of that sort. Copy pasting formatting to Markdown/ReST wouldn't be too bad, but it seems to me polite to ask permission.

tldr; it works just fine.

It is a tiny bit fiddly getting the card in the right place in the adapter (basically just a little piece of plastic), but then it slots in and just works. As long as you are not dexterity challenged, it shouldn't be a problem at all. The adapter is also just a very simple bit of plastic, so buy one from amazon or ebay for a buck.

The SIM I got from a Heathrow vending machines supported all the phones by giving you a nano and then adapters up to bigger sizes.

I agree that trying to sign up elderly listeners would be an excellent idea. You will probably need a pretty strong technical support crew for them, because they in general won't have our comfort level with computers.

My father has been working to keep some older relatives able to use computers, but there are lots of challenges. A couple of points I can offer from his experience: - Tablets are probably easier use, especially if you spent some effort making a specific app. - Reliable always on internet is not necessarily a given. - Even if they have good internet, they may not have a wireless network

I think it is a slightly larger risk than that because a joker could plant say an arduino with a bluetooth shield, or an old throwaway android phone somewhere and script a program of actions, or maybe use a bluetooth antena (do those exist?)

Also, is this a specifically short range bluetooth? Because my old junky bluetooth headset still gets enough range to reach my phone in my room from the bathroom nearby.

I agree with you that the short range makes the threat much smaller, but it doesn't completely eliminate it.

I agree it is a cute hack, but it is also kind of horrifying. You are depending on an undocumented behavior that happens to be shared across the ecosystem. Now what happens if that file hits a parser which takes the first instance, or a functional one that errors out when it sees multiple assignments?

+1 re YAML

I just called.

A feature that would be really nice: A way for me to give them my email address and zip code and then get an email when vote results are posted with how my Representative voted.

The bigger problem I encountered trying it out yesterday was that it (at the moment) is fairly happy to generate an empty page and not give any compiler errors.

I assume that will change, but it made it pretty hard for me to get started with the language.

That said, I hope it changes, because Elm looks really neat!

Maybe it is possible to write a haskell mode for ipython? I watched Fernando and one of the Julia guys hack up communication between ipython and a Julia interpreter in an afternoon. Depending on how ghci is implemented it might not be much harder.

Have you considered parsing the Diabetes guidelines so that you could add an entry for people needing to follow that diet.

Fair enough. Though as later comments point out, constructing a 1tb object is probably a better failure case for functional languages. It would also be fairly easy to avoid if the True on the lhs could be evaluated quickly so you could abort the second calculation.

That kind of code is only valid in strict languages because of short circuiting, is functionally equivalent to lazyness in this respect. If you tried to automatically parallelize C by speculatively evaluating both sides you would have exactly the same problem.

Lazy languages may make this kind of code easier to write, but the problem is actually that of non-deterministic calculations, and would be a problem anywhere.

> Relying on lazy semantics also wrecks parallelism, because some evaluation branches cannot be visited ahead of time, without changing the program's semantics.

For a pure functional language, like Haskell, speculatively evaluating pieces of it in parallel shouldn't hurt anything (since they are guaranteed not to have side effects).

It is my understanding that the lazy semantics of Haskell mostly mean that you shouldn't be making any assumptions about the order of evaluation which would seem to be useful from an optimization perspective.

I am still new to FP and Haskell, so please correct me if I am misinterpreting things.

Agreed, I generate documents with graphs and calculations in them for my research, but I tend to document and automate them with python scripts rather than makefiles, because python does not make my brain hurt.

Yes, I was trying to make posts editable on the HN instance I run, so I got clever and started messing with the files in emacs. Then I learned that the HN code does not like files in the story directory with ~ on the end of their name (emacs backup files), oops ;).

I am looking forward to when we have fire and forget snapshotting system so that we all have rolling backups. I would also like the send snapshot features they have added recently for keeping multiple drives in sync (I currently use unison, but I think this could be faster/better).

Plus copy on write should be pretty cool (cp becomes as fast as mv), though I could see it allowing me to engage in some suboptimal behaviors of copying tons of stuff and counting on CoW to avoid actual duplication.

I have been running Ubuntu 12.04 with my / as btrfs for a couple of months now, with no trouble (and not even thinking about it truth be told). That said, I left my /home ext4 because I didn't know how much to trust it.

Smaller gates mean lower capacitance, so you need to drive less current into them to switch.

The nice thing about CMOS is that you only need to flow current when switching them (at other times current is blocked by an "OFF" transistor somewhere in the logic), so resistance doesn't matter as much as it would for a motor or a light.

The killer applications would probably be power transmissions (as saulrh mentions) and magnets. It would definitely help make MRI's cheaper and probably smaller, and I think it would probably help a lot with electric motors.

Easy long distance power transmission might also help with renewables (think large solar plants in the Sahara or New Mexico with superconducting lines to bring the power without loss to where we want it)