wsbail29

Cool stuff. If you are interested in creating effects like this you might also be interested in:

http://facebook.github.io/rebound/rebound-js/docs/rebound.ht...

We open sourced Rebound for Android a few months ago. It provides simple spring dynamics similar to Pop and is used to drive animations in Facebook apps like Chat Heads and FB Home.

http://facebook.github.io/rebound

http://github.com/facebook/rebound

twitter: @rebound_lib

FYI: I just merged a pull request that adds gradle support. Would love for somebody to send a pull request to add maven as well.

Thanks for the feedback. I agree that hitting a loading spinner on the home screen should never happen. Sounds like you might have encountered a cold start. Occasionally the Android OS will kill our process to relieve memory pressure. This tends to happen when you are using an app that consumes a lot of memory in the foreground and then return to Home. Improving our cold start time and adding additional protections to our process to make it less likely to be killed are things we're working on. We're also continuing to tune our ranking algorithms for showing you the freshest most interesting content when you turn the screen on. The fullscreen experience of Cover Feed presents some unique and interesting technical problems to solve, but our goal is that the most relevant and fresh content is always given the highest priority. We'll continue to tune this over time and fill in missing features. We'll be making some blog posts about the engineering of Home soon that will go into more detail on some of these areas. Thanks for your patience on the wider rollout. I'm really excited to get this in the hands of more users.

Right on. Thanks for checking it out! I'm looking forward to getting more of the features that power users look for in the launcher so we can widen our potential audience.

Hi folks. I'm one of the engineers on Facebook Home (disclaimer these are my opinions and not those of Facebook). It's been really interesting reading the early reviews. I think we can learn a lot from them.

The goal of the product is to make your phone feel more alive with content from the people you care about while still allowing you to efficiently perform all the typical tasks you use your phone for. The navigation model is a bit different than what people have become accustomed to, so some confusion is very understandable; however, we tried very hard to make access to any task just as efficient on Home as any other launcher. Getting to any app is just one gesture away: swipe up to launcher; swipe right to the last app; or double tap the home button to bring up the switcher. As user feedback comes in we'll continue to tune our model to try and achieve a nice balance between surfacing social content and completing tasks.

Home was designed and engineered by a pretty small team with a goal of releasing a high quality, performant, and beautiful product. To ensure our bar was met, we tried to narrowly focus on doing just a few things but doing them well for the first release. Of course the trade off here is that some features that people value are missing. I hope this first version will be judged on the execution of what we did include as we continue to fill in the gaps in future releases.

For anyone who has checked it out so far Thank you! I'm looking forward to making the experience something you'll love.

Here's a CoffeeScript port of this algorithm I did awhile ago.

https://gist.github.com/3733089

and a demo:

http://wsb.im/flocking/index.html

Definitely fun stuff to play around with.

Liked the shout-out to Robert Kieffer. Keep up the good work Jeremy.

This is a really nice inventory of the latest Chrome Developer Tools. I also really like the recent Settings additions of "emulate touch events" and "Override device metrics" for mobile web development.

nice implementation! The color adds a lot of visual interest. Here's my monochrome implementation.

http://wsb.im/conway/index.html

Thanks for the code review folks. I made the countNeighbors method a bit more concise and removed some unnecessary binding code from the travelWorld method.

I've been playing around with CoffeeScript and docco a bit lately and I thought I'd share this little project. Thanks to Jeremy Ashkenas for creating these fantastic tools.

It means that Backbone provides a way to cleanly separate your model/data from your presentation such that your model is concerned with synchronizing state with a server and the view is concerned with listening to changes in that model via data binding.

I really like the approach here of extracting the core functionality of js mvc and data binding without the bloat of a huge framework. I plan on using this on a project soon. Well done jashkenas and co!

My layman's idea for stopping the leak:

