APAfter analyzing the?draft needs of all 32 teams, PFT will review how well each team addressed those needs. Up next: The New York Jets.
What they needed: Quarterback, pass rusher, wide receiver, tight end, safety, offensive line
Who they got:
Round 1: Dee Milliner, CB, Alabama;?Sheldon Richardson, DT, Missouri
Round 2: Geno Smith, QB, West Virginia
Round 3: Brian Winters, G, Kent State
Round 5: Oday Aboushi, OL, Virginia
Round 6: William Campbell, G, Michigan
Round 7: Tommy Bohanon, FB, Wake Forest
Where they hit:?Nick Saban won?t like that I?m writing this, but Milliner fills the hole (on paper, anyway) opened by the trade of Darrelle Revis. Winters, Aboushi and Campbell definitely help an offensive line that badly needed younger bodies to increase the talent level and competition for jobs during offseason work. Bohanon fills the need for a player who could conceivably be called ?T-Bo? if and when the Jets finally say goodbye to Tim Tebow.
The mess the Jets have made at quarterback obscures it a bit, but it was worth the shot on?Smith at the 39th pick. He may not wind up being the long-term answer for the Jets, but acquiring him allows the Jets to move on from Mark Sanchez and that?s a win for the team right now. It?s easier to let Smith learn from the bench if David Garrard is the guy taking snaps than it would be if Sanchez were getting booed off the field every week, if only because it sells the idea that there are no quick fixes for a team that needs a total overhaul.
Where they missed: Where are the pass rushers? Richardson is a good player and Rex Ryan will put him to good use, but there?s still no one who scares you coming off the edge. Maybe Quinton Coples gets more time in that role with Richardson on board, but it wasn?t an area they addressed directly.
Where are the receivers? Another reason to resist starting Smith would be the total absence of new offensive weapons added over the three days of the draft. The Jets had their eyes on Tavon Austin, but no one else tempted them once he went to St. Louis and the receiver situation with the Jets is still an ugly one.?No safety either, as the Jets left several of their biggest needs unattended.
Impact rookies: Milliner will be expected to start from day one, which means he?s got to take as much time as he needs to be fully healthy after surgery to repair a torn labrum. He won?t be Revis, but the Jets will be strong at corner all the same if he?s ready for the NFL. Richardson is going to play a lot, although his exact role will be defined once the Jets start working as a team. Winters will probably challenge Stephen Peterman for a starting spot at guard. He and Aboushi can also play right tackle, where Austin Howard is hardly irreplaceable.
Long-term prospects: With Ryan?s future beyond this year up in the air, it?s hard to know what to make of the Smith pick. Is he going to have to learn two offenses in two seasons while playing under a coach who doesn?t want him? Or does picking a quarterback who most believe needs some time and the two defensive pieces in the first round signal a desire to stick with Ryan beyond this season? The other picks are guys who can work under any system, more or less, but the quarterback will certainly be impacted one way or another. And the quarterback will ultimately decide how things look in the long term for all involved.
taylor allderdice mixtape andrew bogut monta ellis wiz khalifa taylor allderdice mixtape reggie wayne taylor allderdice vincent jackson
John Aravosis
Some developers got very angry and threatened to leave?mobile app backend platform Parse?when it was bought by Facebook yesterday. Hoping to capitalize, competitor StackMob has since released a Parse migration tool that makes it easy for devs to import their Parse apps. It’s a cutthroat game, this game of tech. When the Parse acquisition was announced, disgruntled developers flocked to Twitter, Hacker News, and our comments reel. Facebook pledged not to screw up the beloved development platform. While it won’t operate independently like Instagram, Facebook’s hands-off approach to the photo sharing app it bought a year ago should instill some confidence. Facebook’s director of product management Doug Purdy said in his statement about the acquisition that “We?ve worked closely with the Parse team and have seen first-hand how important their solutions and platform are to developers. We don?t intend to change this.” On the phone with me he reiterated that Facebook doesn’t intend to mess with a good thing. Still, developers’ complaints I read centered on two fears: 1. That Facebook would degrade the Parse service, potentially by?promoting?its own social integrations and app install ads too hard, and 2. That Facebook would spy on data coming into Parse, including what types of content people chose not to post to the social network. Wasting little time, Stackmob launched an auto-importer for developers looking to move their apps elsewhere and published a blog post touting its advantages over Parse. StackMob CEO Ty Amell tells me the company had already been tinkering with a Parse importer, but when the acquisition was announced, it finished it up and made it accessible yesterday alongside a step-by-step guide. Then today the company began offering a Python script that turns the multi-step process into a single step. Amell explained to me, “Over the last few months we’ve seen an increase in people coming over from Parse. Once we heard they’d been acquired, we knew there was going to be a lot of backlash and uncertainty from mobile developers.?Facebook has a history of monetizing other people’s users, and charging through ads and other ways to access users. Parse not being independent any more is a pretty large concern for developers.” He says developers had two main questions about the acquisition. 1. Do developers still own their data? 2. What rights to privacy do developers have, and how will Facebook use their data? Amell says “Facebook has some pretty
