brianolson

19 ms·

151.
by brianolson 11y ago
moderator should add (2014) tag to title as article is fully two years old from February 7, 2014.
152.
by brianolson 11y ago
Large engines (in giant container ships) are supposed to be approaching the efficiency limit according to theoretical thermodynamics. Does this get small engines close to the limit?
153.
by brianolson 11y ago
Python is fine. I just came off a job in it and interviewing around saw a couple other jobs in it. I see it competing with Ruby and server-side-js. Python is more mature than either, and has a different flavor that will appeal to some peopl
154.
by brianolson 11y ago
If you're going to send structured records and care about knowing the structure: use protobuf. If you're going to be binary JSON: use RFC 7049 CBOR. http://cbor.io/
155.
by brianolson 11y ago
Fixed that last night. Good to go now.
156.
by brianolson 11y ago
I wrote the Python CBOR implementation you get if you `pip install cbor`. Source project here: https://bitbucket.org/bodhisnarkva/cbor It's getting pretty extensive use at a few places I know, so I hope it's
157.
by brianolson 11y ago
I have implemented CBOR for Python and Go. In my testing: CBOR+GZIP is slightly smaller, about 10%, than JSON+GZIP CBOR also parses faster, sometimes as much as 3-5x speedup. I'm not sure what 'ambiguous decoding' you're
158.
by brianolson 11y ago
The first graph I saw was that a poll of Clojure fans shows they like the language features in it. This of course fails to survey the people not using it and why not, and what undesired features prevent them from using it or what lack of fe
159.
by brianolson 11y ago
You could probably post that comment verbatim on half the threads in HN and get upvoted.
160.
by brianolson 11y ago
Another "Go isn't Haskell/Rust" rant. I agree Go lacks macros/templates/generics and should fix at least one of those, but mostly this is a bunch of whining wishing that Go was Haskell or Rust.
161.
by brianolson 11y ago
A better title would have been "Terribly Non-Scientific Science Fiction Tropes", still amusing rant though. Maybe even better is the link at the end to the "Turkey City Lexicon" list of common failings in SF/F writi
162.
by brianolson 11y ago
This is a good article with lots of links that I'm going to have to follow. One 'danger' with the types of statistical tests that the author favors is that districting may be subject to gerrymandering towards supposedly good
163.
by brianolson 11y ago
Here's a better algorithmic non-gerrymandered districting, solving for compactness: http://bdistricting.com/2010/
164.
by brianolson 11y ago
"Big" is apparently still limited by the 32TB table size limit in PostegreSQL. My last job was running into this. Sadly we didn't get rigorous metrics, but the database 'felt' slower when it got over .5 TB. The proc
165.
by brianolson 11y ago
this appears to be somewhere between timecube and bronner soap
166.
by brianolson 11y ago
The contract for append() has _always_ been that it might return the original pointer or it might copy-and-extend into a new pointer. That you can keep a reference of the previous version is programmer error for not having clear ownership o
167.
by brianolson 11y ago
This is replacing "Amazon Supply" which was the acquisition of smallparts.com , which was one of the best ways I knew to get a box of just the right bolts. But now they're closing that down and folding it in to this other thi
168.
by brianolson 11y ago
New thing here: NVMe SSD! I've read a bunch of other reviews and none mentioned that. Kudos to AnandTech for thinking about that detail. Thinking about that in conjunction with the storage benchmarks is interesting, faster in most test
169.
by brianolson 12y ago
See also RFC 7049 "Concise Binary Object Representation" (CBOR), a 'binary JSON' http://tools.ietf.org/html/rfc7049 http://cbor.io/ Faster, smaller, pretty sure it will parse on the
170.
by brianolson 12y ago
I grew up in Los Alamos in the 1980s and 1990s and the detailed history of what happened on the receiving end in Hiroshima and Nagasaki is still mostly glossed over. The story told is more about the heroic wartime feat of engineering that w
171.
by brianolson 12y ago
I was hoping for deeper tech dirt and architecture commentary from eetimes. This article didn't say anything I didn't read in Ars Technica yesterday. :-/
172.
by brianolson 12y ago
The first point "no generics, no code reuse" is the best one. Go really needs generics/templates/macros or _something_. It doesn't even have subclassing, although you can kinda extend a type if you only use its publ
173.
by brianolson 12y ago
For another binary-JSON, see "CBOR" Concise Binary Object Representation, IETF RFC 7049 http://cbor.io/ I wrote Python and Go implementations of CBOR. It packs smaller and parses faster than JSON.
174.
by brianolson 12y ago
I wanted the punch line to be, "The Time Lords showed up and insisted we halt all experimentation."
175.
by brianolson 12y ago
Title is going to need more data to get me to click on this. Stop punishing your users ... with ugly color schemes? ... with UI of many useless clicks? ... with full motion video autoplay ads?
176.
This computer programmer solved gerrymandering in his spare time(washingtonpost.com)
5 points by brianolson 12y ago|0 comments
177.
by brianolson 12y ago
See also : http://mercurial.selenic.com/wiki/WhatsNew#Mercurial_3.0-rc_...
178.
by brianolson 13y ago
note: (2006)
179.
by brianolson 13y ago
Alternative algorithmic redistricting optimizes for compactness: http://bdistricting.com/2010/