Showing posts with label opinions. Show all posts
Showing posts with label opinions. Show all posts

Tuesday, January 6, 2009

Bringing credibility to the All-Star game


The official end of the NHL All-Star Game balloting period fits in nicely with the unofficial start of the "why we heck do we need to change the All-Star Game/All-Star Game at all" season.

Personally, I don't really care. The All-Star Game ceased to hold any real attraction for me years ago. I accept it for what it is - a meaningless, zero-intensity game of shinny, albeit one that features many of the most talented hockey players in the world.

That said, I remember what the game used to mean. It was a spectacle and it was special and I looked forward to it each season. Theoretically, that's what it still could be today.

From an NHL marketing perspective, it represents another entry point to sell the game to kids, and those that don't really know much about hockey, to get them hooked or to deepen their bond. As things stand, it's an opportunity that isn't being fully exploited.

In recent years, the hockey community has discussed ad nauseum potential format changes that might re-energize the "mid-season classic." We won't go down that road again right now (personally, I don't really like the North America VS. World thing, with the "US/THEM" feel it gives off...none of that nonsense anymore guys).

One thing to look at is, How the starters are selected because, ironically, the very method they instituted to give ownership to their customers is undermining itself.

The electronic ballot stuffing, or the spectre of it, is a turn-off. While it may not be reflected this year in total number of votes cast, it's impossible to tell since fans can vote as frequently as they like. So when Sidney Crosby "breaks Jaromir Jagr's record" for votes received, it's totally meaningless. Using this method, Chris Simon may break Crosby's record one day (no offense to Chris Simon there).

Here are a few ways they could alter the selection process to lend it more credibility.

1. Have the players vote. Regardless of format they choose to use (East vs. West, North America vs. Europe, Under 28's vs. Over 28's..yes I know that last one sounds real stupid), players would select their side's starting lineup , but would not be permitted to cast ballots for their NHL teammates.

2. Devise a statistical formula to pick the starters. Perhaps it's different for forwards, defensemen and goalies. Maybe each conference's top goal-scorer, assist-collector, plus-minus player and save percentage stopper are all guaranteed spots. Maybe the formula is more complex. Either way, it'd be black and white.... The best player up to that point of the season gets to play in the game.

3. If it remained important to have some fan participation, hold a contest in which two lucky winners got to pick the starters in conjunction with each side's coaching staffs or executive boards. That would draw visitors into websites (that can't be the driving reason behind fan balloting, can it?) and eliminate the risk of a non-worthy player being selected.

