fr0sty

One interesting fact (which is not quite intuitive) is that one way they improved the WiFi network performance was by disabling the radios on a number of the access points in the hotel.

Less is more in some circumstances.

Not sure about you, but my gas bill is $/therm(~100 cu ft) and my water bill is $/100gal.

Pricing data in MB (or KB!) is like billing for water by the cup (or Teaspoon!).

A stock will have a single "primary" exchange. This is where the stock is "listed" (apple is listed at NASDAQ, for instance).

However a stock may be traded at multiple exchanges (BATS, NYSE, NASDAQ, DirectEdge, etc) as well as other market centers.

Hope that helps...

> but probably more than one can output from a small backpack of batteries like in the vid ;)

Actually, Lithium-Polymer battery packs capable of a sustained output in excess of 2kW weigh only a few pounds.

> I could easily imagine everything going the other way if Linus or DHH had picked Mercurial instead of Git.

Just picking a nit, but Linus didn't just choose it, he wrote it. Also, Mercurial wasn't an option for him because it didn't yet exist.

they are in the ./t/ directory in the repository.

Look for more information in the README file: ./t/README

It is not, to my knowledge, possible to commit directly to github. You can create a commit locally and push it to github, sure, but that is not the same thing.

What commands do you use to accomplish this?

> I, for one, will get nothing out of Cameron traveling to the bottom of the ocean that drop cameras have not already produced.

This is true only if you assume that the advances being made in materials and technology will not have applications beyond deep water manned submersibles.

As a comparison: Do you contend that you got nothing out of the development of manned space flight?

The problem with comparing the situation in the US to " the little-known country called the United Kingdom" is that the UK is peopled mostly by the British and _not_ by americans.

This small fact seems to evade most people's comparative analyses and renders them largely void.

Does anyone know how they are planning to sell off the first batch?

If they do anything besides some manner of dutch auction they will be leaving a lot of money on the table for enterprising folks to pick up by reselling them on eBay.

A vendor software push is risky even if well tested...

> "something that causes something to lose all function and become inert"

add "suddenly and without warning" and I'd agree with that definition.

I wonder if as much digital ink would have been spilled on this whole kerfluffle if the original article had not used the term 'bricked'.

Bricking, at least in my mind, is something that happens suddenly usually when attempting something at least slightly risky. Jailbreaking iPhones, replacing your laptop harddrive, desoldering components in an audio amplifier and other 'warranty voiding' all carry some 'bricking' risk.

The situation with Tesla is more akin to leaving your (very expensive) bike out in the rain: Given enough time it will rust up and need to be extensively repaired but I don't think you would say you 'bricked' it...

> I've found it distressingly easy to kill changesets in Git unintentionally.

Mind if I ask how you manage to easily kill changesets in a 'distressingly easy' manner?

In my experience it is somewhat difficult inadvertently lose commits (especially to lose them for good) unless you go out of your way to do so.

I think the $25 price point is a major draw. Your example board with fewer features is $60...

Yes, but only if:

1. All existing hardware and software magically vanishes

2. The government is put in charge of implementing its replacement.

3. The whole system is a dead-weight loss which exists to serve the whims of government oversight rather than facilitate commerce.

Forgive my ongoing skepticism, but where are these codes? on the boarding pass? Who is at the gate to turn you away? Does the TSA chase you down when they discover you have outwitted them?

> "they check the codes"

And what codes are these? the pen-squiggle? the highlighter-check-mark?

Is it your hobby to try to sneak past TSA checkpoints? Are you successful often enough that you have been turned away at the gate for not having the proper 'codes'?

The real danger is someone figures out how to spoof a legitimate request to the TSA-QR service and have them create authentic codes with bogus data.

Never mind that the solution itself is far from 'easy'. Somehow linking every ticket printer to a central TSA-QR service in a reliable and secure way sounds like, uh, fun...

And as we all know, there is no way to generate your own 2d barcodes...

"Quisler" is a non-sequiter. Quisling was a quisler and Obama championed obamacare and Savage wanted to create a vulgar definition of a man's name. One of those is not like the other...

If "Quisling" meant "a man in drag", "pile of manure" or something less tasteful then you may have a point.

> I... usually just `git reset --hard`

This is still risky if your ~/.git had uncommitted changes. I'll admit to being a little paranoid but I spent enough time on the #git irc channel to learn that any advice that is potentially dangerous will _always_ be used in the dangerous fashion, often without knowledge of the risks. > although I think you meant GIT_WORK_TREE, not GIT_WORKDIR, right?

Yeah, brain cramp on that one, sorry.

Do you intend to never use 'git clean -x...' anywhere in your home directory? when you run 'git <command>' git will go upward through the directory tree until it finds a .git directory. If you intend to run 'git clean -fx' in ~/foo/project/src but are instead in ~/foo/tmp/src/ (which is not a git repository) it will run that clean against all of ~/ instead.

Having ~/dotfiles/.git and aliasing a command that sets GIT_DIR=~/dotfiles/.git and GIT_WORKDIR appropriately would be safer.

That could work, but where would the .git/ directory be? If you have in $HOME/.git you are inviting disaster with an errant 'git clean...' command. If not you need to deal with managing the options/environment to make the git commands work (though that could be scripted).

I'm curious about this too since something dead simple (and reasonably idiot-proof) would be useful to me as well.

And by "phone" I mean "always-on internet-connected portable computer". Come to think of it that may be the source of the dissatisfaction: thinking of your device as a phone rather than a portable computer that also makes phone calls.

What would be the refill/recharge time for this car? Is the alternative to have a 100gallon gas tank or towable battery array?

I can charge my phone in under an hour. I can do so in the car, at my desk, or any of hundreds of other places given the ubiquity of micro-usb. For me, once I can go all day on a charge any excess capacity just means more weight/bulk.

A week-long battery would be obscenely large, the phone unnecessarily heavy all while providing nearly zero benefit to my use case.

What is the use-case for the one-week battery? I plug my phone in every night when I go to bed and this has not seemed overly onerous.

Why do we need a "more sophisticated" source of DC power? What would that even look like? 12VDC is 12VDC. Are current 120VAC (or whatever your mains voltage) similarly unsophisticated?

Besides, with an install base that numbers in the hundreds of millions and most of which have well over a decade of useful life.

And if SOPA passes you will see suspiciously simil overzealuos attempts to stop piracy. Same song, different verse but this time you get the federal government involved which is a whole new level of fun.

A world in which the state mandates that your work day begins before the sun rises...

Where do I sign up??

sarcasm off

I'm not sure that quite qualifies as "normal looking"...