Tuesday, July 14, 2009

Steps to Integrate an HXS into an MSI

:Link to Article:
Walkthrough: Registering and Integrating a Help Collection By Using Windows Installer

MSDN is a great resource; alas, finding relevant information on it is very difficult for two reasons. Firstly, no search engine does a good job of indexing the files. Secondly (and primarily), the page authors give the pages the most obscure possible titles. Take for instance the page I just linked to: why can't the summary be "Steps to Integrate HXS into MSI"? Since the page author hasn't done this, I have. It's all in the hands of the Google web spiders now - once they pick up this page and index it, others like me looking for this information won't have to search as much.

To use my close friend Juggy's favorite quote - "Power to the People!"

Hokum - Survey Shows Almost No One Will Switch To Microsoft Bing

:Link to Article:
Third, yes, Bing has added some cool innovations, but nothing that Google can't and won't copy immediately.

And that gets to the heart of Microsoft's problem here: Search isn't broken. The reason almost 70% of folks use Google is that most folks like Google and most folks are used to Google. If there's a 'better' search engine out there, most people probably don't know that it's better (because it's really hard to tell--in part because 'better' is in the eye of the beholder), and many people who can tell probably don't care.
A specious argument, at best, because it doesn't take history into account. When Google was first launched, people were very happy with the search options they had - Altavista and Yahoo. No one even thought they would switch to Google; case in point - Yahoo! is still the top dog in the AMEA markets. Google established a search monopoly only a few years ago, and though it has made incremental strides in its offerings since launch, it hasn't done anything along the lines of a revamp that Microsoft has undertaken with Bing.

Any prognostications on the future of the Search engine market are doomed to failure, because no one can really predict the psyche of users. If Bing continues to innovate past the "honeymoon" stage of its launch, I would be hard pressed to believe that it won't eventually take market share away from Google. Apropos the discussion of Google copying Bing, two things come to mind. First up, a few months ago, no one would even entertain the idea that Google needed to copy anything from Microsoft - the Bing team should pat themselves on the back for a moment. Seconly, the problem with copycat implementations is that people are observant enough to recognize one on sight; human behavioral studies have shown that "discerning" people usually pick the original over the ersatz version.

Sunday, July 12, 2009

Fix - AT&T The Remote Party has ended this connection

:Link to Article:
Use the automatic settings manager under All Programs -> Accessories -> Connection Setup so that you get MEdiaNEt as a GPRS connection configured on your phone. Mind you, the configuration as pushed to your phone by AT&T doesn't really work.

The fix:
Go to Settings>Connections>GPRS,
Highlight IMS CINGULAR And click ok.
It should Connect to: The Internet
Under Access Point It currently says: ims.cingular
THIS IS THE PROBLEM HERE>>>>>>>> Change this to:
wap.cingular
USER Name: Should Be Blank
Password: Should Be Blank
Authentication: Should be CHAP
Primary DNS: 0.0.0.0
Secondary DNS: 0.0.0.0
IP ADDRESS: should Be Blank As well...

It's been a while...


Since I:
- Had to completely reset my phone and start afresh. Apparently, sending and receiving about 3000 text messages and never deleting them from your phone is a bad idea. The database gets really corrupted - like I knew that was gonna happen
- Was part of a team that won its semi-final match and is headed to an ARCL divisional final. Hurrah!
- Came to work on a Sunday at 8pm
- Didn't have Internet at home
- Won a squash match this emphatically (4-0)

But enough bullet points; you would mistake this for a powerpoint presentation. I have been mulling over a few topics to write forth on, but the last two weeks have been the most hectic of 2009 (or so it seems). Arun married Purvie last weekend, and as one of his close friends in Seattle, I was assigned a few tasks during the wedding. All but one went off very smoothly, and in my books, that's a job well done. Surd was in town this past week as well - the guy unfortunately got the flu while on vacation, and unintentionally left it behind for me to pick it up as well. I've had a scratchy throat and have run a fever since Friday, but it isn't anything serious. At least not serious enough to prevent me from playing every sport I like this weekend!

