Skip to main content

The iPhone May Save Korea (from Internet Explorer)

Korea's technology infrastructure far outshines the US, but one area where Korea is stuck in a tech quagmire is browser support. The whole freaking country is stuck on IE, many on IE6. It's not that people love Microsoft. The problem (I think) is that many Korean sites require "Real Name Verification", and back in the day, Microsoft made an ActiveX control that took care of it. As a result, every new website used that control, and all web development centered on IE.

Nowadays, many, many sites only work on IE, which is incredibly annoying. Case in point - I got my internet hooked up a few days ago, and they needed IE in order to set up my ISP username/password. They assured me that once it's set up, I'll be able to use it in any browser, but I'm not holding my breath (thank god for my virtual machine).

But all hope is not lost. Despite its numerous flaws, especially the fact that it doesn't work as a phone, the iPhone is slowly helping to change the landscape of browser compatibility in Korea. Like the rest of the world, Koreans find the iPhone sexy. This is starting to bleed over into laptops, too. I see a lot of MacBooks in coffee shops nowadays, compared to approximately zero when I first visited Korea three years ago. Big websites are starting to take notice, and developing sites that actually work on more than one browser. Sexy iPhone --> Increase in Cross-Browser Compatible Websites. There's something you won't ever see in an Apple ad.

So I guess here's where I should say thanks, Steve. Your brilliant marketing of the iPhone is helping to cut the ball and chain of IE6 from Korea. God knows it's long overdue.

Comments

Popular posts from this blog

Why Korean Is Hard For Native English Speakers

A couple of days ago, as an experiment, I wrote my first blog post ever in a non-English language . It was an attempt to explain some of the reasons that Korean is hard to learn for native English speakers, so I figured I might as well try to write it in Korean. Those of you who actually read Korean can see how awkward the attempt was =). In any case, the post came from an email conversation I had with The Korean from  Ask a Korean , a fantastically well-written blog about all things Korea from the perspective of a Korean who moved to the United States during high school. Since I tend to geek out on language things, I figured I might as well post part of that conversation. An edited version follows. --------- Out of the languages that I've attempted to learn so far, Korean has been the hardest. I've done a lot of meta thinking about learning Korean, and I think there are a number of reasons it's difficult for non-Koreans (and especially Westerners) to learn: 1) Obvi...

10 other things South Korea does better than anywhere else

Recently this article about 10 things that South Korea does better than anywhere else  has been making the rounds on social media, but when I first read it, I couldn't tell if it was sincere or satire. A few of the items on the list are not very positive, such as "overworking" and "using credit cards". So, I thought I would try to put together a better list. Here are 10 other things South Korea does better than anywhere else: 1) Small side dishes, a.k.a. " banchan " (반찬) Banchan are by far my favorite aspect of Korean cuisine. Rather than the "appetizer and main dish" approach of the West, a Korean meal is essentially built around small dishes. Even a 5,000 won (about $5 USD) meal at a mall food court will come with two to four banchan in addition to the "main", and often people will actually choose restaurants based  on the banchan (e.g., seolleongtang , or beef bone broth soup, places tend to have the tastiest kimchi). Ther...

Pushing Python Performance With Parallelization

TL;DR: For certain types of programs, you can take advantage of idiosyncrasies in the Python interpreter and the host operating system to create real shared memory between processes and get some pretty good parallelization. Premature optimization is the root of all evil. As a developer, you've probably heard this before, and what it means basically is that you shouldn't waste time optimizing code unless it's already doing what you want it to do. We also live in an era of seemingly unlimited resources with AWS/Google Compute, and often the easiest way to get higher throughput in your programs or service is just to pay for more instances. But sometimes it's fun to see what sort of performance we can get on a simple laptop (and save some cash at the same time). So anyway ... I've been working on this thing, and it took too damn long to run, and I needed to run it lots and lots of times ... so, it was time to optimize. Basic optimization has two main steps: 1) P...