Thursday, September 29, 2011

XUV 500 - Most hottest car from Mahindra

At last today is the day , for the official launch of Mahindra & Mahindra’s hottest car in India , the XUV 500. Yeah I know all of them are eagerly watch for 9:00 for it official launch in , unfortunately the site is down due to heavy traffic. Now need to search for the youtube upload. In what range it comes ? Its in between the SUV and Premium SUV(Premium SUV range which comprises of the Chevrolet Captiva,Toyota Fortuner, Honda CR-V,Mitubishi Outlander).The base model starts with Ex-Showroom(Delhi) price of 10.8 Lakhs. So its a real competitor for the recently release Tata Aria 4x4 which has the starting tag of 11.5 Lakhs.

Some of the specification/features of XUV 500 are
1)    Powered by a 2.2-litre M-Hawk engine
2)    140bhp , 330Nm of torque
3)    Six-speed manual gearbox,front wheel drive transfer case(Base mode)
4)    High end models have all wheel drive layout
5)    Front end treatment with projector headlamps
6)    LED day-time running lights
7)    Large front bumper with streaked air dam
8)    Recessed fog lamps
9)    Disc brakes abound on all four wheels
10)    ABS, EBD plus ESP,Traction control, Hill decent control
11)    Driver and front passenger air bags
12)    Hill descent control for top end models
13)    ARAI certified mileage of XUV500 is 15.1 kmpl
14)    Static bending projector head lamps with LED parking lights
15)    6-inch monochrome infotainment display, Glass embedded antenna
16)    Integrated music system with CD/MP3, iPod & USB connectivity
17)    4-Door speakers with 2 tweeters on dashboard
18)    DIS in-built in infotainment system, Intellipark
19)    Smart rain sensing wipers, Intelligent light sensing headlamps
20)    Digital immobiliser, Digital trip & tachometer, Disc brakes on all wheels
21)    Dual airbags (Driver + Passenger), ABS with Electronic Brake-force Distribution (EBD)
22)    Side impact beams, Crumple zones for crash protection, Tubeless tyres
23)    Full wheel caps, Racing-styled twin exhaust, Front and rear fog lamps
24)    Chrome Scuff plate for 1st and 2nd row, Streamlined Roof-rails, Cladding strips
25)    Sporty dual tone interiors, Cubic-printed centre console with metal accents, Twin pod cluster with 3D-dials
26)    Tilt power steering, Fully automatic temperature control (FATC) & dual HVAC
27)    Premium fabric seats, Power-foldable and adjustable ORVMs
28)    Centre arm rest with cup holders in 2nd row, Height adjustable seat belts (front row)
29)    8-way adjustable seats including height and lum, bar adjust (driver's side)
30)    Cruise, audio, phone controls & voice command switches on steering
31)    Power windows with driver side express down, Remote tail gate opening
32)    Flip key with remote central locking, Storage spaces on centre console
33)    Reading lamps in all 3 rows, Conversation mirror, Tinted solar-reflecting glass
34)    Mobile charging points, Rear washer, wiper and de-fogger
35)    Follow-me home headlamps, Lead-me-to vehicle lamps, Illuminated key rings
36)    Puddle lamps, Entry assist lamp, Door ajar lamps, Camping lamp
37)    Remote fuel lid opener (electrically operated), Glove box with laptop holder
38)    Flexi seat configuration for convenient storage (60:40 fold 2nd row, 50:50 3rd Row)
39)    Flat fold 2nd and 3rd row seats, Umbrella holder
40)   Reverse parking sensors/Reverse guide system and Cruise control plus Traction control

Premium features include
1) Leather upholstery, 6-inch colour touch screen infotainment display, DVD player
2) GPS Navigation with touch-screen and audio support, Tyre-tronics
3) Side & curtain airbags, Electronic Stability Program (ESP) with rollover mitigation
4) Hill Hold and Hill Descent control, Alloy wheels, Telescopic steering

