Name: Web標準へのヒッチハイカーガイド // ドミニク・ファロリーノ // CascadiaJS 2018 (Hitchhiker's Guide to Web Standards // Dominic Farolino // CascadiaJS 2018)
Uploaded: 2021-01-14T10:51:30.000Z
Duration: 24 min 10 s
Description: VoiceTubeの動画で発音を聞きながら英語表現を覚えよう！学べる英語：

未来進行形

Today we will be talking about web standards.

This is my first time using a clicker so bear with me.

I am a senior at the University of Cincinnati.

I will doing a final internship in Japan and work on Chromium committer.

You can follow me on Twitter, check out my work on GitHub and feel free to e-mail me

any time after the talk if you have questions about the getting involved and the browser

I have three overarching goals I wanted to reach.

The first is provide a background and history into web standards and some of the organizations

that are responsible for their governance.

This could be its own talk but I will give a brief history on this.

Next I will talk about as a web developer how you can make use of a web standard.

A lot of us Google an API and figure out how it works but I want to talk about the technical

bits of the web standards and show how to make use of them and navigate that space.

Finally, I want to talk about how to get involved and share a bit about my own story of getting

involved with standards and working on the platform and, hopefully, encourage some of

I would like to propose the idea we need a definition of a standard.

This largely depends on context if we define a new word.

I would like to propose my own definition for the purpose of this talk.

A document specifying observable effects of tech with multiple independent implementations.

We care about the observable effects of technology.

The last part multiple independent implementations -- I think this one is really important.

It is far from a new concept in technology.

You know, we have seen this with Unix operating system.

You can have your own and you get one and everybody has their own separate distribution

What I really care about is can I write application that works once everywhere and no matter what

operating system I am using that is in the Linux family of OSs it will work uniformly.

To make that environment conducive, we have a set of classic standards.

The same thing goes for web tech and this is primarily what I will talk about today.

I happen to know for a fact you can't go to the store and buy one HTTP.

It is just an idea and something you implement to make it compatible with other versions.

We can run JavaScript in a bunch of places.

I can run it in Chrome, Edge, Node and all kinds of different places.

The same goes for the star of the talk today which is web platform APIs.

I am no longer a Unix app developer but I am a web developer and I need to know the

same extensions will be there in Chrome and Firefox and more importantly work

Keynote is cool and has a bunch of symbols you can use.

Let's talk about where web APIs come from.

We want to know where this stuff comes from and how we can make more of them.

I think the logical answer is probably JavaScript.

Here is an example of a snapshot of the Chrome dev tools.

I can fetch super prominent sites on the internet and set timeout and stuff like that.

This stuff is part of the language but what is the language?

We know the big story of JavaScript being created in 10 days but it is a general purpose

programming language created for the purposes of the web.

It was plopped into an escape 2.0 and made it a candidate for standardization because

there was going to be multiple implementations of it.

We needed a group to come out and pick out this task of standardizing.

They have had success with the various engines.

There is a bunch of same implementations for this.

It is big and hard to read and on GitHub under the TC39 page.

When we write a standard, how does it work?

We are predicting language so have to make it general.

We need a really strict separation of concern.

We need to be dealing with the language, syntax and semantics.

As a true scripting language, it should be able to be plopped into any hosting environment

but the language shouldn't have to know anything explicit about that environment.

We are used to using language in the browser and used to web APIs but the language doesn't

They are effective mixed in and baked into the browsers and browsers can support a version

of this script and a bunch of web APIs that tag alongside this version that interplay

We have that coined -- TC39 is responsible for standardizing the JavaScript we know but

who is responsible for standardizing the web APIs?

Two big groups are primary responsible right now.

You have probably seen one of these logos.

We have the W3C and the WHATWG which stands for What Working Group and is the one I will

The WHATWG stands for a long stream of text.

It was formed from branching off from the W3C.

They have an HTML language and it is the kitchen sink of the web platform.

They specify the interface we use to talk to the web and a lot of really cool things

But how are these things actually written?

If we are going to write a browser, we want to write ES, we start with this.

There is a lot of stuff and a bunch of exposed objects we get for free in JavaScript.

The array constructor and data array objects and weak maps and data structures that are

We want our browser to be a little more powerful and have it be me, the DOM.

We can give it a query selector language and extend the language more.

The document is getting bigger but it is getting more powerful.

We would love to contact the network as well so we will give it network primitives like

It would be really cool if we could do ourselves and give it a console method as well.

This is one way to write it it keep appending the text.

字幕リスト動画再生

Web標準へのヒッチハイカーガイド // ドミニク・ファロリーノ // CascadiaJS 2018 (Hitchhiker's Guide to Web Standards // Dominic Farolino // CascadiaJS 2018)

stuff

bunch

multiple

basically