1,252 karma · joined October 29, 2008
rgd@hey.com
So, I downloaded it. And I got caught (via a warning letter from our ISP). Shortly thereafter we canceled our cable subscription.
I cannot fathom why, as a company, you would make it so hard for someone who is willing to pay you for content to get it. I wouldn't have been happy about having to buy it on DVD since I already have a subscription to HBO (and in my humble opinion, their previous original content should be available via on-demand all the time, although I realize that's a pipe dream), but I would have. Instead, they alienated a customer and lost all my money. That was around two years ago, so at $15/mo. (not sure how much of that goes directly to HBO) $360 has now been lost by them/my cable company for that part of my subscription alone.
If they ever allow you to buy into HBO Go (or whatever their online streaming option is called) by itself without a cable subscription I would consider it, but as long as they are stuck in their old-school ways they can forget having me (or most of my friends) as customers.
I know this article isn't about HBO, but I just thought I would point out another example of the way that content producers continue to alienate the people who should matter most: the consumer.
It’s worth noting that Metro is more than just a new look, and more than just putting touch first. Metro apps have similar restrictions to iOS apps. According to Jensen Harris, for example, Metro apps will get “about five seconds” after they’re no longer on-screen before the system puts them into a suspended state. There’s no file manager. Users no longer quit (or, in Windows parlance, exit) apps explicitly. These tradeoffs sound familiar?
...Did you (and the parent poster) simply read the Gruber article until you could find something to nitpick, then go with it?
The sense of entitlement when it comes to something created and used freely, solely for the purpose of making the world better, sometimes simply astounds me.
At the end of the day, it doesn't really matter who caused what to happen to this woman, does it? AirBnB have obviously given credence to the basic tenants of her story (she is a person, she used AirBnB, she was ransacked), that is enough. The only thing that matters after that is the way they handled the situation.
So I guess it's more of a technical/sign-in limitation than a licensing limitation.
Customers are not stupid. They see right through PR speak, and you can clearly see that in the comments.
"They could also use this information to see whether I’m using Google Video Chat. Whether this is the purpose or not I don’t know. Regardless, they’re collecting this information from millions of unknowing users. Bad form Facebook. Bad form."
I don't think that's making big assumptions. That's just stating a fact: you don't do something invasive when it's not required or expected by the people trusting you to run software on their computer. End of story.
With as much privacy flak as Facebook constantly takes, you'd think at least one person in the company would be trying to make sure stuff like this doesn't happen.
If I really want to not deal with the headaches of managing an infrastructure, I'd really prefer to go with a provider who picks a language and becomes a major player in that field (e.g. EngineYard, Heroku); companies that really push the envelope and give back and are a _part_ of the community. It just feels like you're going to be decent at a lot of stacks, and master of none.
If on the other hand I really have a need for 30 different types of services, and I don't want to work with 30 different service providers (Heroku + RedisToGo + etc.), I would probably be a big enough company/app to be comfortable just running things myself on AWS.
About the only way I think you could compete in this space (at least from my personal prospective) is to be cheaper than Heroku, EngineYard, RedisToGo, etc. for those particular stacks -- the idea being that you're not going to get the "major player" in Ruby to host your site, but you're not quite just using bare-metal AWS, either.
I really don't know why I'd pay the same or more than specialized service providers for a "jack of all trades".
EDIT: That being said, I do notice that you have stacks available for PHP, Perl, and other languages/tools that maybe don't have such an established PaaS provider as the Ruby ecosystem does. So maybe it's not too later to capture that market. I just don't see myself jumping on board the generic PaaS train for solutions where there are great, established providers out there (Ruby, Redis, CloudDB, others).
I agree that when creating an open source solution, you should name it something work-appropriate. On the other hand, picking a name that's unique tends to get it to stick in developer's minds (who read about lots of open source solutions on a daily basis).
I guess I'm just saying: it sounds like you spent a lot of work on a "mammoth" task that could have easily been handled a different way.