After Chrome’s quiet release, almost too quiet for technology writer Michael S. Malone, and a not-so-quiet EULA scandal, Chrome comes under scrutiny from technical analysts.

What’s the verdict? Some like it, some are dissatisfied with it, but there appears to be one general consensus in that Chrome still has a lot of polish-work to be done.

Some of the principal concerns cited by reviewers include the fact that Chrome’s bookmark manager is extremely bare-bones, and offers no advanced organization features, no backup option and no bookmark synchronization. Another concern is its lack of plug-in support.

Although Google has stated that plug-ins are on the way, you’ll miss them until they do arrive. It has poor NPAPI support and no ActiveX support whatsoever, and this, although understandable as ActiveX is a Microsoft-owned technology intended for Windows and not commonly used by multi-platform browsers, will most likely be one of the main reasons for Chrome’s slow adoption into the corporate environment, where in-house web apps make heavy use of these APIs, the latter especially.

A few interface features have been cited as well, most notably the fact that Chrome does not notify the user upon closing multiple tabs like Firefox does, but it is unsure whether these are to be attributed to Chrome’s early development stage or the minimalistic interface which Google have opted for.

Finally multiplatform support is also asked for, as Mac and Linux users are at a disadvantage considering the lack of a version of Google’s browser for their OS.

Nevertheless, none of these are insurmountable problems, and given time all things point to Chrome’s growth as a full-fledged next-generation web application with all the features today’s selective users have come to expect from their browsers.