4. Move the All-Star games out doors! in my opinion (by it being only my opinion, you're free to disagree with me) these outdoor games have been great! Make them a yearly thing by using them for the All-Star game.. The NHL has already seen how many tickets they can sell to a "regular" or "exibition" game, imagine how many more they can sell with 2 teams full of stars!!!.

I'm sure there are MANY other tweaks, amendments or overhauls that could be made to breathe life and credibility back into the event. Let me know what you think would make the All-Star game better and more watchable.

Wednesday, December 10, 2008

Arranged marriages, Why? Why not?

Saturday, November 15, 2008

The browser wars are back!

At the turn of the century, Microsoft brutally vanquished Netscape in the browser wars. For a while, that victory appeared to be permanent. The battle had been a pretty ugly one: A federal court found that Microsoft illegally used its Windows monopoly to expand Internet Explorer's market share; Netscape never recovered from its loss. For most computer users, though, the browser wars were sublime: The Web browser was "invented" in 1992, and within five years, with hundreds of developers at both Microsoft and Netscape pumping out code, browsers became fast, stable, and capable of some very neat tricks.

These days, Web designers boast about all they can do with AJAX, the set of technologies that allow Web sites to emulate desktop-app behavior like drag-and-drop (ie Google Maps). AJAX runs on code that was created by Microsoft and Netscape as competitive weapons during the browser wars. Yes, today's glorious Web was made possible by yesterday's bruising business confrontation. All of us should rejoice, then, at the dawn of Browser War II.

Google has released a Web browser called Chrome. This new piece of software enters a crowded field of browsers looking for your love. Microsoft with its final revision of Internet Explorer 8,.(Both Chrome and IE 8 run only on Windows, though Google says it's creating versions for other platforms.) In June, Mozilla put out Version 3 of its popular open-source, cross-platform Firefox browser, in Version 3.1. The Norwegian software company Opera also released its latest eponymous, innovative, cult-hit browser. And Apple is now working on the next version of Safari for Mac and Windows.

All this competition is great news, because the world desperately needs a better Web browser. For at least the past four or five years, Firefox has been the gold standard among techies; I've been using it as my primary browser for at least that long. I loved it, I appreciated its smart, clean user interface, its tabs (although all browsers use tabs now, at the time when I moved to Firefox, this was the only browser to do so) and keyboard shortcuts, and most of all—Firefox's killer feature—its ability to run a wide range of useful third-party add-ons. But Firefox is hobbled by a couple of major flaws. It hogs system resources: Use it for a while, and it eats up huge chunks of your computer's memory, eventually slowing browsing to a near snail pace. Firefox is also prone to crashing: Load up an errant Web page, and you risk bringing the program to a halt. (This problem makes session-recovery add-ons like Tab Mix Plus essential.)

Admittedly, I'm not an ordinary Web user—I use my browser as a research tool, mail app, calendar, media player, and a tabbed to-do list. I live and breath the internet, I can't be without it... At any point during the day, I've got three or four browser windows open, each with 10 to 15 Web pages running in tabs (at least). I understand that this bespeaks a kind of insanity, but with Web sites growing ever more useful and Web users growing ever more addicted, it's the sort of insanity that afflicts an increasing number people.

The wonderful thing about Google's new browser, is that it's been built with the singular purpose of handling a hefty workload. While I'm not yet ready to switch to Chrome as my permanent browser—it's got some odd user interface quirks, lacks a few useful features, and doesn't have Firefox's hordes of plug-ins—I've found it to be impressively fast and stable. So far, it's run everything that I've thrown it's way without bringing my computer to a halt. For that alone, I really think that Google's on to something.

Just as Windows runs Photoshop and iTunes at the same time without letting each bother the other, or getting in each others way, Chrome lets its processes do different tasks in parallel. If one Chrome tab is busy loading Google Reader, another Chrome tab won't be crimped while refreshing the CNNSI.com website. Best of all, if one process crashes, your full browser session remains intact. I've inadvertently learned many different ways to make Firefox crash; none of these tricks worked on Chrome. The best I could do was crash a single process—this brought down an individual tab, but Chrome as a whole, kept running.

There are several more under-the-hood improvements. Google claims that Chrome beats other browsers at "garbage collection"— the computer-science term for how a program gets rid of memory it no longer needs. Better garbage collection significantly reduces how much of your computer's resources an application consumes. Google also wrote its own JavaScript virtual machine—the engine that runs all the fancy AJAX code that powers complex new Web apps—that it claims is faster and more stable than other browsers' scripting engines. Though I found Chrome speedy and less demanding on my system's resources than Firefox 3.0, its advantage isn't unsurpassable—Lifehacker's tests give the memory and speed edge to Firefox 3.1.

You aren't likely to notice Chrome's tech improvements when you load it up for the first time. What you'll see is a clean, minimalistic app, one missing several features that you're used to in other browsers. For example, Chrome presents no good way to manage bookmarks. Still, there are some innovative features. Instead of an address bar and a search box, Chrome uses only one input bar in which you're free to type either something like "ebay.com" or "policies of Barrack Obama" Chrome is smart enough to figure out when to take you to a Web page and when to perform a Web search. It also lists other recently visited sites containing ebay, obama, or other like terms.

I found some of Google's other user-interface tweaks a little more annoying than useful. Chrome places its row of tabs in the title bar, an area that in most apps isn't used for anything other than displaying the name of the program. This saves space on your screen, but it also eradicates one of the main ways people have grown accustomed to using tabs in browsers—you can't double-click the tab bar to open a new tab, like you can on every other multi-tab browser. (Double-clicking the bar in Chrome resizes the window.)

This is a petty nitpick, obviously. Chrome is very much a work in progress, a beta program that I expect will improve dramatically in the months to come. It shares two advantages with Firefox: Chrome is open-source, meaning outside developers are free to extend and improve it. And Chrome includes a plug-in infrastructure that lets people create add-ons. Because it's new, neither of these features is very important just yet. But if Chrome catches on, developers will likely build these and other great programs for it; theoretically, people could even take the best bits of Firefox and Chrome and build another single awesome browser.

For Google, Microsoft, and Apple, the browser fight is a means to other ends. Microsoft, which holds more than three-quarters of the browser market, looks at the Web as an extension of its operating system. As more of our programs move online, Microsoft fears that we might have little reason to stick to Windows; it sees control of the browser as a way to control the future of software development. Google seems to want to be in the browser business to fight Microsoft. The company's revenue comes entirely from the Web, so it's got to be wary that most of its customers come through software created by its main rival. (Google substantially underwrites both Firefox and Opera, which both feature Google's search engine as the default.) Apple, meanwhile, needs a browser to beef up its own platform—not only on the Mac but also on its phones and iPods.

Sure, these aims aren't entirely noble. But who cares? As the giants duke it out to come up with the best product, they'll copy and improve upon each other's innovations, bringing new features to all browsers. Chrome's immunity to crashing, for instance, is sure to push both Mozilla and Microsoft to improve their browsers' stability. Perhaps soon you'll be able to load up any browser you like and watch two dozen YouTube videos at once without fearing a crash—just like the Web was always meant to be used.

The gloves appear to be off!

Until next time........