guywithabike

Incorrect. You see a flash because the new image has't been loaded yet, but all the other images have been previously loaded and cached, so your browser can display them almost immediately.

Try going back to page 1 — each page will appear to load instantly if you have all the images cached.

This was caused by their scheduled maintenance: https://status.heroku.com/incidents/641

I think they jinxed themselves: "Running apps will not be affected."

A lot of cell phone purchasers can't front the $199 up front. The amount of money you need to plonk down on day one is a big factor for a lot of people (usually people with low incomes). Of course, generally these "0-down" types of pricing models are basically scams that prey on people who can't pay large sums up-front.

It's a shady business model that, unfortunately, works well for the businesses that use it.

In my experience, people who've had exorbitant numbers of kernel panics on Macs have had tons of things installed that muck around with MacOS X internals. VirtualBox, old SIMBL hacks, manual fan controls, etc. Those are all notoriously unstable and can cause lots of kernel panics.

(Author here) Correct -- this post is more about exploring RESP and why it's a neat protocol by implementing a very basic RESP reader. I wouldn't write a new Redis client unless I wanted to do something significantly different than the existing, battle-tested Redis clients like Redigo. This is the reason the code exists only in the blog post rather than in a GitHub repo that can be imported.

Besides, reading RESP objects is only the very first step in implementing a true Redis client. You need to handle response types (null bulk strings, null arrays, etc), opening TCP connections and handling errors therein, and offer up a sane API for end-users. And that's definitely outside the scope of the blog post. :)

(Author, here.) I also recommend garyburd/redigo. I especially like the API. Instead of adding methods for every Redis command, redigo uses a single Do() method and then has several "type helper" methods that allow you to convert the response to various types simply by wrapping Do():

    value, err := redis.String(client.Do("GET", "mykey"))

Of course, this means you need to know about every command's response type and adds an extra (if small) level of verbosity, but in practice it fits very well with Go's philosophy of handling errors often and early. So, for instance, you're encouraged to handle the possibility that your key doesn't exist rather than barreling ahead with an empty string.

It's open source. You provide the support and updates.

Steve was also adamant about not doing a phone in the first place, not doing a tablet, etc. The point being that Steve always publicly denied wanting to do something that privately he was already investing significant resources in doing.

Numbered databases are (de facto) deprecated. Run separate processes, instead.

(Redis is single-threaded, anyways. You probably don't want to run production and staging on the same Redis process.)

Linux is not free, you still need to buy a computer.

If having "some bad luck" and living a "meaningful life" means I die of starvation / poisoning alone in a forest, then I guess you can count me out.

Looks promising? They've only announced the name. They haven't announced a single new feature.

Soylent isn't curing cancer or solving hunger. They're selling meal replacement drinks, which is a large, established market.

It's not about the website, it's about the content. If you read the articles, I think you'll be suitably blown away. Example: http://worrydream.com/#!2/LadderOfAbstraction

Read the FAQ: http://golang.org/doc/faq#generics

Generics are convenient but they come at a cost in complexity in the type system and run-time. We haven't yet found a design that gives value proportionate to the complexity, although we continue to think about it. Meanwhile, Go's built-in maps and slices, plus the ability to use the empty interface to construct containers (with explicit unboxing) mean in many cases it is possible to write code that does what generics would enable, if less smoothly.

In your estimation, what did iOS "steal" from Android?

For example, a common iOS 7 feature cited as "stolen" is the app switching interface. But that's the same interface Safari has used for switching tabs since the very first iPhone. They simply repurposed their Safari UI for the OS.

They call it an "open platform". I don't get it -- what part of their platform is open? The plugins are open source, but that's not their platform.

iOS 7 is beta software. If it was finished, they wouldn't call it a pre-release beta for developers only.

The fact that this is the World Wide Developer's Conference makes me think that developers are the targeted audience.

"the devices are often considerably more expensive"

iOS devices cost $0-$199 on contract, the same as the most popular Android devices.

Dividends and share buybacks are not defensive moves.

From TFA:

…production is set to ramp up in 2014.

Nope. This is the announcement that Go 1.1 has reached beta status.

> compared to other players

Do you have a source for this?

Don't ask for anecdotes -- test it yourself with conditions similar to those that you'd be operating under.

In one message, @humanchimp says:

    Ok thanks for closing my issue.

@humanchimp's very next comment:

    The sarcasm is not appreciated, [...]

"Of course Apple had the market share lead with the iPhone. But the category was not "smartphone". ... The iPhone became the new state of the art for smartphone."

You're contradicting yourself, there. Were pre-iPhone smartphones not smartphones? Were Windows Mobile 6 phones not smartphones? Where's your line? And anyways, Gruber's not talking about your personal definition of smartphone, he's talking about the commonly accepted category of smartphones.

Besides, what in Gruber's piece is factually inaccurate? You said his arguments "sound logical but are just wrong" but don't actually point out any inaccuracies.

"iOS has barely evolved since it was first launched"

That's like saying laptops have barely evolved since they weighed 15 pounds. iOS has evolved a hell of a lot since 2007, and it continues to do so. Just because Apple hasn't slapped new paint on it every other year doesn't mean that it doesn't continue to have new features and improvements every year.

I sucked at it for years, that's how.

To get good at design, you have to suck for a long time. You have to make a lot of sucky designs, of all kinds. Really awful, horrid stuff. You'll try hard as hell and come up with a bunch of turds for years.

But the most important part is that every time you design something, take a step back and evaluate how you could have done better. Then take that knowledge with you for your next design.

Eventually you'll start to suck less.

You do realize that HipChat is owned by... a large company, right?