Google Chrome OS Open Source Project Announcement
Google Chrome OS Open Source Project Announcement
Google Chrome OS is an open source operating system for people who spend most of their time on the web built around the core tenets of speed, simplicity and security. http://www.chromium.org
Content
0 -> >> PICHAI: So, Welcome everyone, good morning.
Thanks for being here. Today is an exciting
6.6 -> day for us. So I really appreciate all of
you coming down here. I heard traffic was
11.19 -> bad on 101, so thanks for putting up with
it. We are here today to talk about Google
15.65 -> Chrome OS. Contrary to some of the reports
out there in blogs et cetera, we aren't launching
21.23 -> the product today. There's no beta today.
There are no devices today. We are a year
26.38 -> away from announcement. Having said that,
we meet tons of progress so we want to take
30.829 -> the opportunity today to walk you through
the progress, so, give you an actual demo
34.8 -> of what we have built so far. We'll be giving
you a technical overview as well explaining
39.67 -> how we are going to go to market, as well
as answer questions. But the primary reason
44.879 -> we are here today is because we are very excited
to announce the open sourcing of the project.
50.19 -> As of today, the code will be fully open,
which means, Google developers will be working
56.059 -> on the same tree as external developers. So
whatever we do will be in the open. And we
61.93 -> are really looking forward to working with
the open source community to help drive this
65.43 -> forward. So with that, let's get started.
So I'm here to talk about Chrome OS but I
70.06 -> want to start with Chrome permanent. The reason
is Google Chrome is the foundation of everything
74.79 -> we are doing here. So we launch Chrome about
14 months ago in a similar audience, the comic
82.06 -> book leaked and, you know, we were launching
Chrome. So why did we do Chrome? The goal
88.52 -> was we had noticed that the Web had a wall
from simple text pages to really rich applications.
95.5 -> So applications like Gmail, Google Maps, Yahoo
mail, et cetera, et cetera. And we really
101.77 -> wanted a modern browser which was capable
of handling those rich applications. So that's
105.83 -> why did Chrome. We really wanted to help push
the Web forward. So let's a look at where
109.98 -> we are now. So it's been a year since launch,
just over a year. We recently announced we
114.98 -> were over 30 million users. Now, we are happy
to announce we are over 40 million users.
119.44 -> So the growth is very, very strong. And by
users, we are referring to primary users of
125.9 -> the browser. They use Chrome as their main
browser. If you count all users of Chrome
129.2 -> the numbers are much higher. The three main
things we focused on Chrome was speed, simplicity
135.611 -> and security, mostly speed though. We really
care about speed. And Chrome is about close
142.23 -> to 40% faster in JavaScript performance than
the current version IE which is IE8. So it
149.22 -> is something which sounds abstract to most
people, it's a benchmark but there it starts
153.78 -> manifesting itself as you start using the
next generation of Web applications. For example,
158.531 -> take Google Wave. With Google Wave, you don't
need a benchmark to say Chrome is faster.
162.88 -> All you need to do is to try Google Wave in
Chrome and an IE and most users will just
166 -> notice the difference in a matter of seconds;
one is fast and the other is slow. So we really
171.63 -> focused on speed but JavaScript performance
is just one aspect of speed. We have focused
176.569 -> on end-to-end speed of the browser from the
time you click the icon to how you load Web
180.46 -> pages to how you interact with the browser.
And most users, who use Chrome, write back
185.03 -> to us and the most common feedback they get
is Chrome is fast. So we really--we really
189.55 -> focus on that. The next point is, over the
last year, we have updated Chrome about 20
195.209 -> times including several major versions. Most
users don't notice. We really care about making
201.72 -> sure software works seamlessly and users shouldn't
have to worry about maintaining software.
207.53 -> The final point about Chrome, an area which
I'm going to talk about in more detail is
211.209 -> we really focused on making HTML5. HTML5 is
the underlying code which powers all Web applications.
217.5 -> We really want to help push the Web forward.
And we have done a lot of work there and I'll
222.4 -> share the progress there as well. Next slide.
So, just this year alone in Chrome, there
228.2 -> is tons of new stuff coming. So before this
year gets over, we'll have three more announcements
233.63 -> to make. Chrome for Mac will be ready for
users to use. I use it as my primary browser
239.17 -> now and it's coming along very, very well.
So we are very close to launch there and it's
243.51 -> something we have--looking at the number of
Macs in the room, I'm very excited by it.
247.349 -> Chrome for Linux is also coming along very
well. It's the foundation of what we are doing
251.249 -> in Chrome OS, so that's very exciting as well.
Finally, we are nearing the launch of the
256.37 -> Extensions. We have taken the time to rethink
how Extension should work. We want the extensions
261.71 -> to be much easier to write. So Chrome Extensions
are based on the same Web technology in which
266.229 -> write Web applications, HTML and JavaScript.
They are very easy to write and as a user,
272.21 -> they are light weight, they don't slow down
your browser, it's easy to use. And most importantly,
276.93 -> we will keep all extensions automatically
updated for users. So once you install them,
279.93 -> you'll never have to worry about maintaining
them. We are doing a lot more of interesting
284.96 -> stuff with extensions working with several
partners and so we have a lot, you know, we'll
289.08 -> be announcing a lot more details later this
year. Next slide. I'll talk a minute about
294.539 -> HTML5 and making the Web more powerful. So
let me explain, this is a very important part
300.419 -> of what we are doing because it has a lot
of implications for Chrome OS. So again, our
306.659 -> goal here is to make sure Web application
function as well as desktop application. Today
311.711 -> desktop, conventional desktop applications
have a lot of access to underlying operating
316.569 -> system capabilities and full system resources.
Web apps in many cases don't have access to
322.669 -> those resources. So we are working hard identifying
every possible gap and we are figuring out
329.309 -> a safe way for Web applications to take advantage
of the same ongoing operating system capability
334.46 -> and system resources. Let me give you some
examples. Graphics. So, we are all used to
340.479 -> running rich games on our personal computers.
We want it to be possible to have the same
346.55 -> games and other rich 3D applications within
a browser. Effectively, we want Web applications
352.33 -> to get access to the GPU which is present
on most computers today. So that's one example.
357.789 -> Let me give one more example, what we call
as threads or workers. Most computers today
363.449 -> should have multi-core CPUs. How do we make
sure Web applications can run parallel threads
369.319 -> and take advantage of the multi-core CPUs
in your machine. One more example, Real-Time
374.099 -> Communication. We want it to be possible for
any Web page to have full high-quality voice
380.9 -> and video chat built in as an example which
means Web applications need a way to communicate
387.539 -> to your speaker, microphone, camera. One more
example, you need Web applications to work
393.81 -> offline. So we are exposing a data base API,
effectively exposing local storage on the
399.949 -> machine to the Web application. So in each
of these cases, our goal is to make sure we
406.219 -> take Web applications, give them the capabilities
they need so that they can be very rich, complex
411.43 -> applications with the full functionality of
desktop applications. So we are making a lot
416.021 -> of progress in this area, it's a huge area
to push for us and in 2010, we expect to have
421.619 -> all these APIs and much more fully built in
to Chrome, as well as we are working with
425.849 -> the other major browser vendors to make sure
they evolved as part of HTML5 standards. Thanks
430.18 -> a lot. So, while we've be focusing on building
Chrome, making sure Chrome is better and making
438.86 -> sure the Web gets better, there have been
some very powerful trends happening in the
444.189 -> industry at the same time. There are three
trends especially which we are very excited
448.219 -> about. So I want call your attention to that.
On the top left, what you are seeing is the
452.999 -> growth netbooks. The growth is phenomenal.
To put it in perspective, this growth happened
459.789 -> in the worst economy since the Great Depression.
You know, it's unheard of growth for the kind
464.52 -> of time in which it happened. So netbooks
are exploding. So what are netbooks? Users
469.259 -> are responding to these because they view
this as ultra thin, ultra light, ultra mobile
474.379 -> computers. In many cases, they are buying
it as companion PCs to spend most of the time
480.05 -> online, right? So, we are very excited by
this development. On the right-hand side,
485.339 -> top right, the point there is hundreds of
millions of users are living on the Cloud.
490.199 -> This is a trend which has been going on for
a while. We notice it internally. I pretty
495.099 -> much, by now I'm a hundred percent. Everything
of what I do is in a browser for me. And that
500.56 -> is true for a lot of people outside. Most
applications, in fact, if you take the last
506.979 -> five years and think about all the interesting
applications that have been written for your
511.33 -> personal computer, I'm sure you can count
with less than one hand the number of conventional
516.8 -> desktop application that have been written.
Everything else has been a Web application.
520.86 -> So the trend is very, very clear. Every capability
you want today, in the future, it's going
526.6 -> to be written as a Web application. It's the
most successful platform out there. So we
530.55 -> are very excited by that trend as well and
we are working very hard to accelerate that.
535.079 -> The third trend on the bottom, there is tremendous
innovation at a computing device level. On
540.569 -> the one hand you have phones. All of you are
familiar with this; phones are becoming smarter.
545.73 -> So, people call these smart phones. There
are rumors of Tablets, but effectively these
551.41 -> are phones getting on computing capabilities.
They expose a rich application framework and,
557.42 -> you know, people are building apps for them.
So, they are effectively becoming computers.
561.49 -> On the other side, laptops and then netbooks,
they are becoming more like phones. There
567.029 -> are netbooks which are selling today which
have--always on connectivity. The battery
571.35 -> times are getting better. I think in the future,
you will see netbooks that you can carry around
575.089 -> with you all day and charge them in the night
just like your phone, right? And so they're
579.12 -> becoming mobile, lighter, et cetera. So, this
convergence is very powerful and we think
584.6 -> really lends itself to a new model of computing.
So, looking at all these trends, the question
590.09 -> we ask ourselves is, is there a better model
of personal computing that we can give to
595.94 -> our users and we believe so and that's what
Chrome OS is. So, with Google Chrome OS, I'm
602.17 -> going to switch now and talk about Google
Chrome OS. With Google Chrome OS, we again
606.62 -> focus on three things. It will be familiar
to you by now since Chrome is the foundation
610.529 -> of what we are doing here. It's speed, simplicity
and security. When I say speed, we want Google
617.829 -> Chrome OS to be blazingly fast. So from the
time you press boot, we want it to be like
623.37 -> a TV, you just turn it on, you should be in
the Web using your application. So we wanted
628.759 -> to be very fast. In addition to just making
the boot time fast, we want the end-to-end
633.79 -> experience to be fast. Chrome itself is very
fast, but Chrome on Chrome OS, because we
638.959 -> understand the underlying operating system
as well as we are specifying competence in
644.029 -> the hardware so that we can profile Chrome
and make it much faster. So Chrome on Chrome
648.7 -> OS will be even faster than Chrome. Simplicity,
this is one of the most important things we
656.02 -> are doing with Chrome OS. In Chrome OS every
application is a Web application. So, let
662.56 -> me repeat it again, every application is a
Web application. There are no conventional
667.06 -> desktop applications. So users don't have
to install programs, they don't have to install
671.26 -> software, manage updates, nothing. It's a
Web app, it's a link, it's a URL. So with
678.399 -> that arises simplicity. You know, most people
when you expose them to a new operating system,
683.839 -> they struggle with lack of familiarity. In
the case of Chrome OS it would be very familiar
689.389 -> to them, it's just a browser. So, it's a browser
with a few modifications which I'll show visually
693.17 -> in a few minutes. So it's very simple to use,
nothing to maintain and the computer should
697.98 -> just work. In addition to that, all data in
Chrome OS is in the Cloud. So as a user, you
705.319 -> really want it to be easy for you to use the
machine. Today, I can take any of your machines
709.62 -> and use Gmail or Yahoo mail. I can login to
my mail. Similarly, you can take any of my
714.61 -> machines and login to your email account.
We want all of personal computing to work
718.759 -> that way. If I lose my Chrome OS machine,
I should be able to go buy a new machine,
723.029 -> login within a matter of seconds. Get my favorite
applications, the necessary cash data back
728.939 -> including personalization, my background,
everything should look similar. We wanted
733.209 -> to be possible for users to share machines
and feel as if the machine belongs to them.
738.339 -> So, we are working really hard to achieve
that objective. The final point is security.
745.22 -> Given what I talked about that everything
is a Web application, we can fundamentally
749.37 -> do different things with security than what's
being done till now. And the reason, security
754.61 -> is a very hard problem, right? You'll never
going to make a system completely secure,
758.73 -> but we can do a whole lot better. Because
in Chrome OS, users don't install binaries
764.819 -> on the system, we understand all the code
on the system; we can detect malicious processes
770.36 -> much better. We can manage the system. If
there is an issue, we can fix ourselves with
775.05 -> the reboot. Matt Papakipos our engineering
director on Chrome OS we will actually talk
778.5 -> about some of the most innovative things we
are doing on the security front. We run completely
783.93 -> inside the browser security model which is
very different from how traditional operating
788.399 -> systems work today. So, speed, simplicity
and security are the three main areas we have
792.55 -> focused on and I want to actually take the
time to switch over and show a demo. We want
798.63 -> to first start by booting the machine. So
Khan is actually, Khan Lee who is the product
803.42 -> manager on Chrome OS is actually going to
press the button and do a called reboot, let's
808.25 -> go. So, we really care about how fast we can
get the machine to boot. We want this to be
814.519 -> in a matter of seconds. And as you can see,
we are in the login screen, right? It takes
819.17 -> about seven seconds right now and we are working
very, very, very hard to make this time shorter.
824.97 -> It takes another three seconds to login to
your favorite application. So, we are going
829.43 -> to switch to the machine from which we are
being projecting. In case you didn't realize,
832.629 -> we have been projecting from a Chrome OS machine.
So we are going to get out of the full screen
836.29 -> mode and we are within Chrome OS. So, two
things before I get started with the demo;
843.22 -> first of all, hopefully this is not a surprise
to you but it looks like Chrome, right, so,
848.769 -> you know, internally we joke around it saying
Chrome is Chrome OS, right, and Chrome OS
855.449 -> to OS for all practical purposes. Having said
that, there are many, many interesting changes
859.749 -> in Chrome which I'm going to walk you through
to make it function like an operating system.
863.37 -> The advantage of doing it this way is it's
very familiar and intuitive to most users.
869.22 -> Almost everyone knows how to use a browser.
So we just want it to feel that way. The second
874.579 -> thing I want to say before I walk through
the UI is at this stage of the project, we
878.399 -> are opening up the project to a year ahead
of release. So we are actually, a trading
883.92 -> through the UI. I have to convince the team
to stop checking in code so that we can cut
888.68 -> our bill to freeze it for the demo, right?
We are checking in code as we speak. So a
893.66 -> lot of UI is going to change. I'm not fully
sure how it will turn out. But one thing I
898.68 -> can guarantee is it won't be exactly like
what you are looking at today. Having said
902.35 -> that, there are many, many important concepts
here which we are very sure we'll carry over
906.52 -> to the final product. So, I'm going to focus
on covering those aspects for you first. So
912.7 -> to start with, it looks like Chrome, but on
the top left hand side, you're seeing some
918.93 -> small tabs, we call this application tabs.
So you can take any of your favorite applications.
925.259 -> In my case, it's Gmail and calendar, etc.
But it could Facebook, it could be Yahoo mail,
932.059 -> whatever users want. You can take any application
and with one click pin it to be a favorite
938.009 -> application. And once you do that, we call
this application tabs. We are working very
941.959 -> hard to make it possible for you to get to
your favorite applications instantly. So once
946.559 -> you choose something as an application tab,
they always stay in place. So let's open a
951.519 -> few tabs, as you can see, Khan is opening
a few tabs but the application tabs, on the
957.93 -> top left, the five of them don't move at all.
So you can open, close, et cetera. They always
962.72 -> stay in place. So we are working very hard
to make it easy for you to access your favorite
968.149 -> applications. In addition, to this method
of accessing our applications, there's, on
972.87 -> the top left hand side, you have something
what we call as to app Menu. So, caveat, the
978.899 -> UI here is going to change, but the concept
is we really want you to be able to discover
983.379 -> new applications as well as just access your
top application. So, let's go around and start
990.439 -> poking around the app menu. I'm noticing an
interesting app called "Contacts." So let's
995.519 -> try that up. Something interesting happened.
Something popped from below. Internally, we
1001.22 -> call these as moles because they kind of come
from underground but we're going to call them
1006.48 -> panels, externally. So panels are something
which these are persistent, light-weight windows
1012.54 -> which you can have them around with you all
the time. They are persistent. So, for example,
1016.089 -> let's click on a few tabs, they don't move
at all. Right? And the panel stays. It's a
1022.55 -> persistent window. There are several interesting
used cases for it. You can minimize them and
1028.09 -> make them go away and you can bring them back.
We're going to work hard to make sure we can
1032.339 -> automatically manage panels for users. So
this is a chat window. So Khan is chatting
1035.94 -> with David, one of the engineers on the team,
and hopefully, David says "Hi" back. There
1042.37 -> you go. So, buddy list and chat is a great
example of how you would use a panel. Let'
1049.1 -> see what are used cases for panels are there.
So, let's poke around, there's a notepad.
1053.04 -> So, let's click on notepad as an example.
So, one more panel, the interesting thing
1057.69 -> about the Chrome OS is I mentioned all data
is in the Cloud, so what does that mean? So
1062.07 -> Khan is going to type something here, and
maybe we should go to Google Docs and open
1068.54 -> this notepad file. You can see it's right
there in the Cloud. All data and Chrome OS
1074.341 -> is in the cloud. So as a model, anything you
put out on the machine, it's instantly available
1079.14 -> to you from anywhere. So, which is something
we are very, very excited about. Let me show
1083.84 -> one more used case for panels. Let's type
U2 in the Chrome Omnibox. Recently, we launched
1090.71 -> this very cool music feature, called "Music
One" box by which you can type the names of
1095.18 -> songs and play it right off the Google Search
page. So, let's click on Beautiful Day. You
1100.36 -> can see a panel popped up and it plays right
in place. It's a persistent window. You can
1105.96 -> leave it there. You can minimize it and keep
working. All right, you can use this to stream
1109.94 -> music from the Web. So, these are interesting
examples of how we expect people to use panels.
1114.78 -> Before we get caught up in the song, let's
scrap it out. If you, if you go to the--well,
1123.16 -> let's go poke around app menu once more. So
what I like about netbooks is today I used
1131.93 -> to travel and I go on vacation and stuff to
carry my DVD player, my computer, my book
1136.37 -> reader, et cetera. The great thing about netbooks
is these are ultralite, thin mobile devices.
1142.72 -> And once battery times get much better, you
can carry them around with you as general
1147.6 -> purpose devices. So we actually expect this
to be great entertainment devices. People
1151.52 -> should be able to watch videos, play music,
play games, books, etc. So let's see how the
1156.4 -> experience looks like. So, I'm an avid chess
player, so I have this chess game which I
1161.06 -> use on my Chrome OS machine and you can now,
it's just a flash. Can you work it? Okay,
1171.27 -> great. So, Kahn is playing the chess game.
You can see how it's very easy and visual
1177.75 -> and you can enter--you can make it full screen
more and take over the screen. So these are
1181.55 -> good examples of what we expect people to
do with these machines. In fact, another good
1187.94 -> example of what you can do is read books.
So, for example, we are working hard on this
1191.62 -> experience and we have days to go. But if
we look at Google Books, for example, here
1196.16 -> is, Alice in Wonderland. So, you can have
it on your netbook, in a full screen mode
1203.36 -> and you can read conveniently. It's, you know,
these are scanned books which are available.
1207.9 -> And I can totally imagine reading it to my
daughter, you know, carrying a Netbook around
1212.43 -> with me. So, it's very, very compelling. So,
we are really interested in solving all these
1216.47 -> interesting user experiences for people. One
of the things is I've spent all my time in
1221.43 -> one Chrome window. But it's very common for
users to have multiple sets of windows. So
1227.88 -> we want to walk you through that experience.
For example, it's the time of the year which
1231.23 -> I'm planning to get all my gift shopping done
before holidays come around, right. So I have
1235.1 -> a set of windows with Amazon, EBay, et cetera
so I can easily switch over to the other windows.
1241.26 -> And so I have Amazon and EBay, it's a completely
different Chrome instance for me. And, I even
1246.75 -> have YouTube, I want to take the chance to
show that YouTube works and Flash works on
1251.16 -> a machine, so let's click on a video and make
sure it works. So as you can see, YouTube
1258.55 -> works and Flash works. I just moved to another
window. Let's go back to the original window.
1263.54 -> You can move back and forth. In fact, you
can go to the "All View" mode and you can
1268.4 -> see all the windows which are open on your
system. The UI here is going to change a little
1272.86 -> bit. But you can imagine, I can open a new
Chrome window, right? And I can drag and drop
1278.15 -> a tab from one Chrome window to another Chrome
window. It's very simple, very intuitive,
1285.58 -> and just works. So this is the core part of
the user experience. Having said that, one
1293.36 -> of the things we realize is people are going
to buy these netbooks. They're going to go
1296.93 -> home and do a lot of common things they are
used to doing with computers. So we actually
1302.28 -> have a long list of all these used cases,
and we are working hard to make sure it works
1306.57 -> seamlessly for users. Let me walk through
a couple of examples, most people plug-in
1311.13 -> their cameras, right? They may plug-in a USB
drive. And so, what happens if we plug-in
1317.91 -> a USB drive? You can imagine the set of concepts,
but you can imagine Chrome opens a tab and
1324.95 -> shows you what's in the content of a camera
or a USB drive. And you can see the files
1332.24 -> that are on the machine. It turns out in this
USB drive, there are Excel files. We don't
1333.74 -> have Microsoft Excel on this machine. So what
happens if you click Excel file? Let's give
1335.77 -> it a shot. It turns out, Microsoft Office
launched the killer app for Chrome OS. They've
1343.5 -> been working very, very hard to do this. The
point here is, Chrome OS does not have a proprietary
1350.64 -> app framework. It's a completely open app
framework. It's the Web. So anybody who puts
1355.89 -> up a URL, anybody who writes an application
that works on the Web and in a browser is
1361.11 -> writing an application for Chrome OS. It's
something we are very, very excited about.
1365.83 -> And, for the record, I'm an avid Google spread
sheet user, just a disclaimer. So there are
1371.13 -> a few other used cases people can do. Here
are some interesting used case we can demonstrate.
1376.69 -> So, Khan is going to take a picture. In fact,
he has he has one of the new droids and it
1382.47 -> has a 5 mega pixel camera so it's pretty cool.
So, hopefully, we're going to get a good picture
1386.8 -> out of it. And he's going to take a picture
and let's see what happens if you plug this
1392.04 -> in the Chrome OS machine. So, you can see
Chrome OS detects that the camera is a storage
1407.99 -> device. Now, the phone is a storage device.
It can pull the picture right there. So he's
1412.49 -> clicking on the picture and here you go. I
can see Arrington squarely in the center of
1417.81 -> the picture. So it turns out there is a video
on the phone as well. So let's try and see
1423.03 -> what happens if you click the video. The video
plays right and plays in the panel we talked
1430.44 -> about. So the point here is we really want
it to be possible for all these seamless used
1437.03 -> cases, I mean, for all these used cases for
users to be seamless. We just want computers
1441.5 -> to be delightful and works, so we are working
very hard to make it possible. One final example,
1446.76 -> I guess, I want to give is, people are run
in to many, many different types of files,
1451.4 -> right, when they use a computer. They need
to be able to use those files. For example,
1455.911 -> let's go to one of my favorite Websites, I
go there pretty often. It's IRS.gov and let's
1458.97 -> poke around and click on a PDF file. All right.
So what happens if you click on the PDF file?
1466.07 -> It works. It's instant. It's in the browser.
All right. So, that's the underlying theme
1468.66 -> of what we are trying to accomplish; speed,
simplicity, and security. So, I'm going to
1474.27 -> take a step back from the demo. I'm going
to turn it over to Matt Papakipos who is the
1478.35 -> engineer director on Chrome OS. And he is
going to take a few minutes to walk under
1484.34 -> the hood. But I would really encourage you
to pay attention because what we are doing
1488.06 -> is a fundamentally different computing model
than what appears on the surface.
1495.679 -> >> PAPAKIPOS: Hi. So, my name is Matt Papakipos.
I run the Chrome OS engineering team. So I'm
1500.45 -> excited to tell you about some of the technology
under the hood here. So the first thing to
1504.62 -> say is, we're doing a big open source release
today. So as Sundar mentioned, all the code
1508.76 -> is out in the open now. You can go and check
it out and build it. In addition, we've done
1513.4 -> a pretty unusual, interesting thing here and
that we've also opened up all of our design
1516.8 -> documents. So, you know, what's the thought
process behind this. Where are we going with
1522.26 -> it? What are the things we're doing next?
So we're showing you not only what we've built
1524.97 -> so far and what the theory was behind it,
but the things we're building next and involving
1528.88 -> the community in that whole process. So what
I'll show you today is a sketch of some of
1533.01 -> those design documents so you can see some
of the technology we've already built and
1536.92 -> some of the stuff we're still working on and
encourage people to read the docs and get
1541.54 -> involved. But I'll give you a quick sketch
right now. So as Sundar mentioned, speed is
1545.97 -> a big focus for us here. So we want to make
it a very fast, delightful system to use.
1551.11 -> So, what we're going for here is that it feels
much more like a television than a computer.
1554.98 -> We want you to be able to just punch the on
button, and it immediately comes on, you log
1559.48 -> in, you're on the Web as quickly as possible.
So, let me talk about how that works. So one
1564.891 -> of the first points is, all the Chrome OS
hardware devices are based on solid state
1568.98 -> storage. So what this means is no hard disks.
So disks would be moving parts with RN particles
1574.28 -> on them. So, it's all entirely flash memory
based storage solutions. And that's part of
1579.4 -> why we can boot so quickly is, 'cause we're
actually just reading out of RAM rather than
1584.78 -> reading out of a spinning magnetic drive.
That makes a huge difference. So let me walk
1589.17 -> through how a conventional operating system
boots. So I've pictured it here. I won't show
1592.51 -> you all the details but there's a firmware
process, there's boot loader, the kernel starts
1596.28 -> up, system services starts, start up applications,
browser, the user actually has to click to
1601.29 -> start the browser, typically, you know. No
wonder it takes a long time. So to give you
1606 -> a flavor of some of the things that slow it
down, when you punch the power button, your
1610.16 -> computer still, to this day, spends time going
out and probing and looking for a floppy drive.
1614.9 -> Does anyone actually have a floppy drive in
their computer? You know, but your firmware
1618.58 -> doesn't know that, your operating system doesn't
know that. So, they're out there looking for
1621.02 -> it. And that's part--symptomatic of one of
the reasons that OSs are so slow. So we've
1626.5 -> really gone in Chrome OS and cut out all the
boot steps that we possibly can. So we've
1631.2 -> eliminated the--working to eliminate the boot
loader to merge it in to the firmware portion,
1636.07 -> doing a lot of work to optimize the kernel,
not start up system services we don't need.
1640.53 -> As Sundar mentioned, we don't run conventional
applications so we don't need to start up
1646.52 -> background services for them, et cetera, so
we can run a lot faster. And in addition,
1650.61 -> we auto start the browser. So as soon as you
log in, we start Chrome, we bring up all your
1654.451 -> application tabs and your tabs from last sessions
so you're off and running. Another thing we've
1661.86 -> done in the boot front that's pretty interesting,
I think, is we're working on a system that
1665.14 -> we described in the designed doc called verified
boot. And the basic concept here is, you know,
1670.56 -> exploits happen in the real world, right?
There are malware breakouts in any operating
1674.85 -> system that exist. So the challenge is once
when it happens, how do we figure out that
1679.19 -> it's happened, how do we correct the situation?
So, as Sundar mentioned, Chrome OS auto updates
1685.06 -> itself. So we go out and make sure everyday
that you're running the correct version of
1688.4 -> the operating system, that you have all the
security patches that we can possibly apply
1692.71 -> to you. So the essence of the verified boot
process is to make sure that every time you
1698.97 -> boot, we double check that you're running
what you should be running. So the basic concept
1703.49 -> is, that every component of software in Chrome
OS from the firmware to the kernel, to the
1709.99 -> Chrome itself, to the whole root file system
have a, what's called, a cryptographic signature
1715.95 -> attached to them. And the basic notion is,
as if each one where a document that's signed
1720.31 -> at the bottom, you know, with the John Hancock
saying, "Yes, this is the right set of bits."
1724.96 -> So, we're using this cryptographic signature
keys to make sure that when we load the kernel
1730.62 -> off disk, we check the signature, we make
sure that it is the set of bytes that it's
1734.9 -> supposed to be, and then we transition control
to it. So what happens if it goes wrong? So
1740.09 -> we start to boot the system, we go through
the firmware, we go through the kernel, we
1745.41 -> start Chrome and we discovered that one of
the bytes is wrong. Right? It fails the cryptographic
1749.44 -> signature check. So if this happens, there
could be multiple reasons. It could malware
1754.502 -> outbreak or some kind, Chrome got hacked.
It could be just a random cosmic ray, right,
1760.481 -> sometimes a bit flips in the memory or a hard
disk, you get a random error. When that happens,
1765.58 -> we detect that it's happened. So, in this
case, the kernel would detect that Chrome--it's
1769.5 -> the wrong version of Chrome, something is
wrong. We do the malware detection, and then
1774.47 -> we go through, what we call this recovery
procedure where the system repairs itself.
1777.9 -> And so, from that point, it offers the user
a reboot, the user reboots. We re-download
1782.99 -> the appropriate version of Chrome, reinstall
it in the hard disk and start it up. So we
1788.37 -> repair the system automatically. And basically
what this is doing re-imaging your computer.
1794.78 -> The trick here is we've taken what used to
be a very painful re-imaging process, right.
1799.28 -> We've all re-imaged the Mac or a Windows machine.
It's incredibly painful when you lose all
1802.79 -> your date. What we've done here is made it
transparent, and we do it in a way where it
1807.48 -> also saves all your cache data, saves all
your system setting so you don't lose anything
1810.55 -> in the process. And I'll talk in a bit about
how that saving state works. Okay. So, I was
1820.44 -> talking a bit about security there. Let me
talk a little bit more about security. So,
1823.19 -> here, I'll talk about, application security.
So, how do we make sure that those applications
1827.5 -> don't harm your machine 'cause this is a primary
attack vector for malware as everyone knows.
1834.34 -> So the security model of conventional operating
system is something which was developed over
1838.35 -> 20 years ago, right? The basic application
security model for a conventional OS is that
1843.41 -> the application is run with your privileges,
right. It says, if the application were you,
1848.28 -> right? So, if you're allowed to modify a file
on the disk, the applications you run on your
1851.91 -> behalf are also allowed to modify those files
on disk. And this creates a bunch of security
1856.62 -> challenges 'cause it means that, a rogue application
or a hacked application could do great damage
1861.39 -> to your system or to your personal data or
even leak your personal data to other parties.
1865.49 -> So it's a big deal. It also leads users to
have to make some very hard decisions on a
1871.42 -> conventional operating system. When you install
an application, you're taking great risks.
1875.32 -> You have to make decisions about do I trust
this application, where did I get it, is it
1879.17 -> safe? And these are decisions that are hard
for users to make good decision about. In
1884.34 -> Chrome OS, we've taken a very different approach.
As Sundar mentioned, all of our applications,
1889.01 -> all the end-user applications are Web applications.
And Web applications as you know have a different
1893.691 -> security model. Their security model is, apps
are treated at a system level as if their
1898.85 -> fundamentally hostile, right? And so the browser
takes great pains, every Web browser to make
1904.15 -> sure that applications can't do things to
your system that they shouldn't be doing.
1908.17 -> So Web application can't change files on your
hard disk, right? It can't reconfigure your
1912.96 -> power settings, right? There are many things
that applications--Web applications intentionally
1917.17 -> cannot do that give it a better security profile.
In Chrome we've gone to greater lengths to
1923.4 -> secure that using a technique that we call
security sandbox setting. So this is in Chrome
1927.97 -> today when you run it on windows for example.
In Chrome OS, we've taken it to even a greater
1932.71 -> length. So some of the new techniques that
we're using in Chrome OS to secure these Web
1938.33 -> applications, this is a techniques, it's like
[INDISTINCT] what are called Linux names basis,
1943.31 -> and then it changes to the tool chain itself.
So meaning, to the compilers that we use to
1949.35 -> compile Chrome. These give us additional benefits
like stack protection, things of that nature.
1951.87 -> And what the security sandbox means is that
every tab that you run in Chrome OS is running
1957.25 -> completely locked down and separated from
the other tabs in the system, but also from
1961.49 -> the underlying operating systems. So we've
protected the OS from the Web applications.
1965.45 -> We've protected the Web applications from
each other. Let me talk a little bit about
1971.07 -> the file system. So file systems are, you
know, not the most glamorous part of an operating
1973.25 -> system but they are very important and we've
done some pretty interesting things here and
1979.09 -> are working on some more that I want to tell
you about. So the first is, as I mentioned,
1983.98 -> the system is always auto-updated; we continuously
auto-update the operating system of Chrome
1989.34 -> and all the bits that are on the machine.
And as we do that, there are basically what
1996.25 -> are called a few file system partitions. So
on the solid-state storage drive, there are
2001.121 -> a couple of different areas of the hard disk.
And one of the interesting things that we've
2004.26 -> done is we've made the primary system area,
what's called the root partition read-only,
2008.88 -> and this provides a lot of protection, right?
It basically means that the operating system
2013.46 -> bits on the disk itself and even the Chrome
executable is in the area that's not writable,
2018.45 -> right? At the OS level, it's locked down,
and this is actually quite unusual on operating
2023.15 -> systems. It sounds obvious as I say it, but
most of OSs today don't do this. The system
2027.84 -> is typically in a writable partition which
is fairly scary. So we really locked it down
2033.16 -> in that regard. The other interesting thing
we've done with the file system is on the
2038.66 -> user partition. So this is where user data
is stored. When I set my system settings,
2043.03 -> like my Wifi settings or my background theme
or bookmark, things of that nature. We've
2047.21 -> done a couple interesting things. The first
one is that it's always encrypted. It's always--user
2052.35 -> data is always encrypted on a Chrome OS machine,
and this provides some great benefits. One
2057.48 -> of them is just, is safety of your data, right?
Should you even lose your machine, you now
2063.05 -> have a machine out there that has storage
on it that you know has some personal data
2065.659 -> on it, you could be assured that it's--that
it's encrypted, right? And this means that
2069.45 -> if somebody, some bad guy gets it, opens up
your machine with a screw driver pulls out
2073.159 -> the drive, puts it in another computer, they'll
have a very hard time reading those bits,
2077.04 -> right? As with all security, you know, anything
can be cracked but we've made it very, very
2082.59 -> difficult, right? They now have effectively
what's a set of cryptographic random numbers.
2086.98 -> So it's going to be quite challenging to get
any personal data out of it. Let's see, the--and
2093.929 -> then the other interesting thing about the
user data partition, what really makes this
2097.19 -> a Cloud device is that all the user data has
sync back to the Cloud at all times. So really,
2101.86 -> all we use the local user data for is as a
cache, as an accelerator. So all the stuff
2107.15 -> that you set, whether it's bookmarks or backgrounds,
system settings like Wifi settings are synced
2112.48 -> back to the cloud. And this has this wonderful
property that if you use a Chrome OS machine
2116.95 -> for a while, all the data is getting sync
back, you lose your device, you give it to
2121.27 -> somebody else, get a new one log in, in a
matter of seconds all the data re-syncs back
2125.74 -> to the machine and it's just the way that
you left it. And that's--we think that's a
2129.12 -> pretty radical interesting notion for an operating
system. Let me transition back to Sundar,
2134.05 -> and he'll tell you a couple of more points.
Thank you.
2135.74 -> >> PICHAI: Okay. So I hope Matt's talk was
technical but I hope what we are trying to
2145.2 -> do here is not just another operating system,
we are trying to offer a choice for users.
2149.93 -> So the model of computing we are trying to
advance is pretty fundamentally different.
2154.22 -> And we really hope the community gets excited
by what we are doing and we can work together.
2159.37 -> Security is not an abstract issue. It really
makes a difference in the lives of people.
2162.65 -> People struggle a lot with issues with their
computers and so we really want to make it
2167.75 -> better. So I want to switch gears and talk
about how we are going to go to market. This
2171.89 -> is not something we are ready to talk about
in detail today. I want to give a high level
2175.27 -> overview of what we are doing. We will be
talking a lot more next year. It is important
2180.44 -> to understand how we are going to go to market
here. There are a couple of interesting differences.
2184.59 -> One is we are working on the Google Chrome
OS image, the software. But in addition to
2190.77 -> that, we are actually going and working with
partners to specify components of the hardware
2196.75 -> level. Matt gave one example, for example,
we don't support hard drives, we support only
2202.67 -> solid-state drives. We will call out the specific
wireless cards we will support as an example.
2208.5 -> The reason is we really want software to understand
the underlying hardware so that we can make
2214.71 -> it much faster and more secure. And I think
that's an important part of what we are trying
2219.21 -> to do, it's important to understand. So we
not only have software, we are specifying
2223.9 -> references hardware components and together
it makes the Chrome OS device which we are
2227.51 -> working at the top OEMs to come to market.
But as a consumer, for you to buy a Chrome--you
2233.11 -> can download Chrome OS and install it on any
of your current machines. You would have to
2237.471 -> go and buy a Chrome OS device in the market.
So that's very important to understand. Our
2242.67 -> target timeframe is end of next year, we want
to be there ahead of the holiday season with
2248.12 -> devices in the market. In terms of the hardware
itself, one thing I want to highlight is,
2254.16 -> while netbooks today are very, very popular,
we do understand there are some pretty [INDISTINCT]
2259.61 -> usable issues with some of the netbooks out
there. We really care about the end-to-end
2265.19 -> user experience. So we're going to be working
with our key partners very hard to make sure
2268.62 -> you see slightly larger netbooks, effectively
netbooks which can accommodate the full size
2274.47 -> keyboard and a much more comfortable touch
pad. We care about the displays. We care about
2279.54 -> the resolutions which people get on those
displays. And those will all be part of the
2282.68 -> specified reference hardware components here.
We really want to make sure we get compelling
2287.99 -> devices out in the market place. And again,
this is about a year away. Let's go to next
2292.41 -> slide. The primary reason we are here today
is I'm very excited to announce as of today,
2297.54 -> the code is open. We are completely going
to be developing this in the open from now
2302.25 -> on, which means, Google developers and the
external developers work of the same tree.
2308.66 -> We will not be here today, it won't be possible
for us to do what we are doing today where--if
2313.72 -> not for several large open-source projects.
We are incorporating components from many
2318.57 -> open-source projects, to name of few, the
Linux kernel, Ubuntu, Moblin, WebKit, et cetera.
2324.72 -> So thanks to all those people who have contributed
to these great projects. We really hope you
2329.72 -> continue contributing to those because everything
we do, we are going to be good open-source
2335.19 -> citizens and commit the code back upstream
so that others benefit as well. And even the
2340.51 -> new model of computing, we are trying to achieve.
We really hope--we are looking to feedback
2344.81 -> from the open source community. So if you
are a Web developer, we really want you to
2349.74 -> take advantage of the new HTML5 capabilities
and help write better Web applications. If
2355.09 -> you are an operating system developer, if
you are a kind who loves to build your own
2358.92 -> operating system, you need to buy one--a few
of the netbooks which are available today,
2364.08 -> you need that, you need a screw driver, you
need a few components, and you can get Chrome
2368.4 -> OS up and running today. So we really are
looking forward to your contributions. Before
2373.13 -> I wrap up, you know, we went through a long
presentation to try and explain to you what
2377.79 -> Google Chrome and Chrome OS is, our marketing
team looked--took a look at it and said they
2382.01 -> thought the whole thing could be done in a
very, very different and in a much simpler
2386.07 -> way. So they worked with a set of external
folks, to produce a three minute video which
2389.35 -> I think really helps explain what Chrome OS.
So, we will do the video and then I'll come
2396.21 -> back for Q and A.
>> MALE: So, you are on the internet using
2403.73 -> a Web browser, you know, that thing with the
address bar and back button, and bookmarks.
2409.3 -> The thing you're in right now up there, yeah,
that's your Web browser. If you're like me
2418.15 -> when you're on your computer, you spend something
like, I don't know, 90 percent of your time
2425.09 -> of the internet in a browser, there's emails,
chatting, your reading news, watching videos,
2426.09 -> playing games, your buying things, just to
name a few which kind of makes the Web browser,
2428.73 -> the most important program on your computer.
And if you think about it, it hasn't always
2434.396 -> been this way. You see, Web browsers were
first designed a long time ago with the old
2437.78 -> internet in mind. You know that one it was
slow and mainly just words with links that
2442.119 -> just send you to more words with links, back
before all of these innovations. So some guys
2448.11 -> at Google asked, what if we redesign the Web
browsers from scratch with an eye towards
2452.73 -> the new Web, you know, maps, video and Web
apps that are a lot more dynamic. And so they
2458.421 -> created Chrome, a Web browser that's crazy
fast on today's internet, and it's sleek and
2463.19 -> more secure, but mostly it's really fast.
I mean, my biggest question when I boot up
2468.35 -> my computer is how long until I get on the
internet, right? I mean, if there isn't any
2472.34 -> internet, I might not even use my computer.
Did you know that even the fastest computers
2476.88 -> will still take like 45 seconds to boot up,
45 seconds, you can make a sandwich in that
2482.03 -> time. So here's what's going on when your
computer is booting up, there's this list
2485.38 -> of things to do, stuff I'm sure you don't
care about but it cranks through them one
2488.88 -> at a time. What you'll probably notice is
that your programs begin loading up slowly
2492.869 -> and if you're like me, as soon as you see
your Web browsers icon appear, like double
2495.84 -> clicking it over, and over, and over, let's
go buddy, I got some emails to read. Well
2499.08 -> all this stuff is called your operating system.
And overtime it gets rusty and your once fresh
2504.72 -> computer gets slow. Well, Google was like,
wait a second. If you're operating system
2509.56 -> is a hassle and all you're really using it
for is to get on your Web browsers, to get
2512.95 -> online, then maybe, well, maybe we don't need
this anymore. What if when you pressed on,
2517.9 -> you were on the internet in seconds, what
if your browser was your operating system?
2522.46 -> And so check this out, this means that you
don't have to deal with managing programs
2526.84 -> or nagging updates, or lost files, or confusing
settings, or blue screens of doom and there's
2533.25 -> no nagging updates, just your browser. Which
means you can still listen to music, you can
2539.75 -> watch movies, interact with friends, you're
creating documents, you're playing games,
2543.16 -> you're writing your emails, you're doing all
of this stuff that you are already doing on
2546.62 -> the Internet, but here's the thing, none of
this is stored on your computer. What? None
2550.79 -> of it you ask? Yeah. None of it. Really nothing...?
Yeah. Nothing is stored on your computer.
2555.96 -> Well, where is it? It's on the internet. You
know, like when you access your emails from
2561.85 -> your computer and your phone, the e-mail,
it isn't stored on either device. So everything
2566.43 -> is stored on the internet, then your phone,
your computer, all of these devices are what
2570.67 -> people call stateless. Which is kind of a
big word, so maybe just remember this, Chrome
2577.44 -> is a totally rethought Web browser and you
could download it right now on your computer.
2581.071 -> But Chrome OS is a totally rethought computer
that let's you stop worrying about your computer
2586.85 -> so you could focus on the internet which is
what most of us use our computers for nowadays
2593.03 -> anyways.
>> PICHAI: Thanks. So we have some time for
2607.07 -> questions, I think the way I thought there
were going to be mic. So there are--there
2611.23 -> is a mike down here and a mike down here.
So if you could, given, we are Web casting
2616.34 -> this, we would greatly appreciated if you
can walk or if not I'll repeat the question.
2619.66 -> >> We can walk...
>> PICHAI: Yeah. And there's mic down there.
2627.68 -> Thank you. And there is a mic down there as
well.
2630.24 -> >> GRANT: Hi, my name is Christian Grant.
This is an amazing innovation and I'm--it
2632.04 -> seems to make things easier for users. There
just seems to be so many questions I have.
2642.18 -> One question would be, this seems to be, this
seems to be, I mean, what is the focus group
2648 -> for this type of device? I mean, I could imagine,
I mean, HTML have this Android device at the
2653.77 -> moment and that the developers that are developing
Android apps, so one question could be, can
2660.22 -> you run android apps on Chrome OS. But another
question I have is, I was joking with Larry
2667.86 -> Ellison about, now the Android devices are
becoming so powerful, I mean, soon there'll
2673.51 -> be a one gigahertz processor and 64 gigabytes
of memory in Android device, so I could move
2679.5 -> my data center to the Android device so that--here
comes the Cloud. So the other question is
2684.4 -> could Chrome, would it be like a Chrome service
solutions, so it's not just a client device
2690.83 -> but actually the Cloud device. I think those
are some of the questions I have but...
2694.87 -> >> PICHAI: Oh, thanks.
>> GRANT: Many more.
2696.24 -> >> PICHAI: There are many interesting possibilities.
I mean, we are clearly focused on first getting
2703.119 -> great netbooks out there, to be very clear.
But the good thing of what you're pointing
2707.95 -> out is, I do think even across Android what
they're doing, there are large innovations
2712.85 -> that are going on. They are all open sourced
and they all involve the community. And when
2719.66 -> you have open platforms like that, I think
we are going to go through a paradigm shift
2723.5 -> in computing, which is what we are excited
about. In terms of the other possibilities
2727.15 -> you are talking about, you know, time will
tell, so. Next question.
2730.05 -> >> KRAZIT: Hi, Tom Krazit with CNET. If you're
specifying hardware components, it would sound
2733.78 -> like you're likely have a decent idea what
these things are going to cause. Can you give
2738.88 -> us some idea of what we can expect the Chrome
OS netbook to cost next year?
2745.829 -> >> PICHAI: So, now, you will hear those messaging
from our partners as they come up with devices.
2752.36 -> We expect to have devices in the price ranges
people are used today. Having said that, it's
2757.55 -> tough to predict the hardware curve, a year
ahead of time, so we are focused on getting
2762.58 -> netbooks out there which are very easy to
use and so you will see larger netbooks than
2768.24 -> what you are seeing today. So we're working
hard to accommodate a full-sized keyboard,
2771.36 -> et cetera, as I just mentioned. But in terms
of the price point, you know, our partners
2775.37 -> will announce it next year.
>> MALE: Do you have a price target that you
2780.34 -> were specifying for your partners?
>> PICHAI: I'm sorry. What's your question?
2781.55 -> >> MALE: Do you have a price target that you
were asking your partners to hit?
2787.05 -> >> PICHAI: No, we have not. I think that's
an off-the-shelf EPC. I don't know.
2795.79 -> >> MALE: It's actually--we'll have all that
information...
2798.019 -> >> PICHAI: Sorry. Let's repeat since people
are on the Webcast, Mike asked what's the
2801.36 -> netbook which is...
>> MALE: Sure.
2802.68 -> >> PICHAI: Off-the-shelf—which is on the
demo and we just responded. So, let's go to--it
2807.27 -> will keep swapping sites.
>> MALE: Couple of questions. First of all,
2810.98 -> are you planning on for the APIs to be supporting
the W3C work on device API working group supporting
2817.09 -> those standards? And second question, as I
understand that you're going to be specifying
2822.58 -> down to the component level what the device
can use. If you're a manufacturer that would
2830.86 -> like to be included in that, is there a process
to apply to be considered?
2833.6 -> >> PICHAI: Let me answer the second part of
the question and Matt will answer the API
2837.78 -> question. So in terms of--in terms of--if
you go to--we have a lot of documentation
2846.07 -> on our Website and we have been reaching out
to all the top partners by now. So, we are
2850.96 -> reaching out pretty, pretty aggressively and
trying to work with people. So, for most partners,
2855.23 -> the information is already--being trickling
down. I mean, it's been going both ways between
2859.94 -> the two companies. We will also have plenty
of documentation. For developers who want
2864.87 -> to try this out, if you come to our Website,
we have a page by which manufacturers can
2869.42 -> come and see which software devices can support
Chrome OS based on the competence we have
2874.05 -> specified and what change you need to make
in those devices to run them today. But, we
2878.17 -> are working very closely with partners.
>> PAPAKIPOS: Sure. To answer the standards
2881.5 -> part, yeah, we're working very closely with
the W3C, the WHATWG, the Chronos group that
2885.09 -> owns the OpenGL and WebGL Standards to standardize
as much of this stuff as we can. The device
2893.051 -> API is when, you ask about. I'm not as familiar
with the details. We're definitely looking
2897.1 -> at that. And I was looking at some other stuff
the other day, it's still in the fairly early
2900.26 -> phases but we're tracking it closely. And
with Web standards, it takes awhile for this
2906.02 -> stuff to get finalized and so many of those
are still evolving and we're tracking it and
2911.9 -> involved very closely. But in general, we
want to see all this gets standardized and
2914.9 -> supported across multiple browsers running
on multiple operating systems.
2918.32 -> >> MALE: Roberto Sazuie with the French News
Agency, will you think about having an application
2924.75 -> store like, let's say like a market for Android?
And what about a driver certification, is
2932.88 -> Google want to certify all the drivers that
OEMs will have to develop for, let's say,
2938.82 -> video cameras or camera? Last question is,
what about maybe editing applications? So
2945.991 -> if I we want to edit photos or videos, I can--it
seems I cannot do it with Chrome OS.
2951.7 -> >> PICHAI: Okay. So, there are three questions
there. So, let me remember and go through
2956.35 -> them. The first question is will we have an
application store. So, we'll have a lot more
2960.619 -> details to announce in this area. I showed
some initial concepts of how people can discover
2968.42 -> applications. You saw me play a chess game.
It is--we really care. The Web has great applications.
2974.13 -> I see a real app platform count the number
of applications. The reason they can count
2979.24 -> is it's countable. In the Web, there are hundreds
of millions of applications. So, our job is
2984.79 -> to make sure people can discover those applications.
So, we'll be working hard in solving the problem.
2989.82 -> Your second question was...
>> MALE: Driver certification.
2991.98 -> >> PAPAKIPOS: I can take that. So, on testing
of drivers and selection of hardware components,
2997.45 -> we're working closely with hardware partners
on that stuff and we definitely want to make
3002.21 -> sure that the systems are built with based
off our reference designs that Sundar mentioned
3005.76 -> with very high quality components with Open
Source drivers, wherever possible. And we
3012.09 -> definitely have a testing plan that we're
working on to make sure that it all works
3015.97 -> at the end of the day. The drivers are of
the highest possible quality. Absolutely.
3019.3 -> >> PICHAI: The third question I'm sure, the
question will come up in different forms.
3021.69 -> So, the question is, there are applications
today which are not available on the Web.
3028.22 -> And you mentioned a few examples. The short
answer is, first of all, we really focused
3034.84 -> as the use case for this device, most people
who buy this device next year, we expect them
3039.61 -> to have another machine at home, right? We
are trying to deliver a device, a companion
3044.32 -> device. It maybe your primary device in terms
of the amount of time you spend, right? But
3050.47 -> the goal of this device is for it to be a
delightful experience for you to be on the
3054.51 -> Web, so that's the scenario we are focusing
on. There are a few use cases where it's challenging,
3060.5 -> even in those areas that are actually alternatives
on the Web than people realize today, right?
3066.82 -> So we will be doing a good job of surfacing
those applications which can solve those problems.
3071.68 -> There will be some things which this will
not be able to do. If you're planning to spend
3076.55 -> your entire day, if you're a lawyer editing
contracts back and forth, this is not the
3080.93 -> right machine for you, not what we will come
out with next year, so. Question.
3087.109 -> >> MALE: One thing about Codec Support, generally
a problem for desktop OS especially from an
3091.38 -> Open Source point of view...
>> PAPAKIPOS: Sure.
3093.27 -> >> MALE: ...and also native-client support,
does everything that works in Chrome work
3097.17 -> in--from OS.
>> PAPAKIPOS: Yes. So, I'll take the second
3100.08 -> part first. So, it's certainly everything
that works in Chrome works in Chrome OS and
3103.17 -> that includes codecs. So, the codecs that
we've been done with HTML5 video codec and
3108.92 -> audio codec certainly will make sure they
work in Chrome OS and we're working to add
3113.109 -> support for more and more codecs. We also,
as you saw, we ran flash today and we ran
3118.13 -> the flash codecs and are very committed to
that. We're also doing a lot of work with
3122.46 -> codec hardware acceleration, right? It's not
enough to just run it, run it with a traditional
3125.97 -> decoder; we're also working the hardware to
accelerate those as much as possible, wherever
3132.93 -> possible.
>> MALE: And then Chrome native client, are
3136.38 -> those hardware accelerator have been built-in
to the whole hardware experience as well?
3139.376 -> >> PAPAKIPOS: Yes. So, all the stuff that's
available in Chrome will come in Chrome OS
3141.57 -> as well and we do think native client is an
important part of this story.
3145.79 -> >> PICHAI: Yes. And to go back to the previous
question, we didn't talk about it today. In
3148.99 -> addition to the HTML5 capabilities you've
heard about, we are investing a lot in additional
3154.67 -> technologies like native client which will
make--make it really possible for some of
3159.55 -> the most performance in terms of desktop applications
to be recognized Web applications.
3163.809 -> >> PAPAKIPOS: Sure.
>> PICHAI: So, we are working on that. And
3166.71 -> you asked will all that is in Chrome being
Chrome OS; that is true. But more importantly
3172.23 -> a lot of what you've seen in Chrome OS will
make its way in Chrome. So, you know, and
3177.69 -> I think that's an important part to realize.
On day one, when we launched this, a lot of
3182.72 -> the capabilities and if you are an app developer,
what we exposed will already have that alone
3190.08 -> 50 million users, right? Because every Chrome
user will be able to see the applications
3196.07 -> menu, et cetera. So I think that's very, very
important to understand. So, that question
3201.57 -> from the middle was will we support Silverlight.
So, Chrome OS today, you know, users can install
3208.54 -> binaries on the system. So, in the case of
certain select plug-ins, we are working hard
3213.63 -> to integrate it closely. So we will have a
lot more to announce on how we plan to provide
3217.97 -> for plug-ins in the future.
>> MALE: But you're working with Microsoft
3221.1 -> to support...
>> PICHAI: Sorry. I don't have anything to
3224.859 -> comment on that question right now. Question
there.
3230.7 -> >> MALE: Yeah. My question was actually about
plug-ins. You've already said multiple browsers
3237.72 -> will be able to run. So, does the browser
end have to go through you to get on the machine
3243.98 -> or how--how would that work and how--and then
other part is that supply plug-ins to those
3248.95 -> browsers, how do they get on to the machine.
>> PICHAI: Sorry. I think Google Chrome OS,
3255.75 -> Chrome is the OS, right? So, when you say
other browser runs, what we have tried hard
3261.67 -> to do is end-to-end Google Chrome OS is open
source. It's free, open, and redistributable.
3268.63 -> So, if another browser vendor or anyone else
out there is interested in making a similar
3273.97 -> operating system with their browser, we want
it to be possible. So we are working hard
3277.92 -> to make sure the code is available for them
to do it. But to swap, I mean, so, that's
3280.97 -> the way I would answer that question.
>> MALE: Okay. But, then you said before,
3281.97 -> multiple browsers will be able to run, isn't
that what you said?
3285.8 -> >> PICHAI: I don't recall--either of us, saying
that, so.
3289.83 -> >> MALE: So, there has to be a certification
process by Google first before any other browser
3297.91 -> will run?
>> PICHAI: No, no, no. So, just so that you
3303.73 -> don't understand. In Google Chrome OS, Chrome
is the operating system, so there is--there
3307.84 -> is no certification process for another browser
to run. The entire code is open source, so
3312.131 -> someone can take it, put out a version of
it based on other browser, so.
3317.351 -> >> MATT: It's very similar to how things work
with Google Chrome, right? So, we build and
3321.91 -> ship and auto update Google Chrome and millions
of users use that. There's also the Chromium
3327.28 -> Open Source Project and many people build
their own variants of Chrome called Chromium
3333.07 -> and they change it in any number of different
ways and we expect and encourage that and
3337.109 -> Chrome OS is exactly the same way. We expect
people will do many interesting things of
3340.71 -> it.
>> PICHAI: Let's take the next question.
3342.45 -> >> MALE: Do you envision the device exclusive
or the system exclusively running on netbooks
3347.8 -> or do you see a variety of devices using this?
And then the second question is, did you--are
3354.65 -> you able to speak to any of the hardware partners
that you have.
3358.01 -> >> PICHAI: So, today is the announcement of
the open source project. We will be announcing
3362.89 -> details on hardware in the middle of next
year since the devices are going to be in
3369.3 -> the market by end of next year. And the first
part of your question was...
3374.289 -> >> MALE: So, you've spoken almost exclusively
about netbooks. Do you see it running on laptops,
3377.69 -> on desktops, on a variety of devices?
>> PICHAI: The question is we are initially
3383.359 -> fully focused on--it's a scope issue for us.
We want to make sure we deliver a very compelling
3388.52 -> device. So we are initially focused on what
I would call netbook-like compacters, so essentially
3395.849 -> clamshell with a display, real keyboard, and
a touchpad, right? That's what we are focused
3401.14 -> on. In terms of how we are designing the system,
we aren't constraining it so in the future
3406.24 -> we want this to be able to run on laptops,
desktops, et cetera, but we are not focused
3410.66 -> on that for 2010.
Male: Just to make it easier for our readers,
3418.32 -> how big is the program and how does that compare
to the conventional software, I mean, operating
3423.98 -> system to the file size?
>> PICHAI: Yes. So since it's an open source
3430 -> project, we have a lot in the code right now
to help it debugging, et cetera. So, I think
3435.16 -> you will see that develop and change over
time. You know, it's--the code is out there
3439.44 -> in the open for people to see. But we are
working very, very, very hard to have a very,
3444.89 -> very simplified code stack and that will be
clear for developers who can see that in the
3447.71 -> open.
>> MCCRACKEN: I'm Harry McCracken with Technologizer.
3448.71 -> Can you speak to whether there's any level
of offline access in terms of other gears
3457.859 -> as part of this, I mean, what happens when
I'm on a plane and I don't have Wi-Fi or I
3463.38 -> don't feel like paying ten bucks for Wi-Fi?
>> PICHAI: So, the question is how do we provide
3467.77 -> for offline access. So, first of all, there
are few things we are thinking about. This
3471.47 -> device is primarily intended for use with
connectivity. Wi-Fi is the use case we have
3475.54 -> in mind and we are designing it because it's
primarily for you to spend time online. Having
3480.82 -> said that, I showed experiences by which you
can plug-in and play media, right? So you
3486.28 -> can cash media locally and you can watch videos,
read books, listen to music, et cetera, play
3491.91 -> games. So, that's something you'll be able
to do while offline. In addition to that,
3495.8 -> as part of the HTML5 capabilities or, you
know, we are exposing offline capabilities
3501.82 -> with the access to local storage, so any application
which takes advantage of the HTML5 offline
3506.43 -> capability and implements on top of it, will
work while you're not connected. So, that's
3509.23 -> all the things that will happen.
>> MALE: Are you specifying wide area wireless...?
3514.36 -> >> PAPAKIPOS: Can I take that? So, we're focused
on--we're focused on 80211N which is the next
3522.42 -> generation, 80211 standards. So, you know,
that's the mainstream wireless technology
3527.5 -> that's in use primarily today, so, that's
our primary focus.
3530.74 -> >> PICHAI: Just hold on. Since we are on the
Webcast, we'd really appreciate it if you
3535.119 -> guys use the mic, otherwise people can't hear
the question. Thank you. Sure. But there are
3539.52 -> people standing in line, too. Thank you. So,
next question, please.
3543.01 -> >> MALE: I'm wondering about virtualization,
can it be run in a virtual machine now? Can
3551.12 -> people try it out today?
>> PAPAKIPOS: Today, you can build the source
3555.34 -> code and run it in a virtual machine and certainly
we do that for development. That's a very
3558.99 -> convenient way to do development. So the focus
today of the open source release is that to
3563.27 -> get developers working with the code being
able to compile it, being able it debug and
3567.75 -> virtual machines are great way to do that.
>> PICHAI: Thank you.
3570.77 -> >> MALE: How are you working with partners?
I know that Adobe, I believe they have a solution,
3575.9 -> a Web-based Photoshop solution. Are you working
with other partners and maybe developers,
3582.41 -> but you said it's probably not to develop
the machine but let's say at one point as
3586.55 -> netbooks become more powerful, maybe developers
using Eclipse, I don't know if there's a Web-based
3592.35 -> Eclipse version, but are you working with
partners on enabling some of their applications?
3597.9 -> And the other question is, I think one of
the success factors for Android is the market
3603.06 -> place. There many reasons why it's so successful.
And then I'm just--I was wondering if Android
3609.31 -> apps would run on Chrome, but they're not
Web app, so maybe, what are your comments
3615.93 -> on that?
>> PICHAI: So, in terms of advancing more
3620.41 -> of Web applications to work, so independent
of Chrome OS, this is a major part of our
3625.57 -> focus. Writing Chrome itself, one of the things
we've tried to do is to really push Web applications
3630.89 -> forward. HTML5, native clients, so there's
a lot of work we are doing. So, things like
3634.53 -> Photoshop on the Web, we are very excited
by it and the way we approach it is we want
3638.83 -> to make sure the browser works and has the
capabilities for those thing to happen. The
3643.49 -> second part of your question is will Android
apps run on Chrome OS. The answer is since
3649.583 -> every application in Chrome OS is a Web application,
Android apps as certain today will not turn
3651.17 -> on Chrome OS. Mike?
>> MIKE: Just to follow up on that actually.
3652.17 -> I was going to ask a similar question but
Steve Jobs said the same thing when he first
3653.17 -> launched the iPhone, like, you know, you can
launch any app on this as you want as long
3658.98 -> as it works in the browser. And you know,
that's not going--you're going to get an incredible
3669.18 -> amount of pressure very quickly starting right
now to have Android-like apps working on this.
3674.91 -> Are you saying flat out there will never be,
or at least there's no plans right now for
3680.18 -> any kind of third party app system for people
to get their apps unto the--their apps unto
3685.33 -> this machine?
>> PICHAI: There's two things. You see, currently,
3687.93 -> our current plan is to only support Web apps.
So the third party apps will work as long
3693.46 -> as it's a Web application. I would call on
the form factory like netbooks.
3697.791 -> >> MIKE: That's exactly what Steve Jobs said
when he launched the iPhone not less than
3701.99 -> a year.
>> PICHAI: Let me point a couple of things.
3704.38 -> Yes. But in the iPhone if you looked at when
they launched the development framework, they
3707.93 -> didn't have the main applications in the iPhone
written as native applications, right? And
3712.83 -> so, in Chrome OS, even the apps we are writing
will all be Web applications. Just to see,
3719.11 -> the browser works very well on bigger form
factors. And in forms, a lot of times you
3725.21 -> see these applications being written as native
applications because the Web has challenges.
3729.54 -> We are working hard. Our mobile team is working
very hard to push the paradigm there, but
3735.49 -> I think it is different on larger form factors.
The Web work is very, very well. Next question.
3741.53 -> >> MALE: Yes. A few months ago, you said that
you thought that the native client would be
3745.41 -> an important part of the Chrome OS experience.
That would seem to imply that you have an
3748.18 -> Intel processor. My question is whether, if
you can still expect to see Chrome OS running
3753.76 -> on netbooks based on the ARM architecture.
And if so, can we expect the equivalent functionality
3756.859 -> on both platforms?
>> PICHAI: So you know, our goal with Chrome
3760.859 -> OS is to run it as a very open project and
we'll be working with a full variety of partners,
3766.76 -> including on the chipset side. So, you know,
Chrome OS will function both on X86 and ARM.
3772.98 -> And native client, you know, it works on X86
today, but there is work underway to make
3777.15 -> it work on ARM as well.
>> MALE: But that would, I mean, there would
3781.93 -> be different code delivered to device running
a different processor in that case. Do you
3786.349 -> have any thoughts on...?
>> PAPAKIPOS: I can take that. I mean, we'll
3789.44 -> make sure that--I don't want to go to all
the technical details today but we'll make
3792.94 -> sure that there's a way that you can run native
client-based applications that run equivalently
3796.99 -> on X68 and ARM.
>> MALE: Thanks.
3798.9 -> >> PAPAKIPOS: And there's a lot of work going
on in that today. You'll see more about it
3803.69 -> soon.
>> PICHAI: I'm sorry, yeah.
3806.68 -> >> MALE: You have two questions. The first
is, when you first announced Chrome OS you
3810.839 -> talked about it running on much more powerful
machines beyond just netbooks. What kind of
3815.63 -> a timeframe do you think that will happen
on? And second, is there a direct business
3820.839 -> model for Chrome OS, or is this just the latest
incarnation of getting people to be more active
3826.02 -> on the Web? For example, will it be offering
some vehicle for advertising directly in the
3831.63 -> browser?
>> PICHAI: So your first question is, all
3835.9 -> we are focused right now, you know, is for
2010 getting devices. It's very hard to build
3840.52 -> an operating system, one ship in a year, which
is what we are trying to do. And so that's
3844.38 -> what we are focused on. In terms of what is
the business model around Chrome, we are working
3849.07 -> with partners. All I can say right now is
Chrome OS is fully free. It's free and open
3854.57 -> sourced. And we really--we are fortunate that
as the Web gets better and people use the
3859.98 -> Web more, it benefits us as a company. So
that's essentially the [INDISTINCT] of how
3864.85 -> we think about it.
>> MALE: So will there be any specific new
3867.19 -> real estate devoted to advertisements, or
will it be just the existing ones we see in
3871.61 -> Gmail and Google search results?
>> PICHAI: There are no plans. Every application
3875.16 -> in Chrome OS is a Web application. It's the
same application you will get on any other
3878.88 -> browser, in any other computer.
>> MALE: Hi, [INDISTINCT] German News Magazine,
3884.21 -> Stern. Your demo made me wonder. In terms
of browser functionality, what is it that
3889.291 -> Chrome does that a regular alternate browser
logged in to all these Cloud services cannot
3896.44 -> do? Because when you speak of floating pellets,
whatever, to me it looked like just another
3901.03 -> pop-up window and things I could maybe do
with Firefox or any other browser.
3905.37 -> >> PICHAI: Sorry. Your question again? I fully
didn't understand it.
3909.13 -> >> MALE: So, the browser functionality of
Chrome, what you demoed, is that anything
3916.12 -> I cannot do with the current browser that
is logged in to all of these Web services,
3920.46 -> Cloud services?
>> PICHAI: Your question, look, Chrome, we
3924.4 -> take a standards-based approach to Chrome,
so most of what we showed here is available
3930.02 -> in other browsers. Having said that, there
are a lot of new user concepts which we are
3934.49 -> exposing today, which are not available in
other browsers today.
3937.23 -> >> MALE: For example?
>> PICHAI: We made application tabs, panels,
3940.72 -> I mean, these are things which we have done
which are not available, [INDISTINCT]. But
3945.14 -> more importantly, our goal isn't to say what
we are trying to offer is a fundamentally
3949.94 -> different model of computing. A model in which
from a user's standpoint, you're in to installing,
3956.119 -> managing software, you're managing data, it's
very fast, very simple and very secure. So
3959.609 -> I think as a model of computing, what we are
attempting to do is very, very different.
3963.319 -> >> MALE: And does that affect me also on non-Google
Chrome netbooks, on a regular machine where
3970.23 -> I would just install Chrome? Do I also reap
the benefits of your approach?
3974.92 -> >> PICHAI: Not everything. For example, in
Chrome OS, Chrome is tuned to run on the underlying
3980.96 -> operating system and hard drive, right? So
those benefits won't carry over. But some
3984.65 -> of the user experience benefits we're providing
in Chrome OS within Chrome will carry over
3988.92 -> to Chrome on other platforms. It's on a case-by-case
basis.
3991.64 -> PAPAKIPOS: And I can give a couple of examples
there. So things that we can't do in a conventional
3995.51 -> operating system that we can in Chrome OS
or things like the verify boot that I mentioned,
4000.69 -> the Malware prevention, the fast boots stuff.
We can't make your existing operating system
4003.98 -> boot faster. And then the file system stuff
that I mentioned. We did a lot of really interesting
4006.34 -> security things with the file system that
are underway. You can't do that to a conventional
4010.5 -> operating system.
>> PICHAI: Next question.
4014.5 -> >> CHAPMAN: Hi, Glenn Chapman, AFP. Thanks
for taking the time to brief us today. The
4021.58 -> broader concern that people expressed over
again about the Cloud is how you are going
4026.11 -> to get people pass, why should they trust
the reliability? You know, I mean, is it going
4033.099 -> to crash? Gmail goes down. All of the sudden,
I'm done for two hours. And then, how can--what
4034.9 -> are you going to do to assure people about
the security of their data that once they
4040.08 -> give Google servers all their personal information
that it can be trusted there?
4045.47 -> >> PICHAI: I'll answer your first--yes. The
first question is our point here is very simple.
4051.76 -> If your cloud is down, it affects on any computer
you are on, because most people and what they
4056.339 -> are doing, they are using Web mail whether
from your other machine or on Chrome OS, right.
4063.55 -> And so, that is important to understand. I
think when people talk about reliability of
4069.23 -> Cloud services, what I would like to see is
a comparison of the reliability of the Cloud
4073.78 -> versus what they actually have today. And,
you know, I think when, you know--so, I think
4078.65 -> that's the right comparison to me. I think
the Cloud will compare very, very favorably
4082.23 -> in those scenarios as well. To third is in
terms of trust and so on, I think it's really
4087.82 -> important that, you know, users have choice.
You know, at a higher level, we are fully
4091.91 -> open, so everything we do there is transparent
to at least developers who can educate users
4097.029 -> about what's happening. The second is, you
know, we--users are always in control. You
4100.249 -> know, you can decide what to do. You can decide
whether to buy a machine. Like today, you
4105.55 -> use Web mail. When you use their mail, your
email is stored in the Cloud, but it's a decision
4110.239 -> users make. It's, you know, so that's the
right way to think about it.
4112.27 -> >> MALE: Hi, Phil [INDISTINCT] from McKee
Electronics again. A couple of questions on,
4120.539 -> first of all, on the data synching or actually
the data is cached by Google Chrome OS, is
4127.609 -> that also open or is Google going to be the
only one that will actually, you can actually--that
4131.759 -> will actually host that data in the Cloud?
It's the first question. And the second question
4136.829 -> is regarding the signature process. Is that
something that Google will be in charge of?
4145.279 -> And will there be a charge for that?
>> PAPAKIPOS: Yes. I can talk about the signature
4146.279 -> steps. You see, signature step is based on
open algorithms that have been out there for
4150.209 -> a while. And our plan is to open-source that
whole thing as well, and we want that sort
4154.999 -> of reviewed by the security community. We
want them to poke at it and make--help us
4160.529 -> assure that it is secure. It is something
where we're using it to secure our auto update
4164.499 -> systems so we would sign the binaries at Google
for the Chrome OS, you know, executables themselves
4170.549 -> and distribute them. And so we'd sign them
here. There isn't any signing that we're contemplating
4174.369 -> for the Web application users would run on
the machine, right, so you don't need to run
4177.349 -> a signed version of Facebook or anything like
that. Certainly, we wouldn't want to do that.
4182.309 -> >> PICHAI: I want to take the chance. Sergey
has dropped by, so let's invite him for the
4184.48 -> Q&A as well. Let me grab a chair.
>> BRIN: Hi, everyone. I wasn't expecting
4192.099 -> to be put in the Q&A but now that I called
up, I guess I'm on the hot seat.
4197.109 -> >> PICHAI: So the next question.
>> GRANT: Hi, my name is Christian Grant.
4201.929 -> I know that one of the--it runs JavaScript
really well, the new Chrome OS. And I was
4208.57 -> wondering, or some browsers nowadays they
support Java. And if you are Chrome OS at
4216.32 -> one point in the future would support, let's
say, Java in one way, if there is running
4220.57 -> a, let's say, a Dalvik virtual machine and
in principle you could run Android apps, right,
4226.309 -> on the Chrome OS. Do you see that totally
an impossible...? I guess it's more of a suggestion.
4231.789 -> Or would it make sense at some point in the
future?
4234.09 -> >> PICHAI: So, please, it's a good suggestion.
Technically, there's nothing limiting a lot
4239.929 -> of what you're talking about. We are focused
on creating the use case by which everything
4245.099 -> is a Web application, so that's what we are
focused on today. In addition to the HTML
4249.809 -> JavaScript, native client is an area we have
talked about, but hopefully there are more
4253.079 -> interesting things we can do in the future.
>> STOKES: John Stokes. So, Dell has a laptop
4261.53 -> that's a full-sized laptop. But then it has
a small separate subsystem with an ARM processor
4266.51 -> and a chunk of Flash in it so that you can
boot to this instant on OS. This is kind of
4271.209 -> popular to make these Linux-based instant-on
OSs that are complimentary to, like, a full
4275.579 -> Windows install and stuff like this. Do you
guys have any plans to be like a second OS,
4279.38 -> like an instant boot OS on a more full-featured
laptop with magnetic media?
4283.55 -> >> PAPAKIPOS: No, we're very focused on the
Chrome OS thing. So you know, the way I think
4290.03 -> about it is we're trying to make the core
base operating system just boot quick and
4293.959 -> fast, right, and get you on the Web as quickly
as possible. So we're not spending a lot of
4298.679 -> effort on things like Jewel boot or multiple
types of processors in the same system. We're
4304.869 -> really focused on making a lean and mean netbook
that runs the Web really well.
4309.889 -> >> MALE: [INDISTINCT] So no drivers or that
type of thing. So I guess I just want to dig
4316.829 -> deeper in. So this thing is not going to be
able to run printers. Or like how, at least
4321.04 -> deeper, with using devices because we have
so many different devices that we use everything
4324.119 -> flip cameras to our printers, how is it going
to handle and how is it going to handle it
4327.67 -> in the future?
>> PICHAI: So we plan, you know, all standard
4334.82 -> keyboards, mouse, and anything which identifies
itself as a storage device like most cameras
4339.469 -> do, et cetera, will work. You saw on the demo,
we plugged in Android phone and it worked.
4345.579 -> In terms of printing, we are taking an innovative
approach to printing. We have a lot more to
4350.03 -> share about it next year. Yes, Chrome OS will
print, and we are working to make that possible.
4357.65 -> >> MALE: Thanks.
>> PICHAI: SO any other questions? Great--oh.
4364.59 -> >> MALE: So when you introduced Chrome, I
think a lot of it was putting a stake in the
4367.94 -> ground and inviting the community to come
and talk to you and become involved with your
4371.57 -> upstream, open-sourced providers. I see this--I
see Chrome OS as another opportunity to do
4377.05 -> that. You're very early on. Can you talk a
little bit about how you hope by releasing
4382.26 -> Chrome OS today the community of hardware
vendors just as you have to with ARM processor
4389.03 -> and such, and all the things that happened
in the Android and Chrome, how do you hope
4392.309 -> this community blooms out of Chrome OS and
comes together to kind of move it forward
4395.82 -> if you look towards releasing in a year?
>> PAPAKIPOS: Yes, great, great question.
4398.719 -> I mean, that's why we're here today is we're
really excited to get the open-source development
4403.01 -> community involved in this. And as you say,
there's two sides of that. One is independent
4407.309 -> open-sourced developers out there who just
want to help us build a great operating system.
4411.099 -> We're delighted to get them involved, and
also excited to see some of the technology
4415.19 -> that we may go out and help other projects.
So we're very serious about up-streaming what
4419.55 -> we do and then down-streaming to benefit from
other things the community is making. On the
4423.739 -> hardware processor component vendor side,
absolutely, this makes it very much easier
4429.179 -> for us to work with hardware vendors and processor
vendors, and lets them help get stuff running
4434.349 -> on their systems. And we're very excited about
that. So those are some of the main reasons
4440.61 -> we're here today is to get this code out there
in the open and start collaborating.
4455.449 -> >> BRIN: Uh-oh, now you're grilling me, because
I wasn't here. The question was, what about
4458.65 -> real time notifications on every page? I think
we definitely need support for real-time notifications
4464.65 -> in the browser and in particular, in Chrome
OS. I mean, just even today you guys might
4472.949 -> use Gmail chat in your Gmail, but if your
browser's off and you don't get alerted, you
4477.95 -> know , somebody can't, you know , pop up the
little widget. And I don't think that's a
4483.01 -> good reason to not have chat via Web app.
It's just capability that's today missing
4488.699 -> from the browser. And hopefully, we can introduce
that into the browsers as well as the Chrome
4494.239 -> OS.
>> PAPAKIPOS: There is a W3C standard that's
4496.579 -> being discussed. And the working groups right
now called it the notification API, and we
4502.69 -> have an implementation of that that we're
working on in Chrome. And it will be a big
4510.53 -> part of Chrome OS.
>> BRIN: I imagine that we would be a customer
4513.15 -> of that of for sure.
>> PICHAI: Okay.
4515.01 -> >> MALE: [INDISTINCT] On Star Magazine again.
Since we have Sergey now--I'm sorry. What
4522.809 -> is Chrome's strategic position for Google?
There's often, you know, war of the Clouds
4529.28 -> being declared, and Google going head to head
with Microsoft. So now you're even making
4535.139 -> your own laptops, so to speak.
>> BRIN: Well, the operating system for it.
4540.559 -> You know, we really--you know, call us dumb
businessmen but we're really focused on user
4545.949 -> needs rather than, you know, think about strategies
relative to other companies and what-not.
4551.559 -> And I think there is a real user need to have,
to be able to use computers easily. These
4558.829 -> netbooks are now, you $300 or $400, really
easy to buy one. You know, you could buy five
4563.619 -> to put around your house. But if you do it
today, there's no way you could manage them,
4568.269 -> right? I mean, the overhead of managing the
software and all would be way too high. We
4573.539 -> believe that the Web platform is so much simpler
a way where the machines are essentially kind
4578.829 -> of stateless, more cache like, and we think,
can still be performed, and yet much easier
4586.039 -> and simpler for individuals to use. So I think
since there is--that's a very important need
4592.709 -> in the market right now, that's what we're
trying to fill.
4596.559 -> >> PICHAI: With that, thank you all for coming.
I really appreciate your time, and we look
4603.57 -> forward of talking more about this. Thanks.
Source: https://www.youtube.com/watch?v=5JyFbF7QFlY