Kapil, Prachie and Aadi have moved to Seattle from Dallas, and I couldn't have asked for something better. In Kapil, I have found a partner in crime for all my sporting activities - he plays tennis, cricket, golf, squash and racquetball - yippee! Wait, I forgot to mention, he just ran the Dallas half marathon (maybe it was the Austin one); more motivation for me to run and a companion that is willing to schlepp it to the West Side every now and again. The pot gets sweeter by the day.

In what I believe is the natural progression of things, Ashish and I tried something new last evening - we went to a lounge and spent quality time with Samrah and her friends. The outcome was surprising to us both - the conversation was crisp, the people were friendly, and there was none of the show-boarding that so characterizes trips to a club or bar in Belltown. The two of us have vowed to have more nights like these - where the people are few yet interesting, and we can walk away feeling like we learned something about someone new, rather than nothing about everyone around us. Next week, it's Lauren's house warming party...

On to the new week it is. My work is progressing at a good clip and this week is going to fly by pretty fast. I'll be in Vegas, India and Hawaii over the next two months - give me a shout if you're going to be in any of these locales, and I'll share my dates with you. Have a good week.

Monday, July 06, 2009

Adobe Flash and a HUGE missed opportunity with HTML5 video

:Link to Article:
Update: Thanks to John Gruber, Wikipedia and an Anonymous Reader, I now know that FLV is just a container format. The contained video still needs to be encoded with a specific codec; H.264 and Ogg are the prevalent codecs to accomplish this.

The author of the HTML5 specification has given up on resolving, what can best be termed an impasse, the issue with the <video> tag. The issue is that H.264 and Ogg Theora are being considered as the de facto video encodings for the Web of tomorrow, but no browser vendor can provide cross platform implementations of both codecs. Some vendors have expressed concerns around patents, while others have raised valid concerns about the encoding quality of Ogg. In all of this, I wonder why no one is even considering Adobe Flash's FLV format as the one "format" that rules them all. Most video on the web is delivered via the Flash player. The choice of video codec should therefore be a no-brainer!

It isn't, and the only thing I can think of is licensing of the FLV codec. That's hokum though - the flash codec is already installed on more than 90% of computers in the world today. Adobe has been more than responsive with fixing security issues, has a great track record with providing both tools to edit videos and has invested heavily in improving the encoder's quality over the last 10 years. Can someone help me understand why FLV is being marginalized here?

Wednesday, June 24, 2009

The Palm Pre's address book criticisms

:Link to Article:
No review of the Palm webOS is without a mention of how the address book is very hard to navigate. True to form (and thoroughness), Ars' review of the webOS has this to say:
"Good luck browsing the Pre's address book—as most reviewers have pointed out, it's a mess. The webOS expects contacts to exist as a collection of federated services that you query, not as a structured, browsable repository. So when you add contact services—Google, Exchange, Facebook, AIM—to the Pre, it dumps all of the contacts that it pulls from these services into one impossibly long alphabetical list (mine is about 450 entries)."
In the last year since I have had a Windows mobile phone, I have never once browsed through my Contacts/Address Book. If I want to call or text someone, I start typing their name or number using the keypad - if they are in my address book, their name shows up; if they aren't, o well! What I'm trying to say is "Navigating the Address Book" is a function that was absolutely necessary circa 1999 when phones didn't have an awesome search feature. We're in the 21st century guys - stop mentioning moot points in your reviews.

For my money, the fact that navigating the Pre's address book is so difficult is a definite step forward. Like all new paradigms, this one will take some adjustment but eventually, it is for the best. There are better things to do than navigate a list of 100+ entries... When you launch the Pre's address book, you're supposed to just start typing the name of the contact that you're looking for on the built-in keyboard, and let webOS zero in on the desired record. If you try browsing for the desired contact, then you're wasting your time, because the data is just not structured for this kind of discovery. Pre wants you to query a service, not browse a repository."

Ars reviews the Palm Pre, part 2: the webOS experience - Ars Technica

:Link to Article:
"One of the established truths of the past 50 years of computing is that the same basic problems crop up over and over again in different forms, so that technological advances are less of a linear march forward than they are a sort of spiral that turns the same corners again and again, but on a different level with each rotation."
Profound