WEBVTT
00:00:00.530 --> 00:00:03.040
Hey there, this is Seth Waters
from Channel 9, coming to you
00:00:03.040 --> 00:00:06.870
from our brand new studios to
talk a little bit about Edge.
00:00:06.870 --> 00:00:07.880
I have some special guests.
00:00:07.880 --> 00:00:10.000
Why don't you tell us who
you are and what you do?
00:00:10.000 --> 00:00:11.140
>> So my name is Helen, and
00:00:11.140 --> 00:00:15.930
I am a Microsoft Edge intern with
the Developing Ecosystem team.
00:00:15.930 --> 00:00:16.890
>> Fantastic.
00:00:16.890 --> 00:00:18.060
>> I'm Jonathan Sampson.
00:00:18.060 --> 00:00:20.420
I'm a Program Manager on
the Edge Ecosystem team.
00:00:20.420 --> 00:00:24.890
>> So we just had a new release at
Windows, the anniversary update.
00:00:24.890 --> 00:00:28.305
Is there anything with Edge that we
should know about that's coming with
00:00:28.305 --> 00:00:29.250
that?
00:00:29.250 --> 00:00:32.350
>> So I think the biggest thing,
at least for me, is the extensions.
00:00:32.350 --> 00:00:36.290
So we've been previewing extensions
to Windows insiders for awhile, for
00:00:36.290 --> 00:00:39.790
a few months now, but they've
finally hit the stable build so
00:00:39.790 --> 00:00:41.750
everyone can go to the store and
download them.
00:00:41.750 --> 00:00:43.290
I think that's the biggest part for
me.
00:00:43.290 --> 00:00:46.000
>> So let's talk about
extensions a little bit more.
00:00:46.000 --> 00:00:49.040
Most people are familiar with
extensions in the web browser.
00:00:49.040 --> 00:00:50.200
How does Edge do it and
00:00:50.200 --> 00:00:52.460
how can people sort of participate
in building extensions?
00:00:53.610 --> 00:00:56.450
>> We actually, you know we're
kind of piggybacking off of
00:00:56.450 --> 00:00:57.780
the progress of other browsers.
00:00:57.780 --> 00:00:59.650
There's already a rich
ecosystem out there.
00:00:59.650 --> 00:01:01.180
People know how to build extensions.
00:01:01.180 --> 00:01:02.810
We have great APIs.
00:01:02.810 --> 00:01:04.360
And so what we did,
00:01:04.360 --> 00:01:06.490
similar to the extension models,
what we did with the web.
00:01:06.490 --> 00:01:07.980
Where we look at what
exists out there and
00:01:07.980 --> 00:01:10.140
we try to build something
that accommodates that.
00:01:10.140 --> 00:01:12.000
And so
we look at what other browsers have.
00:01:12.000 --> 00:01:14.390
What major extensions,
what APIs they expose.
00:01:14.390 --> 00:01:16.060
And we start to kind of chart
that out and say, okay,
00:01:16.060 --> 00:01:18.410
what can we develop first
to get the biggest impact?
00:01:18.410 --> 00:01:21.800
And so we were able to deliver
an initial round of APIs, and
00:01:21.800 --> 00:01:24.550
that'll give us support for things
like LastPass, which is amazing.
00:01:24.550 --> 00:01:27.575
I don't have to log into
lastpass.com to get passwords to
00:01:27.575 --> 00:01:28.740
paste into another tab.
00:01:28.740 --> 00:01:29.490
>> Awesome.
00:01:29.490 --> 00:01:31.530
>> And so that's kind of been
the approach we've taken.
00:01:31.530 --> 00:01:35.050
We continue to build that API
support and move forward.
00:01:35.050 --> 00:01:37.920
And we should have more and
more extensions in the future. Fantastic.
00:01:37.920 --> 00:01:39.040
So, you mentioned LastPass.
00:01:39.040 --> 00:01:41.890
Are there any other extensions that
we should be really excited about?
00:01:41.890 --> 00:01:45.610
>> So, I personally am excited
about AdBlock and AdBlock Plus.
00:01:45.610 --> 00:01:49.221
But, my main one is probably RES,
which is the extension for Reddit. [LAUGHS]
00:01:49.221 --> 00:01:49.870
>> [LAUGHS] Nice.
00:01:49.870 --> 00:01:52.535
>> Yeah, and that's been something
that's really fun to test for,
00:01:52.535 --> 00:01:54.350
cuz all I get to do is browse.
00:01:54.350 --> 00:01:55.280
>> Nice.
So now,
00:01:55.280 --> 00:01:57.977
you can browse the web at work and
not feel guilty
00:01:57.977 --> 00:01:58.659
>> Yes exactly.
00:01:58.659 --> 00:02:00.320
>> Fantastic
>> Strictly professional.
00:02:00.320 --> 00:02:01.930
>> Strictly professional.
00:02:01.930 --> 00:02:03.190
So you mention extensions,
00:02:03.190 --> 00:02:05.640
what else is there that's
coming out in the next release.
00:02:07.160 --> 00:02:08.140
>> In the next release.
00:02:08.140 --> 00:02:09.942
>> No in the one we can look at for
the anniversary.
00:02:09.942 --> 00:02:10.461
>> Right.
00:02:10.461 --> 00:02:15.790
>> Okay, so I think just the preface
thing's there were five core.
00:02:15.790 --> 00:02:18.695
Pillars that we were focusing on for
2016.
00:02:18.695 --> 00:02:22.790
So we talked about extensions, but
another one was accessibility.
00:02:22.790 --> 00:02:23.560
>> Okay.
>> And so
00:02:23.560 --> 00:02:27.630
with the newest update if I could
just show something on the computer.
00:02:27.630 --> 00:02:28.450
>> Let's do it.
00:02:28.450 --> 00:02:32.720
>> If we go to the HTML5
Accessibility test we can see that
00:02:32.720 --> 00:02:37.380
Edge is actually at 100%
compared to 89% on Firefox.
00:02:37.380 --> 00:02:38.680
And 81% on Chrome.
00:02:38.680 --> 00:02:41.420
>> So is Internet Explorer like
the slow cousin or something?
00:02:42.819 --> 00:02:43.469
>> Yes, yes.
00:02:43.469 --> 00:02:45.730
It's to say that we're much better.
00:02:45.730 --> 00:02:46.570
>> Fantastic.
00:02:46.570 --> 00:02:47.430
>> In the improvement.
00:02:47.430 --> 00:02:50.390
>> When we're talking about
accessibility, for those that don't
00:02:50.390 --> 00:02:53.740
have a disability and that don't
know anything about accessibility,
00:02:53.740 --> 00:02:56.980
why don't you talk a little bit
about what this actual means for
00:02:56.980 --> 00:02:59.005
those that need to have
these kinds of features.
00:02:59.005 --> 00:02:59.700
>> Mm-hm.
00:02:59.700 --> 00:03:02.970
So there are accessibility
API's that developers will
00:03:02.970 --> 00:03:04.940
implement to put on their websites.
00:03:04.940 --> 00:03:07.630
And that's sort of what
the site uses to test as well.
00:03:07.630 --> 00:03:11.190
And the whole point is that, hey how
can developers or how can people
00:03:11.190 --> 00:03:14.880
make their websites more accessible
for people who use screen readers?
00:03:14.880 --> 00:03:18.410
Which will basically capture your
page, and it will read out stuff.
00:03:18.410 --> 00:03:21.340
So I think that's one of the main
parts of being accessible and
00:03:21.340 --> 00:03:24.160
making sure that anyone
can use our websites.
00:03:24.160 --> 00:03:25.367
>> So talking about accessibilities,
00:03:25.367 --> 00:03:28.660
it's something that I as
a developer do in my website?
00:03:28.660 --> 00:03:32.140
And what does Edge sort of
help me with on the back end?
00:03:33.850 --> 00:03:36.020
>> Yeah, I was gonna say,
00:03:36.020 --> 00:03:39.550
it's kind of a shame that the web
isn't even more accessible today.
00:03:39.550 --> 00:03:42.190
Because it takes very little effort
to really start to build out a rich,
00:03:42.190 --> 00:03:43.740
accessible experience.
00:03:43.740 --> 00:03:45.800
One of the things that Edge does
though if you check the developer
00:03:45.800 --> 00:03:49.410
tools, so you press F12 or
if you open up your
00:03:49.410 --> 00:03:52.630
action menu at the top and go down
and turn on the developer tools.
00:03:52.630 --> 00:03:55.727
We actually expose the accessible
tree so aria labels and
00:03:55.727 --> 00:03:59.080
that type of stuff can be on
the page, we expose the tree that is
00:03:59.080 --> 00:04:02.501
actually gonna be used by the
accessibility tools and stuff and
00:04:02.501 --> 00:04:06.940
that's something that I don't think
any other browser does right now.
00:04:06.940 --> 00:04:10.170
And so as a developer this
gives you a major leap forward
00:04:10.170 --> 00:04:13.300
in understanding exactly how your
document is gonna be parsed and
00:04:13.300 --> 00:04:15.560
presented to blind users,
00:04:15.560 --> 00:04:18.820
the hearing impaired,
and that type of stuff.
00:04:18.820 --> 00:04:20.320
It's a pretty phenomenal
addition to it.
00:04:20.320 --> 00:04:23.080
Its been super popular, well
received online because it's just
00:04:23.080 --> 00:04:25.330
something that has been really
difficult to do in the past.
00:04:25.330 --> 00:04:26.530
That's really awesome
because I could,
00:04:26.530 --> 00:04:29.020
as a developer,
put a floating div that is
00:04:29.020 --> 00:04:32.130
put somewhere else but it might be
read in the accessibility tree in
00:04:32.130 --> 00:04:34.650
a different order which might make
the reading completely hosed.
00:04:34.650 --> 00:04:35.570
>> If it's read at all.
00:04:35.570 --> 00:04:36.530
>> Yeah.
00:04:36.530 --> 00:04:37.100
That's awesome.
00:04:37.100 --> 00:04:40.060
So you mentioned extensions,
accessibility.
00:04:40.060 --> 00:04:40.680
What else is there?
00:04:41.730 --> 00:04:45.340
>> Another pillar from last year and
you can read this at our blog post.
00:04:45.340 --> 00:04:49.320
Was performance and
just fundamentals in general.
00:04:49.320 --> 00:04:52.899
So, have you seen our battery
life video by any chance?
00:04:52.899 --> 00:04:53.737
>> I haven't.
00:04:53.737 --> 00:04:54.346
>> Really?
00:04:54.346 --> 00:04:55.500
>> I heard about it.
00:04:55.500 --> 00:04:59.640
I read your blog post this morning
in preparation because I do prepare.
00:04:59.640 --> 00:05:00.460
But I didn't see that.
00:05:00.460 --> 00:05:01.800
Why don't you describe the video and
00:05:01.800 --> 00:05:03.420
then maybe we'll put
a link at the bottom.
00:05:03.420 --> 00:05:07.230
>> Basically it's a set up of
four surface books and we're
00:05:07.230 --> 00:05:10.770
playing videos on all four of them
on different browsers in Windows 10.
00:05:10.770 --> 00:05:13.150
And you can just see
how Microsoft Edge,
00:05:13.150 --> 00:05:16.780
when you play the videos,
it lasts definitely the longest and
00:05:16.780 --> 00:05:19.920
I think that plays testament to the
improvements that we made in battery
00:05:19.920 --> 00:05:22.365
life and efficiency on
Edge which is a big part.
00:05:22.365 --> 00:05:24.090
>> Okay.
So let's talk about that because it
00:05:24.090 --> 00:05:27.110
feels like,
how do you make it do that?
00:05:27.110 --> 00:05:28.850
Cuz the video was
a video is a video.
00:05:28.850 --> 00:05:33.150
How do you make the battery
life sort of better in Edge?
00:05:33.150 --> 00:05:35.920
>> That's a good question, I mean
that's maybe a question that's
00:05:35.920 --> 00:05:38.480
more aimed towards the people that
are working on those specific tools.
00:05:38.480 --> 00:05:41.840
I do know that It is
like a nine hour video.
00:05:41.840 --> 00:05:43.250
You don't have to sit there for
nine hours.
00:05:43.250 --> 00:05:44.940
It's time lapsed, fortunately.
00:05:44.940 --> 00:05:48.560
But there's been just a lot of work
to optimize the way in which we
00:05:48.560 --> 00:05:50.210
update the screen,
00:05:50.210 --> 00:05:53.440
different encoding formats
that we support and stuff.
00:05:53.440 --> 00:05:57.510
There'd be more details than I think
either of us could maybe provide
00:05:57.510 --> 00:05:58.634
in the blog post.
00:05:58.634 --> 00:06:01.670
>> I know that there are changes
with like pausing Flash in
00:06:01.670 --> 00:06:05.550
the background and also
>> Like changes or improvements for
00:06:05.550 --> 00:06:06.250
a rendering engine,
00:06:06.250 --> 00:06:08.420
but aside from that I think
there are better [INAUDIBLE].
00:06:08.420 --> 00:06:10.500
>> So there's some tweaks
that you've done to make
00:06:10.500 --> 00:06:11.300
things a lot better.
00:06:11.300 --> 00:06:14.687
For those of us that wanna watch
all nine hours of Lord of the Rings
00:06:14.687 --> 00:06:15.200
in a row.
00:06:15.200 --> 00:06:16.860
>> [LAUGH]
>> So that's good to know.
00:06:16.860 --> 00:06:17.360
>> Yeah.
>> Okay.
00:06:17.360 --> 00:06:18.590
So we're talking about performance.
00:06:18.590 --> 00:06:20.990
Are there any other performance
things that are really cool that you
00:06:20.990 --> 00:06:23.130
wanna talk about or should we
move on to the next pillar?
00:06:23.130 --> 00:06:26.100
>> We actually do have a couple
other things that may not
00:06:26.100 --> 00:06:28.025
be immediately visible to
some people out there.
00:06:28.025 --> 00:06:30.130
Depending on the way which you
interact with the browser.
00:06:30.130 --> 00:06:33.230
In the past, the browser can hang,
and that type of stuff, and
00:06:33.230 --> 00:06:34.080
it's really annoying.
00:06:34.080 --> 00:06:37.100
Or maybe when a web page is loading,
it's frozen, you can't scroll up or
00:06:37.100 --> 00:06:38.340
down or anything.
00:06:38.340 --> 00:06:41.550
And because some of the recent
modifications made to the browser,
00:06:41.550 --> 00:06:43.110
we actually have
independent scrolling now.
00:06:43.110 --> 00:06:45.290
Even if the browser hangs for
whatever reason and
00:06:45.290 --> 00:06:46.510
you're reading an article.
00:06:46.510 --> 00:06:48.130
>> It doesn't stop you from
being able to scroll up and
00:06:48.130 --> 00:06:50.510
down on that page depending on
the way in which you do that.
00:06:50.510 --> 00:06:53.690
So if you're using track pad or your
finger you can still scroll up and
00:06:53.690 --> 00:06:56.630
down pages even if the browser
has hung for whatever reason.
00:06:56.630 --> 00:06:57.570
>> I see.
>> Or if the page is
00:06:57.570 --> 00:06:58.440
loading as well
>> Yeah.
00:06:58.440 --> 00:06:59.700
That's really cool.
00:06:59.700 --> 00:07:03.325
Traditionally the UI thread is
the one that takes the scrolling and
00:07:03.325 --> 00:07:05.045
you've sort of moved
that out of the way.
00:07:05.045 --> 00:07:07.340
>> Right.
>> So that now as things are loading
00:07:07.340 --> 00:07:10.300
and maybe they have a really
good while loop while true.
00:07:10.300 --> 00:07:12.260
You could still scroll
in that while true loop.
00:07:12.260 --> 00:07:14.060
>> Yeah, if they're loading
in a bunch of ads and
00:07:14.060 --> 00:07:16.010
stuff on the side you can
still be reading your article.
00:07:16.010 --> 00:07:16.990
You don't have to wait for
00:07:16.990 --> 00:07:19.760
everything below the fold
to load and stuff. It's-
00:07:19.760 --> 00:07:21.329
>> Which comes full circle cuz we
00:07:21.329 --> 00:07:23.660
have the ad block and [INAUDIBLE]
>> Yup, exactly.
00:07:23.660 --> 00:07:24.290
That's why we have it.
00:07:24.290 --> 00:07:26.090
>> So what is this showing us?
00:07:26.090 --> 00:07:29.550
>> So
we've actually compared Chrome and Edge
00:07:29.550 --> 00:07:31.580
>> On some industry benchmarks
00:07:31.580 --> 00:07:33.075
made by Google and Apple.
00:07:33.075 --> 00:07:33.650
>> Mm-hm.
>> And
00:07:33.650 --> 00:07:35.162
you can see that based on these,
00:07:35.162 --> 00:07:38.090
Edge is actually improving and
sort of better.
00:07:38.090 --> 00:07:39.380
>> So,
what are these actually measuring?
00:07:39.380 --> 00:07:41.000
>> I think it's at least for
00:07:41.000 --> 00:07:43.670
some of them that's operations per
second which is a common metric.
00:07:43.670 --> 00:07:44.700
>> Got it.
>> In the industry so
00:07:44.700 --> 00:07:47.970
it's either how quickly can you
do something and 10,000 times.
00:07:47.970 --> 00:07:49.700
Which is pretty trivial for
computers but
00:07:49.700 --> 00:07:51.010
it should be done quickly.
00:07:51.010 --> 00:07:54.350
And I like the fact that we are
testing for this because a majority
00:07:54.350 --> 00:07:57.031
of the applications now are mostly
client side JavaScript.
00:07:57.031 --> 00:07:57.670
>> Yeah.
>> And so
00:07:57.670 --> 00:08:01.990
the faster these things are you have
a really nice big angular aurelia or
00:08:01.990 --> 00:08:04.910
something else running you
want it to be fast and speedy.
00:08:04.910 --> 00:08:06.180
>> Yeah.
Not only are they client side but
00:08:06.180 --> 00:08:08.690
we're dealing with very,
very large datasets as well.
00:08:08.690 --> 00:08:11.090
As the web becomes more and
more complicated.
00:08:11.090 --> 00:08:11.780
>> That's amazing.
00:08:11.780 --> 00:08:13.060
All right, so performance.
00:08:13.060 --> 00:08:14.120
Any other performance things or
00:08:14.120 --> 00:08:16.220
should we move on
to the next pillar?
00:08:16.220 --> 00:08:17.110
>> I think the next pillar.
00:08:17.110 --> 00:08:19.170
>> All right.
What's the next pillar?
00:08:19.170 --> 00:08:22.530
>> I think it's actually also
bundled under fundamentals
00:08:22.530 --> 00:08:23.945
is compatibility.
00:08:23.945 --> 00:08:26.665
>> So essentially how
well Microsoft Edge, or
00:08:26.665 --> 00:08:28.395
how well popular websites and not so
00:08:28.395 --> 00:08:31.785
popular websites work on Microsoft
Edge compared to other browsers.
00:08:31.785 --> 00:08:33.235
And I also have a graph for that.
00:08:33.235 --> 00:08:34.306
>> Let's do it.
>> [LAUGH]
00:08:34.306 --> 00:08:36.018
>> And the numbers maybe make
00:08:36.018 --> 00:08:36.718
more sense.
00:08:36.718 --> 00:08:37.407
>> Yes.
00:08:37.407 --> 00:08:39.007
>> So this is the graph.
00:08:39.007 --> 00:08:42.467
>> Okay.
>> And basically it's showing how
00:08:42.467 --> 00:08:45.387
HTML5 test scores are improving for
00:08:45.387 --> 00:08:48.637
edge overtime with each release
that we've been having.
00:08:48.637 --> 00:08:50.960
And actually right now we've just
00:08:50.960 --> 00:08:53.500
overtaken Firefox with
the latest update.
00:08:53.500 --> 00:08:55.410
>> Fantastic.
So what is this ME?
00:08:55.410 --> 00:08:56.970
What is it that it's testing?
00:08:56.970 --> 00:08:58.070
And how do we compare?
00:08:58.070 --> 00:08:59.970
I know how we compare but
what is it testing?
00:08:59.970 --> 00:09:02.590
>> So what the HTML5 test is
actually testing is the browsers
00:09:02.590 --> 00:09:05.285
kind a declared support for
particular features.
00:09:05.285 --> 00:09:08.685
Language features and
HTML5, also APIs, and
00:09:08.685 --> 00:09:10.775
other features like web GL.
00:09:10.775 --> 00:09:13.015
Things that developers really
expect to be interactable between
00:09:13.015 --> 00:09:14.035
browsers today.
00:09:14.035 --> 00:09:15.806
And so
if you kind of look at the history,
00:09:15.806 --> 00:09:17.275
especially in contrast with IE.
00:09:17.275 --> 00:09:20.015
We've gotten to move a lot more
quickly in the edge days then we
00:09:20.015 --> 00:09:21.255
could just kind of historically.
00:09:21.255 --> 00:09:24.320
So we continue to see that
trend line move upward and
00:09:24.320 --> 00:09:26.120
we're excited to see
that momentum continue.
00:09:26.120 --> 00:09:29.500
>> Now this looks awesome
because it feels like if
00:09:29.500 --> 00:09:33.340
you sort of extrapolate our
chart is going pretty high up.
00:09:33.340 --> 00:09:34.330
>> Right.
00:09:34.330 --> 00:09:36.649
>> That's awesome so
compatibility wonderful what else?
00:09:39.260 --> 00:09:43.122
So we did extensions
we did accessibility.
00:09:43.122 --> 00:09:44.610
>> Accessibility.
00:09:44.610 --> 00:09:46.560
>> We did a little
bit of performance.
00:09:46.560 --> 00:09:48.260
What else is in there?
00:09:48.260 --> 00:09:52.300
>> So there's also a section called
building for the future of the web.
00:09:52.300 --> 00:09:56.090
And that basically means that we're
trying to implement things that
00:09:56.090 --> 00:09:58.660
web standards and
other browsers are putting in.
00:09:58.660 --> 00:10:02.280
So things like EC 20
00:10:02.280 --> 00:10:03.250
>> Yes, 2015
>> Yeah.
00:10:03.250 --> 00:10:05.931
>> Support for basically the next
generation of Java Script that's
00:10:05.931 --> 00:10:08.040
coming out of
the Eckman International Group.
00:10:08.040 --> 00:10:09.020
>> I see.
So instead of
00:10:09.020 --> 00:10:14.010
me having to sort of down compile
into whatever bottom level thing.
00:10:14.010 --> 00:10:17.570
You can actually write ECMA 2015 or
16?
00:10:17.570 --> 00:10:19.726
>> 2015 right now.
>> 2015 right now directly and
00:10:19.726 --> 00:10:22.450
it will be able to parse it and
read it and do it.
00:10:22.450 --> 00:10:25.030
>> That's exactly correct, and one
of the great things is that Edge was
00:10:25.030 --> 00:10:27.710
one of the first browsers to really
have this kind of booming support
00:10:27.710 --> 00:10:29.920
for ES2015 kind of
natively built into it.
00:10:29.920 --> 00:10:32.640
And so you wouldn't have to use
Babel or TypeScript or anything.
00:10:32.640 --> 00:10:33.680
Type script, no hate there.
00:10:33.680 --> 00:10:35.500
But you wouldn't have to use those.
00:10:35.500 --> 00:10:37.290
You could actually just
open up your console,
00:10:37.290 --> 00:10:39.520
start to use arrow functions,
start to use classes and
00:10:39.520 --> 00:10:41.640
that type of stuff just
right in the browser.
00:10:41.640 --> 00:10:44.548
And so it's delivered at people
usually experience when they're on
00:10:44.548 --> 00:10:46.130
Node or something like that.
00:10:46.130 --> 00:10:47.690
They just get to use
modern JavaScript.
00:10:47.690 --> 00:10:49.660
They don't have to
worry about different
00:10:49.660 --> 00:10:51.360
degrees of support on the web.
00:10:51.360 --> 00:10:53.490
And so we actually have that now.
00:10:53.490 --> 00:10:56.590
The web is still probably gonna have
to transpile down to, you know,
00:10:56.590 --> 00:10:59.756
a simpler version of JavaScript just
because not everyone is on Edge.
00:10:59.756 --> 00:11:02.600
And we'll continue to improve
that as we move forward.
00:11:02.600 --> 00:11:03.180
>> Fantastic.
So
00:11:03.180 --> 00:11:06.480
what other things are you doing to
sort of future-proof people's apps?
00:11:06.480 --> 00:11:09.380
So in the anniversary update,
we've added a few more features that
00:11:09.380 --> 00:11:12.130
allow sites to have a more
integrated feel with Windows 10.
00:11:12.130 --> 00:11:16.070
One example of this is web
notifications where sites like Slack
00:11:16.070 --> 00:11:19.320
or Facebook can push
notifications to your desktop,
00:11:19.320 --> 00:11:22.780
even though the browser tab can be
minimized or in the background.
00:11:22.780 --> 00:11:26.300
Another example would be web
authentication where you can log
00:11:26.300 --> 00:11:30.120
into websites using a camera or
your fingerprint scanner.
00:11:30.120 --> 00:11:31.660
So in the long term
we're also working on
00:11:31.660 --> 00:11:34.700
things like service worker which
we're really excited about and
00:11:34.700 --> 00:11:36.650
everyone else is very excited about.
00:11:36.650 --> 00:11:39.420
As well as a family of features
that make up progressive web
00:11:39.420 --> 00:11:41.910
apps which sort of allow
you to have a better
00:11:41.910 --> 00:11:44.920
native feeling offline
experience with sites.
00:11:44.920 --> 00:11:47.680
>> For those that don't know what
service worker is, can you describe
00:11:47.680 --> 00:11:50.572
this in a thumbnail sketch what
that is and why it's important?
00:11:50.572 --> 00:11:52.970
>> Yeah, it's whenever you come to
a website you'll be able to register
00:11:52.970 --> 00:11:54.890
a service worker, and
this is basically a way for
00:11:54.890 --> 00:11:59.780
the website to start the handle all
the requests for the sub resources.
00:11:59.780 --> 00:12:02.790
Whenever those go out, typically
they go out to the Facebook server
00:12:02.790 --> 00:12:05.020
or to Imgur, some thing like that.
00:12:05.020 --> 00:12:07.938
But in this case, your service
worker would actually be able to
00:12:07.938 --> 00:12:10.085
intercept those and
just return a cache copy or
00:12:10.085 --> 00:12:12.469
make a decision to go out and
get a new updated copy.
00:12:12.469 --> 00:12:15.513
And so, this gives you that full
offline rich experience that people
00:12:15.513 --> 00:12:17.280
are used to with
native applications.
00:12:17.280 --> 00:12:20.359
>> Awesome and with client side
applications, you can make really
00:12:20.359 --> 00:12:23.755
good decisions about what I should
pull and what you already have.
00:12:23.755 --> 00:12:24.915
>> Right.
>> And maybe the request you're
00:12:24.915 --> 00:12:27.965
making as a repeat I can sort of
use the data that's in the cache?
00:12:27.965 --> 00:12:29.515
>> Right.
>> That's amazing.
00:12:29.515 --> 00:12:30.225
All right so what else?
00:12:30.225 --> 00:12:31.615
I think we talked about
four is there more?
00:12:31.615 --> 00:12:34.830
>> Four yes the final one is that,
basically
00:12:34.830 --> 00:12:38.820
just making sure that we're open and
communicating with the ecosystem.
00:12:38.820 --> 00:12:41.010
And that's pretty much
what our team does and
00:12:41.010 --> 00:12:43.370
also why I'm really
enjoying my internship.
00:12:43.370 --> 00:12:46.640
And so the whole point is that
you can, if you have any issues,
00:12:46.640 --> 00:12:51.097
you can talk to us on Twitter
@msedgedev MS Edge dev.
00:12:51.097 --> 00:12:54.640
>> [LAUGH]
>> Or file a bug on our website, and
00:12:54.640 --> 00:12:56.490
we can all go through that and
00:12:56.490 --> 00:12:59.040
you can basically see
what people have said.
00:12:59.040 --> 00:12:59.840
And you can upvote it and
00:12:59.840 --> 00:13:03.030
you can discuss it and you can see
whether our devs are working on it.
00:13:03.030 --> 00:13:06.400
>> So
when we talk about open source and
00:13:06.400 --> 00:13:10.170
you're interested in people
giving you this feedback.
00:13:10.170 --> 00:13:11.430
Where does this feedback go?
00:13:11.430 --> 00:13:14.230
Are people just putting it
into some user voice thing and
00:13:14.230 --> 00:13:15.780
then it's going off
into the darkness?
00:13:15.780 --> 00:13:17.465
Or how does it work for your team?
00:13:17.465 --> 00:13:19.345
>> Historically we used
to have the connect site.
00:13:19.345 --> 00:13:21.575
So connect at Microsoft.com I
think it was.
00:13:21.575 --> 00:13:22.805
And it was a really great site.
00:13:22.805 --> 00:13:24.075
People could submit bugs and
stuff, but
00:13:24.075 --> 00:13:26.885
it was actually separate from
where we tracked our bugs.
00:13:26.885 --> 00:13:29.035
And so there would this interim
process that would pick
00:13:29.035 --> 00:13:32.283
up some stuff from connect and drop
it into where we actually worked.
00:13:32.283 --> 00:13:35.955
We launched
bugs.microsoftedge.com which
00:13:35.955 --> 00:13:39.625
actually puts the bugs directly into
the area that we're working from.
00:13:39.625 --> 00:13:43.048
So whenever a bug is assigned, you
see the developer's name on there.
00:13:43.048 --> 00:13:45.390
Whenever the status
of a bug changes,
00:13:45.390 --> 00:13:47.305
you see that status in real time.
00:13:47.305 --> 00:13:50.610
We've removed that
latency all together.
00:13:50.610 --> 00:13:53.190
So bugs@microsoftedge.com
is really easy to use.
00:13:53.190 --> 00:13:55.190
You don't have to sign
in to see the bugs.
00:13:55.190 --> 00:13:57.590
You can actually just go there.
00:13:57.590 --> 00:14:00.930
If you can repro a bug you
can click me too as well.
00:14:00.930 --> 00:14:04.530
We've even experimented with ways
to reduce the friction even more.
00:14:04.530 --> 00:14:07.421
And so if you're on Twitter and
you have a reduction,
00:14:07.421 --> 00:14:10.375
you can Tweet a title,
a link to your reduction which is
00:14:10.375 --> 00:14:13.586
just a way to repro the bug with
as few bytes as possible, and
00:14:13.586 --> 00:14:17.400
add the hashtag #edgebug And we'll
actual file a bug on your behalf.
00:14:17.400 --> 00:14:18.270
>> Holy cow.
00:14:18.270 --> 00:14:20.050
>> And so,
>> And it goes into your database
00:14:20.050 --> 00:14:20.628
>> It goes into it.
00:14:20.628 --> 00:14:21.310
>> It goes into your system.
00:14:21.310 --> 00:14:21.860
>> Right.
>> Yeah,
00:14:21.860 --> 00:14:23.250
because I know that
when people like,
00:14:23.250 --> 00:14:26.750
send me an email with a problem I'm
like yeah, I should look at that.
00:14:26.750 --> 00:14:27.700
But when it's actually in
00:14:27.700 --> 00:14:28.560
the system,
>> Yeah.
00:14:28.560 --> 00:14:29.780
>> When I log in and I'm like, aw,
00:14:29.780 --> 00:14:32.770
okay this is what I've got to work
on today, that's very different.
00:14:32.770 --> 00:14:33.830
>> There's no excuse at that point.
00:14:33.830 --> 00:14:34.590
>> Yeah, no excuse.
00:14:34.590 --> 00:14:36.250
Well this is awesome.
00:14:36.250 --> 00:14:38.120
Where can people go to find
out more about all of these
00:14:38.120 --> 00:14:40.110
great things that
you're talking about?
00:14:40.110 --> 00:14:43.940
>> So our main portal is
dev.microsoftedge.com.
00:14:43.940 --> 00:14:48.470
But I think if you're on Twitter, we
all have links to our main websites,
00:14:48.470 --> 00:14:53.730
our status platforms for
how far we are going in terms of
00:14:53.730 --> 00:14:56.160
implementing some
of service workers.
00:14:56.160 --> 00:14:57.845
Or just the normal Bing search.
00:14:57.845 --> 00:14:59.250
[LAUGH]
>> Fantastic.
00:14:59.250 --> 00:15:01.709
So to finish up, any final words for
those that are watching?
00:15:02.960 --> 00:15:04.199
We love you.
>> I'm nervous.
00:15:04.199 --> 00:15:05.070
>> [LAUGH] Nice.
00:15:05.070 --> 00:15:07.370
Well this has been so awesome.
00:15:07.370 --> 00:15:09.060
Thanks so much for
spending some time with us.
00:15:09.060 --> 00:15:10.670
>> Thank you.
>> We've been learning about the new
00:15:10.670 --> 00:15:11.680
Edge release.
00:15:11.680 --> 00:15:13.480
Great stuff that you
guys are talking about.
00:15:13.480 --> 00:15:15.920
Please check out all of
the resources below to learn more.
00:15:15.920 --> 00:15:17.510
My name is Seth Juarez, Channel 9.
00:15:17.510 --> 00:15:18.080
Thanks for watching.
00:15:18.080 --> 00:15:18.680
We'll see you next time.