Insert a drill pipe into the well with some sort of expandable yet sturdy bag tucked into the end. Once the pipe is fairly deep inside the well, pump a dense liquid into the pipe expanding the bag similar to an angioplasty procedure. Then cap the well from the top once the flow is stopped or reduced significantly.

Another similar solution would be to attach high explosives to the drill pipe and collapse the well from deep inside.

Have these approaches been considered?

that's what she said

nice work guys...interesting to see a different take on the Flow as a team collaboration medium. Also, Love the flow based puns like "Flowser". At Shareflow we call the creator of the flow the "Flowner".

http://zenbe.com/shareflow

Nice job! I did something like this awhile ago too. I wrote a scraper that pulled all of the reviews from Pitchfork (scraping was necessary before they updated their site with rss feeds). My app currently just display a random set of reviews on each visit.

http://pitchforkd.thirtymontgomery.com

I was actually thinking about updating it to add playlist functionality. Thanks for pointing out 8tracks.com. I'll have to check it out.

It's true that more than 30 style tags on a production application is a big problem; however, in development mode it can be useful for debugging and maintainability to break out your stylesheets into granular modules that get concatenated at deploy time.

I've personally bumped into this limit in IE in development mode. My solution was to build a dynamic method that concatenated all the stylesheets on the fly if the IE user agent was detected.

thanks for the tip...I'll look into this!

Thanks for the great feedback. I'm Looking into the bugs.

As for the feature requests, logging in to view your personal feed and the pause button are on our roadmap and should be added soon.

You make a good point about the lead-ins. We initially had a bunch of silly lead-ins, but we've been getting consistent feedback that we should just keep it simple. We've already trimmed down the lead-ins significantly. Sounds like we should keep trimming.

Tweetrad.io is a fun little side project that converts twitter feeds into audio using text to speech.

We use a distributed network of converter bots to handle the work queue. Jobs are placed on the queue via api calls from the javascript client that interacts with twitter's search api directly in order to avoid rate limiting of a centralized search server. Our app server is a lightweight Sinatra service that handles job queueing. We stream the audio directly from our nginx web server as they become available via the conversion process.

We are trying to decide if this app has a real use case or if it's just a fun thing. One of the ideas we are thinking about is an iphone app for keeping up with your tweet stream on the go. We would love to hear your feedback.

Zenbe is hiring Java and Rails developers for our Tribeca NYC office.

http://www.zenbe.com/jobs

here's the direct link to the sourcecode for the DropManager class extracted from our work on this feature.

http://gist.github.com/153019

from the docs... The DropManager class provides a pleasant API for observing HTML5 drag-n-drop events, cleaning up the data that they return, and triggering the appropriate callbacks. With the drag and drop API so far, there are generally three types of data we're interested in: HTML, URLs, and plain text. On drop, your callback will receive a pre-processed drop object with corresponding 'url', 'html' and 'text' properties.

Hi, I'm one of the developers of Shareflow. Although we are flattered by the comparisons to the amazing work Google is doing on Wave, it's true that we are lacking some of the innovative features Wave provides (open protocol, federation, Operational Transformation data sync).

That said Shareflow was conceived of without any knowledge that Google was working on Wave and developed with limited resources on a tight timeline. When we kicked off the project earlier this year, we discussed our ideal vision for Shareflow which looked a lot like wave (open protocol, federation, pluggable widget architecture, integration with external sites); however, as a small team focused on becoming profitable, we decided to focus on getting a product out there for people to use first.

The day Google Wave was announced there was a mix of excitement, tech envy and some frustration in the office about Google releasing something similar to what we had envisioned. Now we are looking forward to the possibilities that Wave opens. A company of Google's size has the ability to push paradigm shifting innovations and new standards. As people become used to new forms of communication and collaboration I believe there will be more opportunity for products like Shareflow. The fact that Google is making Wave an open system means there will hopefully be an ecosystem of products communicating on this emerging standard. As a company focused on innovating in personal and group communication, we're following it closely.

We're continuing to build out Shareflow based on our users feedback. Thanks for checking it out!