A top-spec Mac Mini is pretty beastly at $1500. I have no doubt it would chew up and spit out the vast majority of workstation use cases. 2.6 GHz Quad-core i7, 16 GB RAM, SSD.

The only thing I can possibly imagine would be some seriously high-end 3D rendering or massively parallel simulation software.

To the OPs point, there is zero reason to get the Mac Pro over even a Mac Mini.

Seems like there's a hole in Apple's lineup. You can't get a discrete GPU without a monitor attached (iMac) or spending >$3000. Not that it matters much for Illustrator, Photoshop, etc. which are not GPU-parallelizable anyway. At least not yet.

These best part of the post is Tim Bray's response, where he says he would keep PUT and DELETE because they're idempotent, but declined to defend the rest.

I write tons of Java in my day job, and at this point it only hurts when I laugh.

I just wrote a REST API for my company and used PUT and DELETE (Tomcat doesn't support PATCH yet).

Plenty of DELETE in Stripe's API: https://stripe.com/docs/api#delete_recipient

Github uses HEAD, PATCH, PUT, and DELETE: http://developer.github.com/v3/#http-verbs

Twilio supports PUT and DELETE: http://www.twilio.com/docs/api/rest/request

There are all darlings of the HK community with highly praised, widely used REST APIs. Have you read through the developer docs for most APIs?

(edit: typo)

To be fair to the other poster, I wouldn't be surprised if 99.9% of requests were GET/POST/HEAD.

And 99.9% of requests are GET rather than POST, so shall we get rid of POST then?

GET and POST already have widely observed distinctions in how they should be handled. For example, try hitting refresh on a page that was arrived at via a POST request. That behaviour is pretty much common to all browsers.

His point was that at minimum you still need a GET and POST for read and write. So comparing the numbers against bike-shed implementations is moot. Of course the number of reads will be significantly higher.

You could write and read using just POST. SOAP is the living example of that. So I think his point is inconsistent.

90% of it is print statement -> function. I got pretty tired of scrolling past all that to try and find the interesting bits.

From the announcement blog post:

-Cool looking dark theme, because that’s trendy these days

I hate Forbes - interstitial ads and persistent headers are super annoying. Can we stop posting Forbes links?

Boing Boing has the same coverage with a much more reader-friendly site design: http://boingboing.net/2013/07/31/nsa-capo-heckled-at-black-h...

Grrr, the Boing Boing article just links to Forbes.

HeroLight is hard to read on that background and looks rough around the edges on a non-retina screen.

Click through to the "Quip Business" page - they use a Thinkpad instead. Subtle bit of "take us seriously" marketing to business types.

So who is writing an app to trigger streaming from a local network file share?

That is half of what I use my Wii for, it'd be very tempting to switch to the Chromecast for that.