Blog of Leonid Mamchenkov

Many of us, Gmail users, have been waiting a really long time for this, but now the wait is over.  Gmail blog announced task manager / todo list in Gmail via Labs extension.

We put your tasks in the same kind of window as chats, so they’re visible while you’re scanning your inbox, reading mail, or searching (and in Settings, too!). Just pop your list out into a new window to use Tasks outside of Gmail.

To enable Tasks, go to Settings, click the Labs tab (or just click here if you’re signed in). Select “Enable” next to “Tasks” and then click “Save Changes” at the bottom. Then, after Gmail refreshes, on the left under the “Contacts” link, you’ll see a “Tasks” link. Just click it to get started.

Excellent news for this morning.

We upgraded our development server to Fedora 10 over the weekend.  Among other things, it runs RT3 - excellent support, issue management, and bug tracking tool.  Once the upgrade was over, we ended up with a semi-working setup of RT3.  The emails were going through just fine, but the web interface was giving out a blank screen with no content or errors or warnings.

Googled a bit, but that didn’t help a lot.   Went through server logs and found an out of memory shout from Storable.pm:

2325:Callback called exit at
../../lib/Storable.pm (autosplit into ../../lib/auto/Storable/thaw.al)
line 415.

Googled for that, but it turned out that quite a few people have the problem with this module running out of memory.  And not only in RT3.

So I left it where it was and had some good night sleep.  And it helped.  In the morning, englightment came in, and I tried reloading the page with cookies and cache cleaned.  It worked.  And then it didn’t work again.  Cleaning cookies was helping for a couple of page views.  So I dived back into the RT_Config.pm file to see my options.  There it was.

=item C<$WebSessionClass>
C<$WebSessionClass> is the class you wish to use for managing Sessions.
It defaults to use your SQL database, but if you are using MySQL 3.x and
plans to use non-ascii Queue names, uncomment and add this line to
F<RT_SiteConfig.pm> will prevent session corruption.
=cut
# Set($WebSessionClass , 'Apache::Session::File');

Once I enabled Apache::Session::File, the problem went away.  We are now back to work, enjoying the new web 2.0 round corners interface, pastel colors, and more.

Google updated the design and interface of the RSS feed aggregator - Google Reader.  Here is a really small screenshot of how it used to look (stolen shamelessly from Google Reader front page - it seems like they forgot to update it):

And here is a really small screenshot of how it looks now (I made this one, you can make your own):

In my opinion, the old interface was much better. Colors and borders helped to visually separate the sidebar from the main content area, as well as news items from each other.  The new design is much “separated”.  Also, there are a few minor quirks and bugs here and there, which will hopefully get fixed in the next few days.  However, one thing is great about this new release - speed.  The new Google Reader is much faster than the old one.  Extra responsiveness can’t hurt, especialy thos of us who go through hundreds and thousands of posts in a fast paced manner.

We’ve been doing some interesting things at work, as always, with yet more people and Linux boxes.  And of the side effects of mixing people, Linux boxes, and several locations is this need for some sort of centralized logging.  Luckily we have either syslog-ng or rsyslog daemons installed on each machine, so the only two issues seemed to be reconfiguration of syslog services for remote logging and setup of some log reading/searching tool for everyone to enjoy.

As for log reading and searching, there seems to be no end of tools.  We picked php-syslog-ng, which has web interface, MySQL back-end, access control, and more.  There were a few minor issues during setup and configuration, but overall it seemed to be OK.  I also patched the source code a bit in a few places, just to make it work nicer with our setup and our needs  (both numerical and symbolic priorities, preference for include masks over excludes, and full functionality with disabled caching).  In case you are interested, here is a patch against php-syslog-ng 2.9.8f tarball.

Once everything was up and running and we started looking through logs from all our hosts in the same place, there was one thing that surprised me a lot.  Either I don’t understand the syslog facilities and priorites fully (and I don’t claim that I do), or there is just too many software authors who don’t care much.  Most of our logs are coming in at priority critical.  Even if there isn’t much critical about them.  Emergency is also used way too much.  And there is hardly anything at debug or info or notice levels.  (RT, SpamAssassin, and many other applications seem to be using critical as their default log level).  Luckily, that  almost always is trivial to fix using either the configuration files or applications’ source code directly.

For the last few days, the biggest thing in the technical news is Google Chrome browser (check the comics book, introducing the browser, download beta).  Sure, we had our share of browser wars, and we still do, but this is something completely different.  Most of today’s browsers started back in the days when the Web was totally different.  Since then, some browsers changed more than others.  Some new ones appeared.  But there was no a big break through.  It was mostly an evolutionary approach.

I’m glad to see these big news from Google, that they decided to create a new browser from scratch.  They built it with solutions to many of the today’s problems.  They’ve put some flexbility for the future.  And it seems like they’ve thought a lot about it.

I absolutely support their choice of open source in this matter.  Nobody, not even Google can build a browser that will satisfy everyone and everything, and then keep developing and maintaining it.  That’s not possible with the current state of the Web affairs.  The only way to pull it off is to open source it, so that the Web itself could help them with this mega task.  Also, it’s nice to see that they don’t want to reinvent the wheel either - taking both WebKit (open source web rendering engine) and V8 (open source JavaScript implementation) is smart decision.

It’s nice to see some real competition in the browser world.  Microsoft’s Internet Explorer has changed a lot in the last few years, and the biggest reason for those changes was Mozilla’s Firefox.  Firefox changed a lot too, but it sure could use a push from another open source product.  Google’s Chrome could be exactly that product.

Also, for once it would be nice to see a browser built by someone who knows the Web, and not how to build software.  Yes, browser is a software, but it’s not on its own.  You need to know more and have access to a lot more data to build a good browser.  In particular, what, who, and how uses the Web.  Neither Microsoft, nor Mozilla, nor Opera Software have these information.  Or at least not on the scale that Google has.

And, of course, there always will be downsides to any good initiative.  In the case with Google Chrome, my biggest concern is the situation with themes and extensions.  Firefox has an excellent community in this regard.  This community has built all possible and impossible thems and extensions for practically anyone anywhere.  And it still continues to do so.  Google Chrome starts from scratch, so there won’t be anything for some time.  And since the whole browser thing is new, it’ll need to start with a new set of developers, testers, users, and so on.  And so it will take them some time build that all up.

As with anything, there are a billion of other ways to look at Google Chrome, the way the Web is going, the way Google is going, the way software development in general and IT as a whole is going.  But I’ll leave that up to you.  Here are, however, a few links to get you started.

• Slashdot : Google Chrome, the Google Browser
• Slashdot : Mozilla’s Thoughts on Google’s Chrome
• Linux Weekly News : The Google Chrome comic book
• PCWorld : Official Google Chrome Screenshots
• Google Blogs Search results for “Google Chrome“