63 karma · joined March 9, 2011
This seems like a succinct summary for the paper. Or at least, it's the part that stuck out to me.
"I no longer have to sit at my desk pretending to complete tasks, as the only person I am cheating is myself."
Snippet from the Wikipedia article:
"On 20 January 2009, the protests intensified into riots. Between 1,000 and 2,000 people clashed with riot police, who used pepper spray and batons, around the building of the parliament (Althing), with at least 20 people being arrested and 20 more needing medical attention for exposure to pepper spray.[3][11] Demonstrators banged pots and honked horns to disrupt the year's first meeting of Prime Minister Geir Haarde and the Althing. Some broke windows of the parliament house, threw skyr and snowballs at the building, and threw smoke bombs into its backyard.[2][3][12] The use of pots and pans saw the local press refer to the event as the 'Kitchenware Revolution'.[13]"
[2] ^ a b Gunnarsson, Valur (21 January 2009). "Icelandic lawmakers return to work amid protests". Associated Press. Archived from the original on 31 January 2009. Retrieved 22 January 2009.
[3] ^ a b c "Iceland protesters demand government step down". Reuters. 20 January 2009. Archived from the original on 3 February 2009. Retrieved 22 January 2009.
[12] ^ "Icelanders held over angry demo". BBC. 21 January 2009. Archived from the original on 24 January 2009. Retrieved 22 January 2009
[13] ^ Ian Parker, Letter from Reykjavík, "Lost," The New Yorker, 9 March 2009, p. 39.
I understand where you're coming from though. I just think that you need to know a lot of context about the developer in question before you dismiss him/her over their tool choices. You need to know why they used those tools and how well they learned them.
But what it really comes down to is how fast the developer can learn something new. I'm fairly confident that I understand enough about programming language concepts to be up and running with a new language in a few days. I might not know the API (if one is provided) but I will probably be able to contribute to the team pretty quickly.
Personally, I dislike the language wars. I think that a good developer should be able to write good software with the tools available. Arguing the opposite always smacked of the "silver bullet" to me.
I only half agree that this is a limitation. I use as little component scanning as possible. I think it's better to scan for the configuration classes (hopefully there aren't many) and explicitly define the rest. I like this for two reasons, first for speed and second because everything is defined in a fairly central place. I can't tell you how many times I've been surprised by annotation based configuration.
Personally I like Spring's Java Configuration over Guice's. It's more flexible for my needs. Although I suppose that an argument could be made that that's the problem: configuration over convention.
I'm glad you mentioned the Guice style @inject is available with Spring now. I wasn't aware of that.
Both are valid points. Why are you arguing? The points don't seem mutually exclusive to me. Tesla has a lot going for it. They make innovative cars, and I would love to own one. That doesn't make the company's PR responses any less defensive and cagey. The response for this particular issue is a big turn off for me. I would definitely prefer that they didn't contradict themselves within the first three paragraphs.
I get it. Owners of Tesla cars need to charge their cars or they will be out $40,000. That makes sense to me. Batteries don't last forever. My Mother however doesn't care how the car works. She just wants it to work. She'll do the maintenance that you ask her to do, but she's not going to know why. So, she won't know why she can't leave the car at the airport for a month.
That's why it's important for Tesla to say, "yes this is an important issue that is part of maintaining your car." Not, "A single blogger is spreading a rumor about electric vehicles becoming inoperable." If my Mother read that last sentence, she might say to herself, "oh, I guess that blogger was just lying," and move on without reading the whole article, now assuming that it's not possible to "brick" her car.
I also lay some blame at Michael Degusta's feet. I don't think that it was appropriate for him to title his article "'It’s A Brick' – Tesla Motors’ Devastating Design Problem." I don't see this as a design problem. It works. The potential for bricking your car is just something you'll have to watch out for, just like not changing your oil is something you need to watch out for.
I think that Tesla was just reacting against the accusation that they had a design flaw. As long as they make sure that all of their customers know of the issue, it's not a design flaw. At that point it's maintenance. That's where I think that Tesla failed today. They skimped on their responsibility of informing the customer of important facts, so that they could come out smelling like roses.
P.S. Incidentally, if I were to take a trip to my mountain home in Italy for half a year, roughly how much would I expect to pay in electricity to keep my Tesla vehicle charged? Does it draw a constant amount of power for the entire time that I'm away?
Also, what does Android being open source have anything to do with his argument? He sneers at Android calling itself open. Why? Sure, Google made a bad decision by supporting Verizon's take on Net Neutrality, but how does that make their source code less open for modification? It may mean that we can't treat carriers as dumb data pipes, but that fact makes Android less open?
What does your project do? I might be interested. What I'm really looking for, is an easy way to give a small group of people (like people who respond in a hacker news comment) a full version of my app for evaluation purposes.
On a somewhat unrelated note, are there any usability aids for smartphone users out there? Something like the Voiceover application mentioned in the article?
Edit: I'm mostly curious about Android phones.
In my humble opinion, the area where Google TV really kills is in media aggregation. I can enter a few search terms, and suddenly video, audio, and who knows what else is available on my big screen TV. Is it on Netflix? Is it on Youtube? Is it on Amazon? It doesn't matter. I just search in one place and press play. Ultimately, this list will include Hulu, ABC, NBC, Comedy Central, Fox, et al. We will have to wait for the content providers to decide that advertising to web viewers is just as worthwhile as advertising to cable viewers.
Imagine a TV experience where everything is video on demand from thousands of sources, but searchable from one place. You won't even need a cable subscription.
Does anyone know what version of Chrome is on Fishtank?