HNHacker News
TopNewBestAskShowJobs

synxer

18 karma · joined December 10, 2010

submissionscomments
synxer··on What I think Dropbox's next move should be.
True, but I don't think it would be any more than the support provided for personal web space. The big difference of course is that Dropbox is much better, more user friendly and much more enjoyable as it is available from your desktop instead of FTP clients.

I also think Dropbox's own support system far surpases the support that most ISPs have for personal web space.

synxer··on What I think Dropbox's next move should be.
In the article I mentioned that Dropbox would have to source some costs in infrastructure. In my opinion, Dropbox with your ISP would be more beneficial for multiple accounts. Dropbox could have a control panel for ISPs to link their customers to which would allow a MobileMe-esc division of the available space. The ISP could provide Dropbox with the assigned IP address (hashed, of course) so decisions regarding the use could be handled appropriately. Outside of your ISP connection, you'd have the same access with the same experience.
synxer··on Simple Questions for Google Regarding Chrome’s Dropping of H.264
Bravo to Google for thinking a few steps ahead.

> In addition to supporting H.264, Chrome currently bundles an embedded version of Adobe’s closed source and proprietary Flash Player plugin.

For one, I am a little tired of the hyperbole surrounding Flash. Yes, it isn't quiet open source, but it's not quiet "closed source", either. Since I can download an open source Flex SDK and compile without the need of any Adobe tools. I can't fork the player API, but this rant seems like sensationalism. Secondly, Flash player handles much more than just video. I'm not saying it is used in the best way, but it definitely caters beyond video render. Removing H.264 doesn't have the same impact as removing an embedded Flash player.

synxer··on Apple Doesn’t Want Coders Messing With iPhone Buttons — Sometimes
While true, there is a much bigger point here that you're missing. What is the point of the App Store approval process if it's not inherently reliable to the developer who has spent countless hours bringing him/herself up to speed on the guidelines of the store?

And this isn't really a secret Easter egg, either. The supposed rigorous approval process should catch something this obvious, I would hope.