Posts Tagged ‘google Lively’

Firefox 4.0 Beta 1, bringing major changes released

Monday, July 19th, 2010

Firefox 4.0 Beta 1, bringing major changes released

Mozilla Firefox is, without doubt, one of the revelations of recent years. Although having to fight off serious competition, it has managed to overcome browsers like Google Chrome, Safari, Opera and set itself as a serious rival for Internet Explorer, the number one browser for as long as we can remember. This ascent is mostly due to Mozilla’s constant desire to improve its products. We’ve lately discussed about the Firefox 3.6.4 Beta Build Release and then about the Final Mozilla Firefox 3.6.4 Release and just when we were getting ready to announce the 3.7 version, in a last moment move, Mozilla renamed it to Firefox 4.0, our star today.

The new release is meant to refresh the image of the browser, making it faster and better looking. One of the main things that have changed is the interface which now allows the users to show or hide the tabs and the menus displayed in the upper partof the window. A significant number of other changes have been made, amongst which the new single button for stop and reload functions, the Home tab, a bookmarks button and an application tab. Furthermore, crash support and protection have been added, while running either Adobe Flash, QuickTime or Microsoft Silverlight plug-ins.

(more…)

Chrome OS proves Google can hype, but can it win?

Monday, July 27th, 2009

Chrome OS proves Google can hype, but can it win?

Google becomes more like Microsoft every day. It used to be that only Microsoft could pre-announce a product to mass hysteria (and mass exodus of start-ups dabbling in the area), then proceed to under-deliver for the first few iterations of the product and still make billions in the process. With Google Chrome OS, Google has signaled that it, too, can over-commit and under-deliver and still mint billions.

Perhaps equally dismaying, as Anil Dash suggests, is that Google may be having “its Microsoft moment” and starting to develop software to work nicely with its other software…rather than actually building software that its customers want.

But let’s step back and strip away the frenzied media response to Google Chrome OS to determine what, exactly, Google announced: Google announced that it was shipping Ubuntu.

No, Google isn’t calling it Ubuntu, but Chrome OS is nothing more than the promise of an Ubuntu fork. Given that we have Ubuntu and plenty of other Ubuntu forks today, what’s the big deal?

Heck, for that matter, we also have Jolicloud, another Linux fork that promises to be an “Internet operating system” for Netbooks, just like Chrome OS. (Ubuntu makes largely the same claim.)

The difference, of course, is that you can actually use Jolicloud today (alpha version), unlike Chrome OS, and I’m actually typing this on an Ubuntu-based Netbook. (Incidentally, you’ve got to think that Jolicloud’s investors were kicking themselves last week when Google announced Chrome OS a day after they announced Jolicloud’s funding.)

So, Google will ship an Ubuntu fork, but one that presumably will come with its own secret sauce. Why? Well, as CNET’s Rafe Needleman generously suggests, because “The stakes are big enough that it’s worth the shot for Google.”

Maybe. Maybe not.

Let’s assume “Maybe.” This still leaves Google with the stated intent to tackle a Lilliputian market that only the Linux crowd seems to get excited about, which is why Barron’s slaps the idea around:

I think Google misunderstands the nature of netbooks, which simply are small, cheap, lightweight PCs. Early versions ran Linux, and didn’t sell. Once the netbook companies loaded them with Windows, sales picked up. On its last earnings call, Microsoft noted that the attach rate for Windows on netbooks had reached 90%. The people have spoken. Netbooks are a misnomer; while people do use them to connect with the Web, they use them for a lot of other things. Customers want netbooks to run standard software, including Office. And I doubt there will ever be a version of Office for Chrome OS.

Of course they won’t support Microsoft Office. They’re going to support Google Docs! (See “Microsoft moment” above.) Much as I like Google Docs, and much as I like OpenOffice and a range of alternatives to Microsoft Office, the reality is that if you don’t support Microsoft Office, you automatically limit the market appeal of your operating system, a lesson Apple learned. Apple’s support for Office was the beginning of its rise within enterprise computing.

It’s just incredibly hard to overcome the inertia of an incumbent in an established market. Google looks smart when it is changing the rules for computing (giving search away and charging for ads, moving e-mail to the cloud, etc.), but when it competes with Microsoft on its terms…it’s likely going to lose. Mozilla’s Asa Dotzler gives a hint as to why. (Spoiler: It’s the installed base, stupid):

New markets on the Web can emerge and grow really quickly. There’s lots of opportunity for something like Facebook to take over in just a few years. But that’s not really the case for PCs and desktop software. The installed base is just really, really large, and the growth and upgrade cycle are much much slower than with Web services.

(more…)

Windows 7 will give boost to PC hardware

Monday, July 27th, 2009

Windows 7 will give boost to PC hardware

Windows 7 will be more than just a better interface. Under-the-hood changes will allow chips from Intel, Nvidia, and Advanced Micro Devices to ratchet up Windows 7 performance above previous Microsoft operating systems.

Microsoft on Wednesday said it has finalized the code for Windows 7, set to ship with new PCs starting October 22. Improvements will include how Windows handles multitasking, graphics acceleration, and solid-state drives.

Microsoft is working closely with Intel, whose chips will power the vast majority of PCs running Windows 7. A July 22 post from Joakim Lialias, Intel Alliance Manager for Microsoft, described how Microsoft and Intel “saw unique opportunities to optimize Windows 7 for Intel processor technology” in the areas of performance, power management, and graphics.

