HN user

ulope

60 karma

[ my public key: https://keybase.io/ulope; my proof: https://keybase.io/ulope/sigs/hY6AH2TsiXIPC32bDuGfP3cFeh4aiseRzcXX8KhfDRA ]

Posts0
Comments24
View on HN
No posts found.

I just wanted to say thanks for the entertaining talk you gave at FOSDEM and also that I appreciated the Sneakers reference :)

HTTP 2.0 13 years ago

No I don't particularly want to read a 3kB JSON file without tools - but the point is: in a pinch I _CAN_.

With a binary protocol you're entirely dependent on tools (except you want to trawl through it with a hex editor)

It really doesn't need to since you aren't bound to a fixed schema. Just use whatever fields are necessary for your documents and map them to the appropriate types.

Interesting, but it's not as if hotels in general have been high security installations.

Very easy experiment: Just go to the front desk an thell them that you sadly seem to have lost your room card. 90% of the time they will just ask for your room number without requiring any kind of proof that it's actually your room.

This incident also sheds a different light on another tidbit on talk show history. In one of the earlier episodes of the 5by5 version Dan and John were talking about how Dan's recommendation of "Silent Running" to John basically ended the first run of the talk show. At the time I thought that was just a joke. But after this I'm really wondering if that supposed friendship between the two wasn't all that strong after all.

I and several of my clients use quite a few of those and I'm very happy with the performance. IO performance is very good (especially for a virtualized system) for example apt-get update / upgrade takes less time on one of those than it does on a dedicated root server of mine (Core i7 Quad, 8 GB Ram, 7.2 kRPM SATA).

Any other specific questions?

As long as the package you need doesn't include a C extension (which most don't) you can just ship it with your code (license permitting ofc.) - just add the path to the libary to sys.path. It's not a very clean solution but can be a real life saver when you have to work on "broken" systems.

Because it leads to namespace pollution and hard-to-track-down bugs.

It's especially bad in this case where adding an executable in the system can suddenly shadow any built-in name (e.g. imagine someone adds a "print" or "sys" executable).

Having read that (and assuming it's accurate) I really wonder how anyone in their right mind can see EC2 as a viable hosting solution.