864 karma · joined February 6, 2009
Back to your original point though, I would suggest trying it out for a week or so. I was hesitant as well, but so far it seems very natural and fluid to me. Even scrolling sideways to see more tiles just feels very natural.
If a politician changes his view and publicly states that he held a very different view before but he was swayed by x, y, and z then I think nobody would accuse them of flip-flopping.
What I'm thinking is a service that uses Glacier to store my photo library and some type of front end service (like dropbox) that keeps a low res version of that photo along with some meta data about it.
My reasoning for this is that we all build up pretty significant photo libraries (mines already over 60GB) and I'm always trying to make sure I have them backed up. I currently use a paid plan at Dropbox so I can put them all up there but it's kind of a waste since I hardly ever pull many of them down again. Every once in awhile I browse through them looking for certain pictures that I might need to get a copy of (which is why I'd need the low res copies easy to access/browse) and then be able to choose which ones to pull down from glacier. The other good thing about a service like that is the need is not typically immediate.
Maybe I'll look into building this since it's something I'd love to have for myself!
http://bits.blogs.nytimes.com/2012/08/29/samsung-windows-pho...
I don't think the lack of the feature is the main complaint in the article it's that her data seemed to be suddenly gone (I know she eventually found it but it took a third part tool to try to export the proprietary format into something usable).
That's the thing I can't get past with most of your arguments on here. If an algorithm is truly unique and worth the patent then in reality it shouldn't need the patent at all.
I also don't understand the "I invented an extremely complicated algorithm for solving X" mentality. We all stand on the shoulders of those who came before us in solving more and more complicated problems. Without the software, algorithms, and general knowledge of computing that have been made available to us we'd not be able to take that and build ever more complicated systems on top of that.
I'm one of those people as I have several devices (kindles and tablets) so I prefer paying for one data plan on my phone and tethering vs. individual data plans for each.
It seems like Microsofts end game is that you will have one device and the interface for interacting with that device will depend on where you are. If docked at home with external monitor, keyboard, and mouse you get more of the desktop feel. Unplug the device and take it with you and you have more of the touch based interface.
Most people who buy tablets are likely to have a smartphone so it would seem more appropriate to have tethering and use that one connection for multiple devices.
I realize that's a personal choice, but I currently own an iPad 2, Kindle Fire, 2 Kindle Touches, and I just bought the Nexus 7. I'd rather pay for one connection and tether all those devices to that connection than each one have their own.
You can never forgive them for making the absolute best browser on the market at the time it was released? Don't blame Microsoft because there are people out there are still trying to use IE6 today.
Therefore, it stands to reason that any decision made, whether for or against Google, could effect future decisions for companies involved in similar suits.
I think, in this particular instance, a decision against Google could have set a terrible precedent.
What is wrong with writing your core application logic physically removed from any of these frameworks. Why do people insist on fitting their application into the Rails framework or any other web framework.
Write your core application code in Ruby (or your language of choice), package it in another gem, use tools and patterns we've had all along to plug that code into a dependency for persistence (if needed)...communicate with it through a standard API that you define for your delivery mechanism (i.e. Rails).
I just don't get this idea of trying to contain my application code within the confines of a specific framework.
It's still pretty good thanks to the work the Xamarin guys have done.
We have a large .NET code based developed on Windows for Windows and out of curiosity once we tried to compile under Mono. We were expecting hundreds of issues and we ended up with only a few errors and if I'm not mistaken I believe it had to do with some of the file based handling code we had. Granted we never fixed those and attempted to run it, but I think they've done some amazing work.
Even now, one of the only ways (maybe the only?) to build a re-usable library for iOS, Android, and Windows Phone 7 is to build .Net library that compiles under Mono.
We are a global business and China's most popular browser (at least with users hitting our site) seems to be Maxthon which is based on the Trident rendering engine (which of course is what IE uses). This makes it nearly impossible for us to ever consider cutting off IE support unless we wanted to neglect one of our largest growing user-bases in the world.
Make sure you seriously consider which parts of the world your app could potentially be used in and do the research to find out what browsers they use in that area.
What I find lacking, coming from the Apple world, is the severe lack of accessories for my phone. Finding even a simple dock or a decent case is a pain.
We must remember that they are all kids just trying to find their way. Some kids find their way by trying their best to fit in while others might be like the kid in this story.
You can build this kid up while not tearing the others down. Even the kids who are popular and mean, like the girl he mentions in the story, may at an older age find some of the things they did in school reprehensible. Lets not condemn them while they are still young and immature.