deadcyclo
I'm interested in the impact on users when one changes things several times quickly like this. Anybody here that has knowledge/experience that would like to say a few words about it. Personally I always am annoyed by change, more so when things seem to change "all the time". Anybody have some actual statistics on how people reacted to this type of design changes?
But running around telling people their argument is invalid because it is X, simply makes one look like an ass.
AFAIK Apple doesn't restrict you from bundling files in your application. That simply wouldn't make any sense.
The point here is that he is talking about an application consisting of a single runnable binary of size X with tons of bundled .sty-files that brings the whole application up to 4GB.
Previously, this would not be allowed, since .sty-files are interpreted (which in turn would make it impossible to implement LaTeX on the iPhone), but that really wasn't the point here. The point is simply that this wouldn't be a single 4GB executable, but a an executable of perhaps 100MB bundled with a whole bunch of .sty (and other) files to a total size of 4 GB.
Edit: Fixed typos. Sorry. HN doesn't work very well on my phone.
Suddenly, out of the blue, he claims that this will create an arms race to produce disruptive location based services. A claim, that on it's own, simply doesn't make sense. Further he claims that the downside is location based ads, as if this is some kind of new concept.
None of the "conclusions" in this article seem to make any sense.
Personally I'm not a huge fan of RMS. I agree with a lot of what he says, but at the same time I cannot agree with the way he presents it. There are two reasons why I am a member of The Linux Foundation, and not the FSF, and their names are Richard Stallman and Matt Lee. Though I feel very strong about the motives and ideology of FSF, I simply cannot condone their way of presenting them. I personally feel that RMS does as least as much to harm their goal as to aid it, and I find ML to be horribly hypocritical. No matter how much a disagree with how their do tings, I would never disrespect them as human being. But sometimes it feels like I'm alone in the world. Everybody else either adores them, or tries their darndest to disrespect them.
This is in no way unique to HN. I see it everywhere. Even in the media (here in Norway). Last time RMS talked here, all of the important IT-related media where represented. (And I noticed immediately that they were more concerned with their beers than actually listening). The articles the day after were horrible. RMS had talked about some really far out there, fairly absurd stuff, and some really smart, realistic stuff. Every single media gave their best effort to make RMS look like a loon. _None_ of the smart, realistic stuff was mentioned, even with a single word, anywhere. An they had twisted the far out stuff, to look even worse. One of them seemed even to either not have listened to a word, or was simply making stuff up. RMS said at least 6 times specifically: "I'm not talking about Micropayments, I'm talking about making pay what you like/can easier", "Don't confuse this with micropayments", etc. Yet this journalist managed to write a half an article about all of the stuff RMS had "said" about micropayments.
Last time I went to one of his lectures he clearly stated that you should do you best to avoid using proprietary software _for your own good_, while he said that creators of proprietary software were evil.
I have a hard time seeing this as hypocritical, unless he actually goes on record stating that «you should not own a mobile phone, and you should never ask to borrow a mobile phone when needed».
The only way a could consider this hypocritical is if he asked to borrow a phone from somebody who at all times turned their phone of, and only briefly turned it on to make calls. But I'm rather sure that if he asked to borrow a phone from somebody, and their reply was, "sorry, I would rather not turn it on because I don't want to be tracked", he would respect that.
In other words. Who ever arranged this graduation obviously did a horrible job, and is the person you should blame.
- Scan the QR code to receive a rebate coupon for the product advertised - Scan the QR code to receive a two for one deal on tickets for what ever event advertised - Places like 7-eleven offering you a free soda with your hot dog if you scan the QR code on the poster in the window before entering - Scan the QR code for an exclusive trailer for the movie advertised - An ice cream company introduced a new ice cream and you could scan the QR code on the advertisement to get a free ice cream - Adverisements for universities where scanning the QR code would let you order their information brochures sent home to you - Scan the QR code to be informed when the advertised service is available in your location
And several other uses I can't remember at the moment.
My point is that it is, like the author of the article indicates, quite possible to make great use of QR codes in advertisements.
Many of the mentioned campaigns I also know worked great. For example during the free ice cream campaign, the local 7-eleven was filled with teenagers with smartphones getting their free ice cream every time I went there.
I've also noticed that most of the campaigns that succeed don't "just slap a QR code in their", they give you information about it: "Scan the QR code to get a free ice cream using your cell phone. If you have an iPhone go to xxx to get a scanner, if you have an Android xxx, if you have a Nokia xxx" or similar solutions. It's kind of a chicken and egg problem. Nobody will use QR codes if they don't know what they are, or how they work. And nobody will known what they are and how they work, unless somebody tells them.
Now, if he really was talking about google reader being retired, and not just the API, that would mean that he in no way, shape or form could have read the blog post he himself initially posted a link to.
My best guess is that it simply is a poor choice of words, and that he figured since he was posting on the webpage of the API, he simply skipped the word API.
It's posted in "Friends of the Unofficial Google Reader API"
and he says: "I realize that we're using an unofficial API, so we have no right to complain about any changes to it (instead we should be thankful to have been able to use it for so long). But at the same time, the Reader team is well aware that developers such as myself are using their API in our software, and some of us rely on this software to generate an income."
That sort of seems like modifying FOSS and not bothering to contribute back your modifications to the original product because "from experience most FOSS projects don't bother about my code". (And yes, many FOSS licenses require you to provide your code if you distribute. They don't, however, actually compel you to actually submit it to the original project.)
In my eyes, it's about common courtesy: If you sign up for testing a product, you report your findings. That said, I'm not saying you have to, I'm just saying that by providing your feedback, specially when they actively are seeking it, you might help create a better product.
Much much worse, however, are all of the people/companies that include multipart/alternative sections, but do it completely wrong: "This is an HTML-email. Your client lacks HTML support. Please visit [url here] to view this email" or even worse "This is an HTML-email. Your client lacks HTML support. Please upgrade your software".
I come across these almost daily, and it bugs the hell out of me. Unless it is something very important (bill, sign-up email, etc.) I simply ignore these emails, and they never get read. (Yes, it really is out of spite. I'll ignore them when reading email in a web client or on my phone later. They simply lost their chance)
I don't really like HTML mail, but I can live with it. I see the reason why it exists (great for advertisement). However, if you use HTML email, do include multipart/alternative section for non-HTML clients, and include the same information there, non of this "your client can't handle HTML, you loose crap".