While listening to Wil Wheaton’s podcast a few months ago, he played an interview he did with Felicia Day, creator, writer, and star of The Guild, a web comedy series (a TV show but only available on the web). I had never heard of The Guild, but Wil did a number of guest appearances on it and kept talking about how great it was, so I thought I’d give it a try. The Guild is undoubtedly one of the funniest shows I’ve ever seen, on or off TV. The writing is brilliant, the characters are hilarious, and there are even shocking plot twists and cliffhanger moments that make you look forward to Tuesdays. Each episode is only 6-8 minutes long, and a new episode is released every Tuesday. A “season” lasts for about 12 weeks and season four just finished last week. I started watching The Guild when I was off work, so I managed to catch up with all of seasons 1 through 3 in a couple of days, and during season 4 I tried to watch it every Tuesday night.
The Guild is about a group of six people who play some kind of online game, similar to World of Warcraft (which I’ve never played). Note that you don’t need to know anything about gaming (I don’t) to enjoy the show. The game has taken over their lives and they even use each other’s game character names when talking in real life. In fact, of the six of them, I only know the real name of one of them – Clara, because her character name is also Clara. Oh wait, Bladezz’s name is Simon but even his sister calls him Bladezz. The other characters (except Tink, I believe) have had their real names mentioned, but only a couple of times. The main six characters are part of a guild known as The Knights of Good, meaning that they play together as a group and fight against other guilds. The guild members are:
- Codex is the main character, played by Felicia Day. She’s a single woman who’s very insecure and always concerned with what the other guild members think of her.
- Zaboo is a young man of Indian descent who is good with computers but has no social skills whatsoever. (When he moves in with Vork, Vork tells him, “Men only shower together when there’s more than one shower.”) He lived with his very controlling mother until season 3 when he moved in with Vork.
- Vork is a 40-something balding guy who is extremely cheap and follows rules to the letter. He’s the leader of the guild.
- Tinkerballa (known as Tink) is a bit of a mystery. I believe she’s a med or pre-med student, though her personal life is pretty much off-limits to the other guild members. I don’t think they even know her real name. Tink is beautiful and not only is she well aware of this, she uses it to her advantage whenever possible.
- Clara is a stay-at-home mother of three (or two, depending on the season – one seems to have vanished) very young children, who she routinely ignores while playing the game. Her husband, George aka Mr. Wiggly (named after…. um, never mind) once joined the guild temporarily but was completely inept at the game.
- Bladezz is a high school student who works at a local burger joint, “Cheesybeards”. Bladezz is always making off-colour sexual comments and was described in a recent episode as “skeevey”. Good word.
The Axis of Anarchy is another guild that the Knights of Good are constantly battling with. Their leader is Fawkes, who has a strange love/hate relationship with Codex. Fawkes always has this little “I’m smarter than you but I suppose I can bring myself down to your level” smirk on his face when he’s talking to someone. Fawkes is played by Wil Wheaton, who does a great job of playing an evil yet oddly charming douchebag.
When I first started watching it, I assumed that it was done as a web series because it wasn’t good enough to be picked up by one of the big networks. Because you know, the sitcoms that are shown on the big networks are all really good. cough $#*! My Dad Says cough But it looks as “professional” as any network sitcom, the actors are all really good, and as I said before it’s very funny. If it were a network show, they’d have to expand it to 22 minutes per episode, and tripling the length of each episode would likely water it down too much. Having a “live studio audience” watching the taping of each episode would not make the show any better, and God help Felicia Day if she were to add a laugh-track.
Being an internet-based show aimed at geeks, it is a little surprising that the website for The Guild is so confusing. If I were to design it, I’d have a page for each season and links to each episode in that season all in one place, so it’s easy to find episodes. There is a blog that has a page for each episode, but that bumps you off to Bing where the episodes are hosted. Once you’re there it’s not easy to find other episodes – the “related videos” on the right seems to be a random assortment of episodes from all the seasons. One page I went to (season 4 episode 10) had a link to season 4 episode 5 instead so I had to start poking around until I found the right episode. From the time I started looking to the time I was actually watching the right episode was at least five minutes – should be a matter of seconds.
But being an internet-based show aimed at geeks, it is not particularly surprising that there is a fan podcast for The Guild. It’s called Knights of the Guild and features a guy named Kenny who is a member of the crew, though he hasn’t mentioned (in the few podcasts I’ve listened to) exactly what he does. After every episode, he does a “companioncast” during which he interviews many cast and crew members and talks about that episode. This is recorded right after the episode was filmed, which is months before it actually airs. Most of these interviews are pretty interesting, though some are kind of Chris Farley-esque. “Remember when happened? That was soooooo funny” isn’t much of an interview question. It does seem a little weird to have a 90+ minute podcast about a 7-minute episode, but whatever, it’s fun.
I suppose The Guild is not for everybody, but I think a lot of internet geeks like myself (I have a blog, I use twitter, and I use terms like “epic FAIL”) would love it. As I said, you don’t need to be a gamer (or even a geek) to like the show, but if you’re a gamer or a geek, give it a try at watchtheguild.com.
If you are an American citizen, you should be very frightened at the direction your government is heading. Last week’s Security Now podcast talked about two different but related issues regarding privacy and censorship of the internet. Both issues involved the US government attempting to legislate away some problem that they don’t know how else to solve, and in both cases the legislation will accomplish precisely nothing.
The first is COICA, the “Combating Online Infringements and Counterfeits Act”. The idea of this bill is to allow the government to force the delisting of particular web address from DNS servers around the country, so if you tried to go to http://www.copyrightinfringer.com, the browser would fail to look up the IP address for that name, so you wouldn’t be able to get there. There is no due process here – the US Attorney General could order a web address added to the blacklist (which all ISPs would be required by law to respect) even without any kind of trial. This is obviously at the
request demand of the RIAA and MPAA to catch people pirating music and movies, but the bill is worded vaguely enough that the AG can take down any site he wants. As the EFF puts it, “had this law been passed five or ten years ago, YouTube may not exist today”. The idea that the US government is considering censoring which web sites its citizens can visit is more than a little scary. There are millions of Americans who are thankful that they don’t live in China because the internet is so heavily censored there, and now their own government is considering the same thing. The really dumb thing about this legislation is that it’s going to make it slightly more difficult to get to web sites on the blacklist, but not impossible. You can still use the IP address directly to get there, and all the legislation does is make the translation from name to IP address unavailable from US ISPs. I guarantee you that within hours of this bill being passed, there will be people outside the US creating open DNS servers and web sites listing the IP addresses of blacklisted web sites. There will be Firefox plugins that automatically check one of these other servers and retrieve the IP addresses that way. There already exist legal means to take down web sites that contain illegally copyrighted data. So what will this law accomplish?
The second one is even more frightening. The FBI wants the government to legislate that all cryptographic systems have back doors that the FBI can use to decrypt anything. Law enforcement agencies have been complaining for years that they can’t do the internet equivalent of wiretapping because the encryption that is used is unbreakable. And they’re right: the encryption in use nowadays is unbreakable, despite what you might see on TV. If something is properly encrypted using a modern encryption algorithm, the only way to decrypt it is to correctly guess the key that was used to encrypt it. This is called the “brute force” method, but because keys can be any characters and any length, the number of possible keys they have to check is essentially infinite. And the only way to know if your decryption attempt has worked is to look at the resulting data and see if you recognize it as something useful. Encrypted data just looks like random noise, and it’s not even possible to detect that it’s encrypted. If you were to encrypt a file twice, even brute force becomes impossible. Even if the bad guys guess the correct key the first time, they wouldn’t know that they got it right because the decrypted result looks like more noise. So when they say “unbreakable”, they mean it – without the key, the data is simply inaccessible. By anyone. Ever.
I understand that this ties their hands, but I’m afraid it’s too late to complain about that. This legislation is doomed to failure because strong encryption routines are already out there. Does the FBI honestly think that terrorists will continue to use Skype if they know the US government can listen in on any conversation (which they currently cannot do)? No, they’ll just write their own version of Skype using the existing unbreakable algorithms. Or they’ll send email and attach encrypted files. The terrorists are not going to stop using unbreakable encryption just because the government tells them to stop.
Not to mention the obvious – if all encryption has a back door that the FBI can use to break it, how long until the bad guys figure out how?
In my job at Sybase, I am responsible for the encryption aspects of the SQL Anywhere client and server. If this legislation goes through, we will have to:
- immediately stop sales of our existing products in the US
- remove the existing encryption algorithms from our products for sale in the US (we’d likely keep the existing stuff for sales outside the US)
- obtain a specification of the new encryption algorithms that the US government will allow us to use
- implement them, test our product with them
- implement some kind of tool that will allow our customers to decrypt data that was encrypted with the old algorithm and re-encrypt it with the new one
- ship the new software and politely ask our customers to stop using the software they already have and install the new stuff
This is a significant amount of work that we’ll have to do in order to comply with this law, and thousands of other software and hardware companies will be similarly affected. Some, like Skype, will likely need to redesign their entire product. The only impact will be that people that were already law-abiding will know that the FBI can get into their data if they want to. If there are any terrorists or criminals using encryption software, they just won’t bother upgrading so they’ll know that the FBI cannot see their data. And none of the above even addresses the civil liberties issues with the government being able to spy on its any of its citizens’ private data.
Not a single terrorist or criminal is worried about these bills being passed. But American citizens should be.
Star Trek: The Next Generation is one of my all-time favourite TV shows. I watched it religiously when it was on in the late 80’s and early 90’s and I bought each season on DVD as soon as it was released. I also enjoy former TNG cast member Wil Wheaton’s writing, so imagine my excitement when he started writing reviews of TNG episodes a couple of years ago. He wrote an article about every ten years or so – OK, it was more often than that, but that’s how it seemed when you were patiently (or not) waiting for the next one to come out. He posted links to them on his blog, and then gathered them all up, did a few more, and put them in a book called Memories of the Future. There will be at least two volumes; each covering one half of the first season of TNG; only Volume One has been released. I don’t know how much further he’ll go – I asked him on twitter if he was planning on continuing the books or podcasts right up to season 7, but he never responded. Geez, you get 1.6 million followers and suddenly you don’t respond to questions? Bastard. I’d respond to you, @wilw.
Anyway, this book is a must for TNG fans. Wil rips each episode apart, telling you what was good and what was bad, which is fun to read because there were a number of really bad episodes in the first season. There is a lot of humour in the episode recaps and technobabble, and I found the behind-the-scenes memories really interesting.
Wil also gives some insight into the whole TV industry and how it works – like when person X is writes a script for an episode, but then their original script is hacked and changed without their knowledge by someone else who doesn’t get credit. By the end of the process, the writing of this really bad episode is still credited to person X, who really had nothing to do with how bad it is. It seems unfair, but that’s how it works. Wil pulls no punches, naming names on who were the worst writers, directors, and guest actors that he worked with.
Wil is very complimentary to the other cast members of TNG, particularly Patrick Stewart and Brent Spiner, who are indeed excellent actors. One person he’s not very complimentary to, however, is himself. He seems convinced that he was the worst actor on the set, and that a large contributing factor to that is his youth. A number of times he mentions that if he wasn’t such a self-absorbed teenager at the time, he might have done a better job. Of course “self-absorbed teenager” is a redundancy, and Wil himself does acknowledge this at one point, when he tells the story of apologizing to (I think) Patrick Stewart for being the way he was when he was a teenager and not appreciating things as he should have. Stewart tells him that everyone at the time understood that he was a teenager, and that that attitude came with the territory. Of course, some of this self-deprecation could just be modesty – he only makes a point of mentioning when he did a lousy job. Perhaps there were a number of episodes where he thought he did a great job, but he decided to keep the “Wow, my performance was really great in this episode” thoughts to himself.
Wil was also doing weekly podcasts called “Memories of the Futurecast”, where he would read part of his review of one episode a week. In many cases, he’d expand on the stuff in the book, or mention memories that had come up since the book was written or that he didn’t include in the book for whatever reason. Those were pretty cool too – Wil is a good storyteller and is also pretty funny, though I find sometimes that the funny loses steam fairly quickly. In one or two of the podcasts he mimicked a conversation between himself and some pretend person – the first two or three lines were pretty funny, but then he kept going and the next seven or eight lines were just not. More is not always better. It’s kind of like my seven-year-old: “if I say or do something and daddy laughs, then obviously if I do it every ten seconds for the next hour, it remains funny.” Wil doesn’t go that far, but there have been a few times where he starts one of these jokes or “conversations” and after the second or third line I think to myself “OK, that was funny, but stop there. Please just stop there.” and he doesn’t. These long drawn-out jokes don’t appear in the book though, just the podcast.
The one thing I don’t like about the book is the language – there’s a fair bit of cursing and some sexual language and stuff like that. This is true of all of his podcasts actually, he’s quite the little potty mouth. It doesn’t bother me directly – I’m no language prude, and some parts of this book are quite hilarious because of the language. Example: when talking about Q giving them the whole Farpoint thing as a test, Wil explains why this will not be a problem: “in Starfleet, we save the universe and fuck the green alien chick before breakfast. We got this one.” My problem is that my 10- and 7-year-old sons are both TNG fans (ironically, Wesley Crusher is their favourite character along with Data) and I think they would get a big kick out of some of these stories, but it’s just not appropriate for kids that age to read about anyone fucking green alien chicks, or any other colour of alien chick for that matter. Perhaps I can find some stories that the boys would like and read parts to them.
As I said, if you’re a TNG fan, you owe it to yourself to check this book out, or at the very least, find the reviews through his blog. I am anxiously awaiting volume 2 and any subsequent volumes.
Attention Facebook readers: You might want to click the “View Original Post” link at the bottom of this note. Facebook sometimes messes up the formatting. Irony: Writing about Facebook in an article available on Facebook and telling people to go somewhere else to read it.
Gail and I attended a “Facebook 101” seminar at a local school a couple of months ago. A local (Oakville) parent started looking into Facebook privacy, and was appalled at (a) the amount of information available by default to the world, (b) the number of people who don’t know this, and (c) the number of kids joining Facebook and not considering the ramifications of what they post. He started doing this seminar so that parents unfamiliar with Facebook (and even those who are) were informed about the privacy aspects. There were a number of parents there who had older kids than ours, and whose kids were on Facebook. Some of them didn’t really have a good idea what Facebook was or what their kids used it for. After the meeting, I checked on my privacy settings. I was aware of most of the information given in the seminar, and I had already changed my privacy settings, so I didn’t have to make many changes. I then started poking around my friends’ settings and their friends and so on just to see how much information I could glean about these unknown people, to see if what this guy had told us was really true, or if he was more of an alarmist, pointing out the extreme cases. Fairly quickly, I came across a fair amount of information about people I don’t know, the best example of which was the page of my manager’s teenage daughter, who I have never met. Her privacy settings were set wide open. Despite the fact that I was not her friend, I could see who her friends are, pictures of her, where she went to school, and even her her email address, home address, and home and cell phone numbers. I immediately emailed my boss to tell him, and a day or two later her page had been locked down. Even my very limited research told me that this was not an isolated case, and that the guy running the seminar was not an alarmist at all.
- As I said, it’s easier to lock down your personal information – or at least it’s easier to lock down the information that Facebook allows you to lock down. There are now some pieces of information (for example, your networks, sex, what city you live in, and your list of friends) that Facebook now considers public information, which means that you cannot prevent people from seeing that information. It is more than a little disturbing to me that Facebook has decided that they have the right to decide that for you and won’t allow you to change it.
- The old default security settings weren’t bad, for the most part – your friends and people in your network could generally see most of your information. There were some pieces of information that were available to everyone, but not everything was. But the second big change was to the default security settings – the new settings mean that by default, everything is globally visible. If you had modified your security settings before the change those settings were kept, so security-conscious people didn’t notice any difference. But the vast majority of Facebook users had never touched their security settings, and are now sharing all of their information with the world.
- When you install a Facebook application, the application developers get access to all of your information, even if you’ve marked it as private. Even worse, the application developers get access to all of your friends’ information as well. (This has always been true, but you used to be able to turn it off. Now you can’t.) This means that every time you install an application on Facebook, my information (assuming I’m on your friends list) is sent to the developer, and not only do I not have any control over that, I am not even informed of it. The application developers are then free to do whatever they like with the information. Technically they are subject to Facebook’s terms of service, which says that they are not allowed to use the data in any manner inconsistent with the user’s privacy information, but there’s no way for Facebook to police that.
If you don’t like these rules, you can just delete your account, right? Well, sort of, but that still doesn’t solve the problem. First off, Facebook doesn’t give you any easy way to delete your account. There is a way to “deactivate” your account, but there’s no “delete” button there. Apparently if you search hard enough you can find a way to delete it, but does Facebook actually delete your information from their servers, or just make it harder to find? Secondly, even if they do delete it, they still have backups of everything, so the information is all still available to them. Thirdly, (and this isn’t specific to Facebook) if someone on the internet can see your data, then they can save it to their hard disk, and nothing Facebook does can delete that. At the seminar I mentioned, the guy showed pictures that were taken at a frat party back in the 90’s, where two obviously drunk guys were standing at a party next to a stand-up cardboard cut-out of Hilary Clinton, and one of them had his hand on her breast. That guy, years later, became a speechwriter for Barack Obama, and when that photo re-appeared, he got into some serious trouble, jeopardizing not only his job but his entire career. Think about that when you post those pictures from last weekend’s kegger.
I read a comment online somewhere that said something like “Facebook shouldn’t be sharing information about their customers”. Another commenter responded succinctly and summed up everything: “You are not Facebook’s customer. Advertisers are Facebook’s customers. You are the product.” The more public information Facebook has on you, the more they can offer advertisers.
The easiest rule of thumb for internet security is: if you ever put anything on the internet, whether through Facebook, YouTube, a blog, a message board, or even email, whether it’s information, pictures, or videos, whether it’s intended to be publicly visible or not, you must always assume that it will be accessible by everyone – forever. Facebook is proving this – if you post information or pictures on Facebook and expect that only the people you allow to see it will be able to see it, you’re wrong, and it’s not because of some glitch that may or may not come up in the future, and it’s not because someone might squirrel the information away and publish it themselves later. It’s because Facebook is less concerned with your privacy than with how much they can make by selling it.
I read an article recently about a significant virus or some other kind of security problem that people were being warned about. One of the comments on the article said something like “Yeah, well they warned us about Y2K as well, and that was a bust.” I have read similar comments before and even heard similar sentiments from people I know. The truth is that Y2K was a real problem that would have caused real chaos if it hadn’t been fixed in time. However it was fixed in time, and the fact that no significant problems occurred on January 1, 2000 is a testament to the amount of planning and work that went into fixing it. The fact that the general public thinks it was a bust proves that it was successful.
I know that there were Y2K problems in the database server that I worked on at the time (and continue to work on), and I know that they were fixed beforehand. Our problems were fairly minor, but I know of other problems that were not. Gail worked for a large steel company at the time (still does, kinda), and some time in the late 90’s, they did some Y2K testing. They simultaneously reset all the clocks on all the computers in the plant to 11:30pm December 31, 1999 and fired ’em all up again. A few seconds after the clocks hit midnight, everything shut down. The problem was eventually traced to an exhaust fan deep in the bowels of the plant, which decided that it hadn’t had any scheduled maintenance in a hundred years, so it shut down. All the systems that depended on that fan to be running also shut down, and the failure cascaded upwards until nothing was running.
If they hadn’t done the testing, the plant would have shut down a few seconds after midnight on New Year’s Day, and it might have taken them a couple of days to find the problem and a couple more to get a new fan installed. This is assuming that the fan was the only problem. When every hour not producing steel costs your company hundreds of thousands (if not millions) of dollars, a five-day outage would be devastating. Now think: what if that same brand of exhaust fan was used in your local power or water treatment plant? Could half your city live without power or running water for a week in January? What if a similar failure occurred in an air traffic control system? Or some safety-related subsystem in a nuclear power plant? Or the computer controlling the respirators in your local ICU?
The fan was fixed or replaced and the test was repeated. I don’t know how many times they ran the test, but when the real December 31, 1999 arrived, the plant kept producing steel like it does through every other midnight. Many hours and dollars were spent in advance to make sure that the problem was solved before it happened. This was done in countless other factories, businesses, hospitals, airlines, and such (not to mention every software development company) so that when January 1, 2000 arrived, all the hardware and software would handle it.
The people who were expecting nationwide blackouts or planes to start dropping out of the sky at midnight were surprised to find that the number of actual problems was very small. Many people assumed that this meant the whole “Y2K problem” was overblown or some kind of industry hype. It wasn’t. It was a real problem with an absolute deadline that could not slip. It was solved in time thanks to the combined effort of thousands of software developers (who, admittedly, created the problem in the first place) and IT professionals who put in a lot of effort so that people would never know there was a problem.
This, of course, is part of the thankless world that IT professionals live in – if they do their job properly, you don’t notice them. You might even mistakenly think that they do nothing. Every morning, you arrive at work and check your email or internet connection and find that everything is working properly. How many of those mornings have come after nights where the IT staff were up until 4am fixing some network or hardware problem? I’m sure you don’t know, but I’ll bet that it’s more than zero. Tell ya what – next time you see your sys admin walking through the halls at work, say thanks.
Attention Facebook readers: You might want to click the “View Original Post” link at the bottom of this note. Facebook sometimes messes up the formatting.
Back in May 2009, I wrote an article comparing the Chrome and Firefox browsers. Since then, it has been by far the most viewed page on my blog. From the day it was posted until today (almost six months), that particular article has accounted for about 80% of all pageviews on my blog. I’ve had days where 110 people visit my blog and 103 of them view that page and that page alone. I use mybloglog.com to track which pages are viewed the most and how people find my blog, and here’s a piece of the results for one day. Note that this is a fairly typical day. I don’t know why mybloglog can’t collapse all of the “chrome vs firefox” entries into one.
Anyway, after about six months of using Chrome pretty much exclusively, I decided to revisit this comparison and see how much of it is still valid. To that end, I reset my default browser back to Firefox for a week.
Note that I am comparing the “generally available” versions of Chrome (184.108.40.206) and Firefox (3.5.5), not development or beta builds.
Advantages of Chrome
- Chrome starts up almost instantly, while Firefox takes several seconds before it’s ready to go. Both are still faster than IE for me.
- Chrome updates itself completely silently. Firefox tells you there’s an update available and asks if you want to install it. Actually doing the install is pretty painless, but it asks you if you want to install the update when you start the browser, which is usually when you are trying to do something with it. Frequently I don’t want to wait while it installs an upgrade and then restarts itself, so I end up trying to remember to do it when I’m done. I have no idea when Chrome updates itself, because it does it silently in the background and then the changes take effect the next time you shut it down and start it again.
- Chrome searches your bookmarks and previously visited sites extremely quickly, so when I start to type a URL, it comes up with probable matches really fast. For example, I don’t have twitter.com bookmarked, but I can get there using tw because by the time I hit enter, Chrome has searched my previously visited sites and autocompleted “tw” to “twitter.com”. Until I started using Firefox again, I did not realize how cool this feature was and how quickly I came to depend on it. I would visit a site and not bookmark it, and then the next day if I wanted to find it again, I could type whatever part of the URL I could remember into the address bar and it would just find it for me.
Advantages of Firefox
- Chrome still doesn’t have plug-in support. If this isn’t number one on the “must get this done” list for Chrome, someone needs to be fired. Yes, I know this is at least mostly working in the dev builds.
- When Chrome isn’t going really fast, it seems to be going really really slow. I had a situation on my computer recently where everything seemed to be taking forever – compiling was taking 20-30 seconds per file (rather than the <1 it should take), and a test that was running at the same time was taking minutes rather than seconds. I looked at the task manager, and the two processes taking up the most CPU were Chrome and our stupid virus scanner that grinds my machine to a halt and IT won’t let me configure it despite the fact that it prevents me from doing my job efficiently (but that’s a rant for another day). I shut down Chrome, and within a few seconds everything sped up noticeably (though not as much as it should have because of the stupid virus scanner). I am going to keep an eye on this, but it may be a showstopper.
- Perhaps related to the previous problem – every now and again, usually when my machine is very busy, I enter a URL in the address bar, hit enter, and nothing happens. I have seen pauses of 30+ seconds before it even changes the status to “resolving whateverhost.com”. Firefox doesn’t have these complete blackouts, but just goes really slow in those situations. I rarely see this or the problem above (#2) at work, but it happens a lot at home – I think it may actually be related to the VPN I use.
- Bookmark support has been improved in Chrome to the point where this is no longer an advantage of Firefox. Firefox supports keymarks which Chrome does not, but Chrome’s searching of bookmarks is so fast this is hardly necessary, other than the magic %s searching thing that Firefox supports. XMarks support is still missing though (it’s in beta).
- On a site with lots of Flash (i.e. games), sometimes everything seems to slow down to a crawl after 10-15 minutes or so. Sometimes it speeds up again after a while, but other times I have to just give up on the game. This happens in both Chrome and Firefox. Don’t know about IE.
For now, I’m going to stick with Chrome, but as I said above, I’m going to keep an eye out for machine slowdowns and see if closing Chrome fixes them. If that continues to happen, I will have to go back to Firefox.
I kind of miss the plug-in support from Firefox, but Chrome is still pretty peppy and quite honestly, I feel like Firefox is starting to pick up the bloat that IE has had for years. Chrome still feels small and sleek.
I’m surprised that adding plug-in support is taking as long as it is, but I also understand that this basically amounts to allowing the general public to add executable code to your application on the fly. Getting this right and making it usable and flexible while remaining robust is difficult.