Recent submissions

Comment · 9 months ago
That doesn't sound like the actual issue, or am I not understanding it correctly?
Comment · 6 years ago
This talk https://talks.golang.org/2019/playground-v3/playground-v3.sl... on the golang playground has some details on its security considerations.
Comment · 12 years ago
Comment · 13 years ago
Comment · 13 years ago
Comment · 13 years ago
This looks fantastic and the timing couldn't have been better for me. It's been a while that I started a new Django project and I was looking for exactly this type of best practices just this afternoon.
Comment · 14 years ago
Probably https://developer.apple.com/videos/wwdc/2012/?id=243 I haven't watched it yet, but it's been on my to-watch list for a while now.
Comment · 14 years ago
> Why would we have thought that they would sell the new adapter any different then the old 30 pin?

Before the new connector was announced there were rumours that licensing for it would be more restrictive. Also notice how you can't license MagSafe at all.

I'm not saying Apple's decision is the right one, but IMHO it was clear there was a risk regarding licensing.

Comment · 14 years ago
They've been live streaming the iTunes festival too. I wonder if they are using this to test their streaming infrastructure ...
Comment · 14 years ago
IMO directly viewing the videos in safari and not having YouTube.app hijack the links actually makes for a better experience overall.
Comment · 14 years ago
http://www.apple.com/osx/specs/ lists the following macs as supporing AirPlay

  * iMac (Mid 2011 or newer)
  * Mac mini (Mid 2011 or newer)
  * MacBook Air (Mid 2011 or newer)
  * MacBook Pro (Early 2011 or newer)
I remember reading that AirPlay mirroring uses the video encoding capabilities of SandyBridge CPUs, but I can't find a source for that now. Anecdotally, http://airparrot.com really taxes my 2010 MacBook's CPU.
Comment · 14 years ago
Also keep in mind that AirPlay mirroring requires at least a Sandybridge CPU, so you need a mac released in 2011 or later.
Comment · 14 years ago
When I ran into this problem I simply added a post-checkout hook that deletes *.pyc files within the git root.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton