HN user
I think it's because IE6 is the default browser for Windows XP Installs. I think even with the later Windows XP Service Packs, they still baselined to IE6.
That and there was a big gap in time between IE6 and IE7. Didn't Microsoft once announce that IE6 would be their last browser, as that's all the world needs?
It's worth noting Scott McCloud also did the Google Chrome comic - http://www.google.com/googlebooks/chrome/
I think this comic sums it up nicely -
http://www.ethannonsequitur.com/facebook-you-customer-produc...
I agree with this. At first glance the problems he presents are simple, then you realise all the design decisions they've made and the pros and cons of each approach they were aware of when writing C#.
On a footnote I also recommend Jon Skeet: Coding Blog - http://msmvps.com/blogs/jon_skeet/ He's known in the .Net community. He's the guy behind Tony the Pony. He's a Google staffer who has written some C# books. He goes into great depth about C# stuff.
This has happened to British Agents before in WWII. I remember seeing a documentary about training British agents to infiltrate France. While in France one agent got caught out by asking for a black coffee. This was the default coffee at the time in France, people would just ask for a coffee and expect a black coffee. This made him stand out.
There are similar stories like this in movies, such as the Great Escape, when one of the escaping prisoners is dressed as a civilian and is boarding a bus in town. A German Officer says in English "Good luck", the prisoner replies in English "thank you" and is caught.
Newspapers and the press in general normally have an obituary team who write and update obituaries for noteworthy people who are still alive. That way if anything happens, they can be quick off the mark and publish a well researched article about the person. Occasionally these are published in error when the person in question is still alive.
Well, when working on a code base, the first thing I think is who wrote this and when. When they wrote this how experienced was the developer? What's there coding style or was it written after coding standards were introduced? I've had this misfortune of inheriting a lot of bad legacy code in the past and when you see a chunk of bad code, you can either spend a good chunk of time figuring what it's really doing or less time figuring out the intent. Depending on who wrote the code, what it does, and various other factors you can decide which path to take.
With this code snippet it's obvious that the intent is to remove all the elements. So it can be fixed with a .Clear();
From a higher level, you can see that the snippet smells bad, and will need some attention.
I didn't say I'm smarter than all the developers I encounter. I've just encountered a lot of bad developers in my time.
Or Even this.MyControl.TabPages.Clear();
Sorry, I should have been clearer. I was getting flashbacks to when I saw a similar problem (except in a for each loop), that's what set the alarm bells ringing in my head.
When I see nasty code like that, I tend to stop parsing it fully and sniff out the intent. I think it's a form of bad code blindness (like banner ad blindness) my brain is protecting me from all the bad code I've seen. If I fully parsed all the really bad code properly I’d become a dribbling wreck. :) So I tend to look at it at a higher level instead to stay sane.
As soon as I saw that snippet I could see what's wrong.
In C# / .Net you can't remove an element from an enumerator while you're enumerating through it. You can remove the last element however, as it's the final loop the enumerator isn't used again so it won't throw an error. The original developer probably tried to remove it forward only first, encountered an error and wrote the code to loop through it backwards, using the random tweaking technique.
What's rather depressing is that a lot of developers I've encountered use the random tweaking methodology, instead of figuring out what's really happening.
Google did this when they first launched Chrome too - http://www.google.com/googlebooks/chrome/index.html
Most of the talk of Google buying Motorola Mobile has been about the patents and more control over the hardware. I think it's also important to consider the tax breaks Google could be aiming for -
http://www.theregister.co.uk/2011/09/01/google_buys_tax_brea...
You could always check this incident map of the areas and visit the high street shops -
http://www.guardian.co.uk/news/datablog/interactive/2011/aug...
Something like an automated resume / CV generator would be a great feature for a site like Linked In, or perhaps Monster.com.
They exist outside of the Japan too. It's called Lolita Fashion - http://en.wikipedia.org/wiki/Lolita_fashion They have lots of different sub styles - Gothic Lolitas, Sweet Lolitas. Generally from what I understand they're their own sub culture outside of Japan, but they're not uncommon at anime / manga events. The retailers at these events already sell Japanese sweets, even the seasonal and limited edition ones. In the US JBox.com – and their NSFW parent company JList.com are probably the biggest retailer of such candies in anime / manga fandom.
JList buy candy in bulk from wholesalers and advertise heavily to anime and manga fans. They have a generous affiliate banner ad scheme too, which means lots of sites link to them. As Candy Japan expands I imagine JList would be a primary competitor for selling Japanese Candy. They already have the market share and infrastructure in place, with offices in Japan and the US. I'm sure there is plenty of room for competition, but I'd be aware of them as a business rival in this market.
The parent article is doing it's round on the internet at the moment. It's linkbait.
Scott Hanselman has a better rational breakdown of the article - http://www.hanselman.com/blog/HackersCanKillDiabeticsWithIns...