In his blog, Lialias focused on improvements to multitasking based on “SMT Parking,” which provides additional support to the Windows 7 scheduler for Intel Hyper-threading Technology. With Hyper-threading, the operating system sees a single processor core as two cores. For example, a quad-core system would be seen as having eight cores, thus potentially improving multitasking–or doing tasks (threads) simultaneously.

Hyper-threading is back in vogue at Intel after being pulled from Intel Core 2 chips (it debuted in the Pentium 4 processor). Nehalem Core “i” series processors use Hyper-threading, as do Atom chips. Intel, in fact, now includes Hyper-threading as part of a chip’s core specifications. The Core i7-975 processor, for example, is listed as “4 Cores, 8 Threads.”

Lialias also mentioned enhancements to boot and shutdown times. “Our mutual goal was to provide the most responsive compute experience possible.” (Lialias’ blog was cited in a PC World article.)

Windows 7 will also do more than previous operating systems with graphics–and here, DirectX 11 stands out as the most highly anticipated technology. A recent AMD blog describes a “beast called the tessellator…which enables games developers to create smoother, less blocky and more organic looking objects in games.” The blog discusses how DirectX has been redesigned “to ensure that it is much more efficient” at using multicore processors, such as the AMD Opteron chip.

Beyond games, Windows 7 has the potential to turn a graphics processing unit (GPU) from AMD or Nvidia into a general-purpose compute engine, used to accelerate everyday computing tasks like a CPU. Specifically, “the compute shader” can be used to speed up more common computing tasks. The buzz word used to describe this technology is a mouthful: GPGPU or general-purpose graphics processing unit.

(more…)

Review: T-Mobile myTouch 3G with Google

Monday, July 27th, 2009

Review: T-Mobile myTouch 3G with Google

It’s been nine months since I first dabbled in the world of Android. It wasn’t a pretty picture then, but a lot has changed in those short nine months. The platform has grown and become more stable. The Market is filled with useful and enjoyable apps. Cupcake has had the biggest impact thus far but we eagerly await what Donut has to offer.

Changes to the OS have been well publicized and covered at length, but we’ve been stuck with one piece of hardware, the G1. Despite its many inadequacies, it’s managed to carry the platform until now. Enter the myTouch 3G with Google from T-Mobile. It’s a rapid departure from what we’ve grown accustomed to with the G1. It lacks a physical keyboard, but has a boost in RAM ROM and one key software enhancement that many have been longing for. It also falls in line with the rest of HTC’s gorgeous hardware lineup. Many will have to wait until August 5 to pick up the latest Android device, but we’ve had one for a little over 48 hours and we can’t put it down.

Let’s start with the operating system. Just like the G1, the myTouch runs a flavor of Cupcake (1.5), COC10, that doesn’t seem to differ from the CRC1 build that was pushed out over the weekend for the G1. HTC really rained on T-Mobile’s parade by introducing the Sense UI on the Hero because it makes the generic Android UI even uglier, but it’s much snappier than the Hero’s Sense UI.

Despite its lack of a physical QWERTY keyboard, the myTouch’s virtual QWERTY works just fine. Those with bear claws will need to resort to using the landscape keyboard because the 3.2-inch screen leaves very little room to comfortably type on the portrait keyboard. This happens to be the one area where I’m tempted to make a direct comparison to the iPhone. The 0.3-inch advantage makes a huge difference.

Enabling haptic feedback makes the experience marginally better but it’s still difficult to walk down the street and compose emails or text messages one handed in portrait mode. You’re forced to constantly look down and make sure you’re tapping out what you want.

The one software advantage the myTouch has over the G1 is Exchange support. G1 owners will not be receiving this update so keep this in mind if your company doesn’t issue BlackBerrys or Windows Mobile devices.

Battery life seems to be marginally better than the G1, but only by a hair. Alas, all 3G devices packed with Wi-Fi, GPS and a decent browser will suffer from horrendous battery life. The myTouch 3G is no different.

(more…)

Update Available on the Stable, Beta and Dev Channel: Chrome 2.0.172.37 and Chrome 3.0.194.3

Tuesday, July 21st, 2009

Update Available on the Stable, Beta and Dev Channel: Chrome 2.0.172.37 and Chrome 3.0.194.3

Google, the Mountain-view based company that we all know for their search engine, has released an update for the Chrome 2.0 browser. The update, which carries the version number of 2.0.172.37, has been released on the Beta channel and on the Stable channel and is meant to fix some bugs and some security vulnerabilities affecting the software.

Chrome 2.0.172.37 fixes the following bugs”
- Fixed solving CAPTCHA images at Orkut.com.
- Forward and back navigation works even when the user is redirected.
- Some CET locales did not properly recognize daylight savings time. This issue has been fixed.

Chrome 2.0.172.37 version changes
- V8JavaScript engine version 1.1.10.14
- Google Gears 0.5.25.0

The Chrome 2.0.172.37 also addresses two security vulnerably affecting the web browser. One has been given the critical rating (run arbitrary code with the privileges of the logged user) while the second has been rated high (attacker might run arbitrary code on the targeted machine within the Chrome sandbox).

An official description of the two security vulnerabilities has been provided by the Google security team, the one who uncovered these security holes:

Critical: Memory corruption in the browser process

A compromised renderer (tab) process could cause the browser process to allocate very large memory buffers. This error could cause the browser process (and all tabs) to crash or possibly allow arbitrary code execution with the privileges of the logged on user. To exploit this vulnerability, an attacker would need to be able to run arbitrary code inside the renderer process.

(more…)