I didn't say they're perfect or anywhere near perfection. I could go on at length about the myriad things that annoy me: Finder, HFS, software update crammed in the App Store, iOS lockdown.
All I did say is that they absolutely do _care_ about what's below the surface. Parts that a fraction of a fraction of folks will ever see are given loving attention far beyond the norm. Do most or any other manufacturers color coordinate battery warning labels, PCBs, etc., down to the cm^2 headphone jack?
It chronicles competing standards, proprietary efforts, attempts at sea-rail-road integration, with some lively characters thrown in. It captures the entrepreneurial vibe of the heady postwar decades. I loved it.
Indeed there is no indigenous population and hasn't been since 1966 [1]. It's nothing but a strategically well-placed airbase with a few thousand personal and contractors.
.io is clearly a gccTLD. The TLD administration and commissioner in charge of 'the government' reside in the UK.
You're right, I just re-read the judgment with the proposed wording. Apple should have gone with that verbatim and otherwise shut up so as to not drag it out.
They made what could have been a publicly boring notice buried in the page footer a spectacle.
The judgement specified where, when, and how to publish the notice down to which website and publications, the typeface, and point size.
It was sloppy to do all that and then not either properly parameterise what should be published or include a requirement that the copy be agreed or reviewed before publication.
Apple complied with the letter of the judgment and arguably the spirit of the judgment which was "not designed to punish" but rather "to dispel commercial uncertainty". It clearly states that Samsung's products were found not to infringe in England and Wales. Unambiguously. Can anyone parse that first paragraph in any other way?
Going on to provide nuance by quoting the original judge and including rulings from other jurisdictions doesn't negate that.
Apple have been foolish in getting the court's dander up, but they're not wrong.
The obvious answer is to use progressive fines, making them proportional rather than a fixed amount. For example: http://en.wikipedia.org/wiki/Day-fine
Beats me. Apple complied with a sloppy judgment. I'm no great fan of Apple in this, but the appeal judges fucked up by not clearly specifying what Apple needed to do and could not do.
"The job of an OS not a human admin. "apt-get install puppet" on the clients and "apt-get install puppetmaster" on the puppetmaster. That's about it."
It might be a simple apt-get command, but consider setting up Chef Server. You're suddenly adding the following to your system: Ruby, CouchDB, RabbitMQ, Java, merb-assets, merb-core, merb-helpers, merb-param-protection, merb-slices, thin, solr-jetty. And then maybe libxml-ruby, merb-haml, haml, coderay. (From http://wiki.opscode.com/display/chef/Installing+Chef+Server)
That's a whole heap of stuff and moving parts I wasn't looking for. Compare that to the above mentioned Ansible or cdist on the lightweight end of the spectrum.
Sorry, I don't recall in particular. It was about a year ago.
It was only a basic setup of a user account, a directory tree, and ufw. It took over a minute for either a first or subsequent run on a clean install of Natty. Considering how much more config I had to add and too little time to dedicate to investigating and speeding it up, I had to put Puppet aside.
Good to know 3.0 is a lot faster. I'll give it another look in future.
I never got on well with either. Puppet was mind-bogglingly slow (even locally without a master), both Chef and Puppet felt overwrought, and I prefer keeping dependencies to a minimum.
Just a pointer for anyone else that doesn't have much love for either: I found myself happy and productive with Salt. Fast, simple, and lets me do what I needed with less Byzantine setup: http://docs.saltstack.org/en/latest/
There's also Salty Vagrant and Salt Cloud for local and remote provisioning.
I forgot Browett came from Dixons. Everyone then said he would probably be disastrous for Apple. Looks like we were correct. I can't imagine him not being shown the door imminently after such a huge PR gaffe.
Ah hah, I forgot about Fantastical. Looks like it will do the trick for quick entry of reminders which was one of the few features I was missing after Things. (Plus there's a 50%-off sale).
Using an Fn double-tap to dictate makes it Siri-esque, only more reliable :)
I loved the original release of Things on the desktop, but wish I had never bothered with the iOS app. It took far too many taps to do anything and syncing was clunky to the point of uselessness.
It was the wait for over-the-air syncing, with months of overwrought blog posts, that led me to abandon Things. I recreated my use in the Reminders app and have been much happier since. With this 2.0 I see they have finally, years later, released "cloud syncing".
I don't see $50 worth of functionality, but still, wish them well with the new release.
I read both "What wasn't I consulted?" and "Behind a Press Release" as being very directed at this situation, neither of which were classy ways for Gruber to handle it, just snide allusions.