News for hackers. Stuff that matters.
Re:Cheap and Nasty by kabdib on Saturday June 18, 2011 @09:52AM (#2668635)
I was at a startup in 94/95 where we made something a lot like protocol buffers, with a multi-platform, multi-language (Java / C++ / COM) API on top of it. Was very friendly -- very JSON-like -- and worked really well, up to tens of thousands of messages a second through then developer-class Pentium boxes.

I think you can still go fast without being nasty. Whether there is money in it is another question.

Re:Cheap and Nasty by nas on Saturday June 18, 2011 @03:12PM (#2669281)
Another real-world example: SMTP vs QMTP (http://cr.yp.to/proto/qmtp.txt). IMHO, saving space by packing bits is not really so important anymore since nearly every link has high-bandwidth. Reducing latency by reducing round-trips is huge though.
Re:Cheap and Nasty by Stiffy on Saturday June 18, 2011 @09:44AM (#2668618)
Something is wrong with the styling of that page. In Chrome, Firefox and IE the first few paragraphs overlap some of the panels on the right, making it very unreadable.
Re:Cheap and Nasty by ramchip on Saturday June 18, 2011 @05:01PM (#2669532)
It's broken on Opera as well. That doesn't make a lot of working browsers...
Re:Cheap and Nasty by Luyt on Saturday June 18, 2011 @11:38AM (#2668810)
Indeed - but when I clicked the Readability button (it's a FF addon) the site was easy to read.
Re:Cheap and Nasty by staktrace on Saturday June 18, 2011 @05:15PM (#2669564)
Also available as a bookmarklet for other browsers.
Re:Cheap and Nasty by VMG on Saturday June 18, 2011 @12:21PM (#2668899)
looks fine here (linux chromium 12 w/ adblock)
Re:Cheap and Nasty by Anm on Saturday June 18, 2011 @01:19PM (#2669044)
also, very mobile unfriendly
Re:Cheap and Nasty by arethuza on Saturday June 18, 2011 @03:46PM (#2669364)
Re:Cheap and Nasty by dfox on Saturday June 18, 2011 @09:21PM (#2669947)
Anything from completely brain-damaged (XER) over cheap (GSER or BER, depending on whether you want widely-used or human-readable) to nasty (PER) depending on what encoding rules you use.