Ex Showroom price
Mahindra XUV 500 W8 4 wheel drive - Rs 10.80 lakhs
Mahindra XUV 500 W8 2 wheel drive - Rs 11.95 lakhs
Mahindra XUV 500 W8 4 wheel drive - Rs 12.88 lakhs

Comfort features include
1) Power steering, Power windows, Remote central locking/Keyless entry system
2) Climate control system, very unique design for AC vents
3) Dash integrated music system, AUX, Bluetooth and USB support
4) 8-way adjustment for driver's seat, Electrically adjustable and retractable ORVMs
5) Global positioning system, AC vents for rear passengers, DVD player
6) Dual-tone theme for upholstery, dashboard and central console

Colors available
1) Satin White
2) Volcano Black
3) Amazon Green
4) Moondust Silver
5) Tuscan Red
6) Opulant Purple
7) Dolphin Grey

Initial production capacity of 2,000 units a month.As per the plan the same will be launched in South Africa tomorrow. "In the next six months, it will be launched in Australia, South and Central America, Western Europe and SAARC countries," M&M President (Automotive and Farm Equipment) Pawan Goenka told reporters

Wednesday, September 28, 2011

Can Amazon Kindle Fire replace iPad ?

After lot of buzz we finally got the details of Amazons brand new Kindle Fire, they called as replacement of iPad. After knowing the features of Kindle, what I think , why Amazon came with this is not to replace the iPad or RIM’s PlayBook or any android tabs. They are sure that with the classic kindle they cant survive in this market.The only thing that customers get attracted is with it price , just $199 for its 7-inch color touch-screen tablet with android 2.3. I think no one else is quoting lower than this. But do you think a person who carries this on his travel will accept a tab without a camera, yeah unfortunately no camera.

A normal DVD quality movie needs 2.8 GB of space, so Kindle Fire cant hold more than 3 movies, as its just  8GB of internal memory and no media slots. As usual Amazon limits to only 6 things that you can do with this product Newsstand for magazines, Books, Music, Movies, Docs, Apps and Web. Oh for got to mention in the first, It don't have 3G, but comes with Wi-Fi ( Thanks for that ) .

The good thing is you will get unlimited storage in the cloud, even though not attractive , this is one of the best feature that we need in the future. This is built with Texas Instruments dual core processor. After seeing this , I don't know its powered by Android 2.3 OS, as there is no evidence, by comparing other Android tabs, and its desktop is different by normal Android tabs. It has a speaker on one side and on the other a single button. Oops still I forget to mention that there is no Mic , so to call some one , need a phone :) forget about video chat,

Yeah it have amazing offer - $79-a-year Amazon Prime service, which offers free two-day shipping and unlimited streaming TV and video, comes as a free 30-day trial for each and every new  Fire owner. Even though it dont have port to connect to HDTV, still if you have a  device that supports Amazon Prime connected to your TV, you can watch a movie on the Fire to your TV.

It also promises a native email client where you can manage multiple accounts, but no demo is shown on the release. But if you really need a tab for read or browse internet this will be good enough and it had to get a Android tab less than $199. In that way it is a wonderful instrument , and can replace iPad, if you are not much bothered of video chat, playing with Apps or worrying of space. More that that its too handy to use.

Tuesday, September 27, 2011

Dart Rumors

This is how the Dart rumors came , just by an email chain
Not much at all is known about Dart, and mum's the word from Bracha, who posted to his Google+ and Twitter streams "all will be clear" next month after the keynote. But some intelligent guesswork (notably by sister site ExtremeTech's Sebastian Anthony) is pointing to the likelihood that Dart will be more like Java (an object-oriented language) than, say, C. Additionally, because Google already has one programming language, called Go, which is similar to C in some ways, it's likely that Dart will not try to cover the same ground. Plus, Bracha and Bak's backgrounds point more toward object-oriented languages than anything systems-related.

---------- Forwarded message ----------
From: Mark S. Miller <>
Date: Tue, Nov 16, 2010 at 3:44 PM
Subject: "Future of Javascript" doc from our internal "JavaScript Summit"
last week

On November 10th and 11th, a number of Google teams representing a variety
of viewpoints on client-side languages met to agree on a common vision for
the future of Javascript.

This document

is the result. It was first announced on Buzz at

Please forward this message to people and groups that should know about
this. This internal list,, is the place we
should have the Google-wide discussion of this document and these issues. If
you'd like to join this discussion, please subscribe at <>.

Executive Summary

Javascript has fundamental flaws that cannot be fixed merely by evolving the
language.  We'll adopt a two-pronged strategy for the future of Javascript:

   - Harmony (low risk/low reward): continue working in conjunction with
   TC39 (the EcmaScript standards body) to evolve Javascript
   - Dash (high risk/high reward): Develop a new language (called Dash) that
   aims to maintain the dynamic nature of Javascript but have a better
   performance profile and be amenable to tooling for large projects. Push for
   Dash to become an open standard and be adopted by other browsers. Developers
   using Dash tooling will be able to use a cross-compiler to target Javascript
   for browsers that do not support Dash natively.

That’s the 10,000 foot overview.  For more detail (including an FAQ), read

Future of Javascript State of affairs Building delightful applications on
the web today is far too difficult.  The cyclone of innovation is
increasingly moving off the web onto iOS and other closed platforms.
Javascript has been a part of the web platform since its infancy, but the
web has begun to outgrown it.   The web development community has been
backed into using large amounts of JS largely to work around the
deficiencies in the platform.   Complex web apps--the kind that Google
specializes in--are struggling against the platform and working with a
language that cannot be tooled and has inherent performance problems. Even
smaller-scale apps written by hobbyist developers have to navigate a
confusing labyrinth of frameworks and incompatible design patterns.

The web has succeeded historically to some extent in spite of the web
platform, based primarily on the strength of its reach.  The emergence of
compelling alternative platforms like iOS has meant that the web platform
must compete on its merits, not just its reach.  Javascript as it exists
today will likely not be a viable solution long-term.  Something must
Overview of two-pronged solution
There are two ways to approach the problem: either we can try to evolve
Javascript, or we can push for a new language that addresses core problems
in Javascript that can’t be repaired easily or quickly.

The “evolve Javascript” option is relatively low risk, but even in the best
case it will take years and will be limited by fundamental problems in the
language (like the existence of a single Number primitive).  Javascript has
historical baggage that cannot be solved without a clean break. Thus,
although it’s low risk, it’s also relatively low reward.

The “clean break” option is extremely high risk--it will be a huge challenge
to convince other browser vendors to rally around a new language--but is the
only way to escape the historic problems with Javascript.  Thus, its high
risk is matched by the potential for a very high reward--a classic leapfrog

Pursuing either strategy in isolation is likely to fail.  The evolve
Javascript strategy, if executed in isolation, leaves the web in a hobbled
state and unable to compete against the encroachment of other, less open
platforms.  The clean break strategy, in isolation, would leave us in an
undesirable situation if it were to fail--Javascript evolution would have
slowed down or evolved in undesirable ways without our support, we would
still have the fundamental flaws, and--worst of all--Google’s leadership
position on the web would be seriously damaged.

The only solution is to execute the two strategies in parallel.  When the
leapfrog attempt succeeds (that is, it is an open standard and browsers
covering a majority of market share implement it), web programmers will have
a viable and superior alternative to JavaScript.
Harmony: Evolving Javascript
It is paramount that Google continue to maintain a leadership position on
important open web standards such as Harmony.  Harmony is the name of the
agreed trajectory of EcmaScript in TC39. Our JS++ project (part of the
larger Parkour project) will join with our Caja project’s efforts to advance
Harmony. Together, we will focus on improving the public Harmony spec and
helping drive it forward at a faster pace in external standard committees
and by leading by example in Chrome wherever possible.

In order to help speed up what can be a long and drawn out standardization
process, the  internal Harmony effort will experiment using a preprocessor
on top of V8 to prototype features in a way that allows real code to be
written against the proposal.  Details of this approach are yet to be
determined.  The effort will also work with other browser vendors (e.g.
Mozilla) to get experimental support included, providing further pressure to
get Harmony standardized and widely implemented quickly.  Harmony will be
implemented in V8 and JSC (Safari) simultaneously to avoid a WebKit
compatibility gap.

Developers who can focus solely on Chrome can expect to be able to see some
Harmony features in Chrome (behind a flag) by the middle of 2011. Developers
focusing on all browsers will have to wait multiple years for direct Harmony
support, due to the relatively slow pace of the standardization process. To
enable Harmony developers to target all earlier browsers, we will enhance
our source-to-source translators (such as Caja’s ES5-to-ES3 translator) to
translate from a large subset of Harmony to earlier versions of JavaScript.

Harmony will continue to be evangelized by Google externally as the
evolution of Javascript.   The audience for Harmony is developers currently
building on the web platform who wish to write standards-compliant
JavaScript.  GWT, JSCompiler, and Caja continue to offer tooling support for
Harmony for those that need it.
Dash: The Clean Break
Dash is the leapfrog effort that is designed to be a clean break from
Javascript.  It will seek to keep the parts that have made the Internet so
successful, but fill in holes everyone agrees it has.

Dash is designed with three perspectives in mind:

   - Performance -- Dash is designed with performance characteristics in
   mind, so that it is possible to create VMs that do not have the performance
   problems that all EcmaScript VMs must have.
   - Developer Usability -- Dash is designed to keep the dynamic,
   easy-to-get-started, no-compile nature of Javascript that has made the web
   platform the clear winner for hobbyist developers.
   - Ability to be Tooled -- Dash is designed to be more easily tooled (e.g.
   with optional types) for large-scale projects that require
   code-comprehension features such as refactoring and finding callsites.
    Dash, however, does not require tooling to be effective--small-scale
   developers may still be satisfied with a text editor.

Dash is also designed to be securable, where that ability does not seriously
conflict with the three main goals.

Dash will be designed to be consumed in a number of locations:

   - Browser VM -- Our aspiration is that Dash will ultimately be a viable
   substitute for Javascript as the native client-side language of choice
   across all browsers.
   - Front-end Server -- Dash will be designed as a language that can be
   used server-side for things up to the size of Google-scale Front Ends.  This
   will allow large scale applications to unify on a single language for client
   and front end code.
   - Dash Cross Compiler -- Dash will be designed so that a large subset of
   it can be compiled to target legacy Javascript platforms so teams that
   commit to using Dash do not have to seriously limit their reach.  Platforms
   that have a Dash VM can operate on the original Dash code without
   translation and take advantage of the increased performance.  One of the
   ways we will evolve Harmony is to be a better target for such compiled Dash

The goal of the Dash effort is ultimately to replace JavaScript as the
lingua franca of web development on the open web platform.  We will
proactively evangelize Dash with web developers and all other browser
vendors and actively push for its standardization and adoption across the
board.   This will be a difficult effort requiring finesse and
determination, but we are committed to doing everything possible to help it

While Dash is catching on with other browsers, we will promote it as the
language for serious web development on the web platform; the compiler
allows such developers to target other browsers before those browsers
implement Dash.

The Dash language effort will be driven by Lars Bak and his team in the
Aarhus office.  Bruce Johnson’s team in Atlanta will handle the tooling, and
Pavel Feldman in STP will provide Web Inspector level support for Dash and

Dash will be spec complete and have working bits for the browser in Q1 2011.
Developers who can focus solely on Chrome can expect to be able to rely on
some Dash features built into Chrome within a year.  Developers focusing on
all browsers will have to make use of the Dash cross compiler to target
other browsers, and, depending on the success of the evangelizing effort,
might have to wait years for other browsers to implement native support for

Although Dash is in the early stages of development, work is progressing
rapidly.  You can learn more about the current proposal in this

FAQ Who authored this document?
Brad Abrams, Erik Arvidsson, Lars Bak, Darin Fisher, Dimitri Glazkov, Dan
Grove, Peter Hallam, Bruce Johnson, Alex Komoroske, John Lenz, Kasper Lund,
Mark Miller , Ivan Posva, Alex Russell, and Joel Webber, who collectively
represent TC39 (the EcmaScript standards body), WebKit, Parkour, Brightly,
JSPrime, JS++, Closure, JSCompiler, V8, Dash, Joy, and GWT, among others.

What happened to JSPrime?
The JSPrime effort was begun to unify and be a (single!) successor to GWT
and Closure/JSCompiler, suitable for large-scale development inside and
outside Google, including being amenable to IDE-like tools and static
compiler optimizations. The JSPrime team is happily folding its efforts into
Dash now that everyone agrees Dash will explicitly include the same goals.

What happened to JS++?
The collection of features under the JS++ umbrella have been folded into
Google efforts around the Harmony Javascript effort.   We continue to seek
to improve the Javascript language to allow developers to better take
advantage of our DOM improvements.  This is a better plan because it gives
us fewer independent Javascript evolution vectors.

What happened to Joy?
The Joy templating and MVC systems are higher-level frameworks that will be
built on top of Dash.

Where can I learn more about Dash?
Dash is still in the early stages of development, but work is progressing
rapidly.  For an early look at the current proposal, see this

How will Dash interoperate with the huge body of existing JavaScript
(JQuery, Analytics, etc)
Moving to a new language will be a very large undertaking.  The specifics of
how inter-operation with current Javascript would work is still an open

What about the existing code bases for large Google Apps?  Won’t they have
to rebuild everything to take advantage of Dash?
The Dash Cross Compiler should be capable of taking typed Closure code (with
some restrictions) and converting to Dash.  Although the migration process
won’t be fully automatic, it should make moving over to a Dash codebase
somewhat easier.

How does this affect Web Inspector?
Web inspector will continue to support Javascript including any new features
of Harmony that we add to chrome.

How does this affect our cloud IDE (Brightly)?
Brightly will enable building any web application in V1 using today’s
Javascript plus the additions in Harmony.  As soon as it is ready, Brightly
will support Dash as well.  We expect that the more prescriptive development
aspects of Brightly that will come on line in the future will be more Dash

We expect Brightly itself to be the first application written in Dash.

How will we get Harmony related changes into Chrome?
Very carefully ;-).  V8 is carefully tuned for speed with the current
Javascript standard rather than flexibility--this makes it very difficult to
make experimental changes.   We are considering pre-processors and a number
of other options, but ultimately the precise solution is still an open

What about Go?
Go is a very promising systems-programming language in the vein of C++.  We
fully hope and expect that Go becomes the standard back-end language at
Google over the next few years.   Dash is focused on client (and eventually
Front-end server development).  The needs there are different (flexibility
vs. stability) and therefore a different programming language is warranted.

Will Dash run on the Server?  Android?
Yes, but short term we are focused on the client.

Does Dash replace Java?
For many projects that will be a viable option but it requires significant
engineering effort on Dash tooling and an extensive set of libraries.

Is Dash statically typed and toolable?
Dash is optionally-typed and with judicious use of types is as toolable as
Java.  This enables “grown up” developer tools such as code-refactoring,
while still allowing small-scale or experimental projects the flexibility
that dynamism provides.

What is the future of the JSCompiler and GWT?
JSCompiler and GWT were already on a merger path.  This effort gives us a
direction for that unification around the Dash language.  We will actively
support teams for a long time on the current generation of JSCompiler and
GWT and provide fantastic co-existence and migration tools to Dash.

Why are you killing Javascript?
We are not!  Google has a huge interest in keeping the evolution of
Javascript on track.  In fact, our investment in TC39 (the Javascript
standards body) will likely increase somewhat, and we will continue to
honestly and whole-heartedly improve the language within the constraints.

What are the time frames?
The Dash VM and Dash Cross Compiler will be developed in parallel with the
language specification, and so should be available not long after the spec
is settled (likely in early 2011).  However, the initial versions will not
be heavily optimized (and thus not necessarily ready for production apps)
until later (likely later 2011).

Experimental Harmony features will begin showing up in Chrome (behind a
flag) by midway through 2011, and will later be implemented simultaneously
in V8 and JSC (Safari’s Javascript engine) to avoid a WebKit compatibility

Why do you have two projects?  Why not just one?
See the section above about why we’re pursuing a two-pronged strategy.

What will Google developers be using?
We will strongly encourage Google developers start off targeting Chrome-only
whenever possible as this gives us the best end user experience.  However,
for some apps this will not make sense, so we are building a compiler for
Dash that targets Javascript (ES3). We intend for existing Google teams
using GWT and JSCompiler to eventually migrate to the Dash compiler.

What if other browsers don’t follow us with Dash?
Lars has promised to “sweet talk” the other browser vendors and, while we
are all eager to see this, we recognize this is a very difficult road.  Our
approach is to make an absolutely fantastic VM/Language and development
environment and build great apps that fully leverage it in order to help
other browsers see the wisdom in following.   Once Dash has had a chance to
prove its stability and feasibility, we are committed to making Dash an open
standard with involvement from the broader web community.

However, in the event that other browsers don’t follow, Dash can still be a
success.  Developers that target only Chrome can rely on the Dash VM, and
developers that target other browsers as well can still make use of the Dash
compiler.  In this event, the wider web will be stuck with Javascript as the
standard language--and that’s precisely why we must continue investing in
evolving Javascript.

Why are you circumventing the standards process?
We fully intend to cooperate fully with standards processes--the problem is
that the current standard processes are limited to Javascript, which is not
viable in the long term.  Any effort with the historic baggage that
Javascript has will be extremely limited.  We need to make a clean break,
make progress, and then engage the community.

What will we say at Google IO about Dash/Harmony?
Google deeply cares about the web.  We care about making the web
incrementally better today (Harmony) as well as making it substantially
better in the future (Dash).  Large scale applications should probably build
on Dash; smaller-scale developers might want to stick with Harmony until the
Dash standard gains ubiquity.  Given that Dash is such a big bet we are
likely to spend much more time at IO on Dash, though of course we will spend
some time on the leadership position Google is taking in Harmony.


4G Long Term Evolution of Sprint in 2012

Sprint Nextel announses its 4G Long Term Evolution (LTE) on early 2012 . Eventhough they are not aware of how the market will accept, Sprint is now testings its 4Gin selected area. As Sprint has planned its 4G long back , they said there wont be much investment on this product.But with this they are pretty sure that the quality of this will be much better than any other product so far in the market. 
Sprint's 4G LTE network would give the carrier a network on par with Verizon. Sprint will officially announse more details and launch of its 4G in October . Even they are expected to getting ready for its iPhone , which was the monopoly of AT&T and latter by Verizon. With the acqusition of Nextel , who owns the D-block spectrum , will be used for this. . The whole project, which is expected to cost $4 billion to $5 billion

What is LTE?
Long Term Evolution (LTE) is a standard for wireless communication of high-speed data and is based upon GSM/EDGE and UMTS/HSPA network technologies . LTE is the brand name for emerging and developed technologies that comprise the existing 3G and 4G networksThe goal of LTE is to increase the capacity and speed of wireless data networks utilizing cutting-edge hardware and Digital signal processing techniques .

Features of LTE include an all-IP flat network architecture, end-to-end QoS including provisions for low-latency communications, peak download rates nearing 300 mbps and upload rates of 75 mbps, capacity exceeding 200 active users per cell, the ability to manage fast-moving mobiles, and support for multi-cast and broadcast streams.Peak download rates of 299.6 Mbit/s for 4x4 antennas, and 150.8 Mbit/s for 2x2 antennas (using 20 MHz of spectrum).Peak upload rates of 75.4 Mbit/s for every 20 MHz of spectrum using a single antenna.

The LTE standard can be used with many different frequency bands. There are planned 700 and 1700 MHz in North America; 900, 1800, 2600 MHz in Europe; 1800 and 2600 MHz in Asia; and 1800 MHz in Australia.The combination of LTE’s increased spectral efficiency and flexibility, added capacity, and simpler network architecture should offer a very cost effective value proposition.

Friday, September 23, 2011

Dart programming language from Google

After the release of GO Lang from Google on 2009, we didnt hear any thing from our search giant.May be the last one that I head is appengine supports the Go lang , mean while the cost of appengine increased like anything. Every one was busy with Android and the Motorola's acquisition by Google.  So what is DART ? No idea. They are not ready to reveal any thing till October . On October they may release the brief on GOTO developers conference . May be that conference may be for this new programming languages release. But we may expect this may change the web programming or no one cares.
Thinking +ve , the key people involved are Lars Bak , who worked for Sun many years , who owns dozens of patents and Gilad Bracha , a veteran of SAP Labs . The only thing that we can think is the new language, is purely for web and will need Chrome / Android . Bracha blogs mentioned that “However, Javascript remains a seriously limited language for platform implementation. Here are some of the problems.Concurrency primitives. There aren’t any.”  So are they targeting Oracle’s Java? One thing by reading Bracha’s blog , I felt that , this Dart is a language that has the capability of communicating to the machine directly like C and in the same time it can play around with Web.

Thursday, September 22, 2011

India’s $2500 worth car become million Dollar car

Tata Motors’s Tata Nano, legendary $2,500 car  , came in a new style with covered GOLD.Titan Industries-owned Goldplus has made an unaffordable car designed to appeal to the masses with its conspicuous use of gold and jewelry.Nano with 80 kilograms of gold (22 karat, of course), 15 kilograms of silver, and precious and semi precious stones including rubies, pearls, emeralds, and the black beads worn by Hindu brides in a necklace. The price that is 2200 times the price of the original car.
Tata's Gold Plus stores are celebrating 5000 years of jewelry making in India and to celebrate this 5000 years of Jewellery making in India, Tata decided to cover the Nano with Gold, Silver and jewels.
The Gold Plated Tata Nano is studded with 176 pounds of 22 karat gold, 33 pound of silver and more than 10,000 precious gems and stones. The resulting cost for this Tata Nano would be somewhere around $4.6 million.

Mango update to Windows Phone 7-Features

Microsoft will push its Mango upgrade to its Phone 7 platform within the next couple of weeks.There will be no set date for release, since individual malware vendors will be tweaking the software for their own handsets when they are ready.Every Windows Phone will also receive software from the handset manufacturer.Mango brings a huge number of improvements to the system, and significantly expands the number of locations and languages. This will have a bigger market share by 2015 than Apple or Google.Mango 7.5 is out in the open.
Some of the features of Mango
  • Hands free — When you're driving, Mango can announce an incoming call or text message and will allow you to respond to either without ever picking up your handset. Safe driving FTW!
  • Threads — Switch between your active texts, Facebook chats, or instant messages in one threaded space, so you can keep the conversation going no matter where it takes place.
  • Local Scout — Bing will aggregate activities and events that are going on around your current location and allow you to rate each activity.
  • App Shortcuts — Kind of like multitasking, App Shortcuts are a handy feature in Mango. For example, if you're reading about a movie while surfing the web, Mango will create a quick shortcut to your IMDB app, so you can check out the film's details.
  • Fast app resume — This feature keeps things moving as it quickly reboots apps that have been recently used.
  • Turn-by-turn navigation — Bing Maps supports voice-guided, turn-by-turn directions, so you don't have to take your hands or eyes off the wheel when you're in a new 'hood.
  • Kinect support — For the ├╝bergamer: you can interact with Xbox Kinect games with your Mango phone.
  • Bing Vision — Scan QR, Microsoft Tags, books, CDs and DVDs for quick info and pricing.
  • SMS dictation — Microsoft Tellme technology helps you text on the go by enabling you to speak your texts instead of typing them on your virtual keyboard.