You just jogged my memory about WoW (Windows on Windows) :)

It was in the works after Full Throttle's success, but was cancelled. I don't know the reasons.

There was actually more than one attempt at a sequel (Payback, Hell on Wheels) which were mostly "cash ins" outsourced by LucasArts and focused on more of the action-y stuff (FPS were just becoming the overriding rage in games) rather than the story telling. Tim Schafer, of course, moved on to Grim Fandango was not involved in the sequel attempts.

New rumors are that Tim himself is considering ideas for a Full Throttle 2 once they finishing remastering Full Throttle, but take those rumors with a giant grain of salt.

One entry way into the giant rabbit hole of old Full Throttle 2 news:

http://www.bing.com/search?q=full+throttle+2+site%3Amixnmojo...

Here is a good article: https://quarterly.camposanto.com/the-art-of-fiction-3-tim-sc...

I'd love to see a new Full Throttle, but it would be sad to hear a new voice for Ben, who died not long after the original was released.

Back up. Time to migrate!

My sympathies to any workers displaced by these events, but I'm happy. Parse is a bad product: it has weird quirks in normal usage but most importantly scales abysmally. I'm thrilled to have ammunition to justify moving away from it. Love love love the open source angle however, and wish more sunsetting products go this route.

Concord, MA USA (soon Cambridge, MA USA) KAYAK Software Corporation

Mobile engineers, iOS

Hi all. Kayak is a world leader in travel search and our iOS app is #1 in the App Store. Help us keep it that way by building out exciting new features and relentlessly polishing our existing ones. You should have iOS and network experience along with a deep desire to grow and perfect your skill sets. We have a very small team we are looking to grow, so talented juniors all the way to principal architects are welcome. We have a flat organization, give people tons of responsibility and autonomy, pay well, and enjoy lots of perks.

If this sounds good feel free to reach me directly at mdurgavich+hn@kayak.com

My issue with masonry is that it's a paper thin abstraction over auto layout. There's some nice syntactic sugar, like chained calls to layout rules. Ultimately I think there's room for some containers that give up flexibility in exchange for simplicity in code and mental model

Thoughts? Does anyone care?

Honestly some screenshots would go quite far. Some of us aren't that familiar with Swift.

The idea could be cool, but that README needs some work. See, http://scoreme.report

Two great points. I'll address.

That's all you need to do to make money on stocks, or bonds, or any other speculative trade. The trick is being consistent :)

Sure. The point is that mining wouldn't have helped if you sold at the wrong moment.

There is a difference between "shit talk" and rooting out personal contact information to then send death or rape threats. I don't think anyone expects an experience akin to high tea with the Queen, but no one deserves to be threatened. Everyone, consciously or not, wants respect.

It's simple in theory but hard in practice. It likely has to come from guidance. As a parent, I expect I will have to teach her how to engage with people both on and offline.

There's a reason we force kids to line up and shake the opposing team's hands after a soccer game.

>There is a difference between "shit talk" and rooting out personal contact information to then send death or rape threats.

Of course there is. The problem with this conversation is that it appears to be a polymorphic one. Which of the two are we talking about? I would imagine that there is no consensus on this.

Realizing you had more options at your disposal because you were not submitting to the App Store was a cool hack.

Thanks! To make it a little more clear just how much the hack helped: wait times went from around a minute (often many minutes) to ~5 seconds.