The Future of Loading on the Web (Chrome Dev Summit 2017)

  Рет қаралды 15,051

Chrome for Developers

Chrome for Developers

Күн бұрын

Пікірлер: 10
@jeffreydwalter
@jeffreydwalter 7 жыл бұрын
Why the weird naming conventions for the priority stuff? Instead of critical and late, why not highest, high, low, lowest, etc.? Also, why "group" instead of "priority" for the html attribute?
@toooes
@toooes 7 жыл бұрын
I wonder too. I think critical and late are explicit terms whereas high/low require context to be meaningful. Edit: From the proposal: We will define a new standard importance attribute that will map to current browser priorities: critical, high, medium, low, unimportant
@srcspider
@srcspider 7 жыл бұрын
Props for admitting to the fact that even unminified bundle (with none of the usual special sauce like code splitting) still beats loading granually but you've still omitted a lot of the problems with getting this "magic" to work. For the client to request X, Y, Z from the server the client needs to know the dependency graph (not knowing works, but is slowest since you requerst / parse / excute to find out whats next), and how exactly is the client to know this exactly? If we added a minifest file (ignoring the complexity from having one and the complexity from browsers and servers understanding them (since servers have to bundle everything for you) you have the issue that you're loading one file, then can you start loading. And even with a manifest you're still stuck in the mud when it comes to the "promise" of cherry picking and tree shacking.... that just can't happen with out having dedicated monolithic and inflexible architecture on the server that parses any and all javascript. Let's not even get into "how does the client know what files have actually changed?" with out spamming the server. A bundle is just one check, how much does making 10,000 checks cost? The "problem" you're trying to solve is a real one, however you can just as easily solve it but configuring webpack to split your stuff into more bundles. Code splitting to essentials per page is also already minimal enough that it doesn't really matter IMO (or at least you should in theory be able to get it there in 99% of real world use cases).
@gnorberg
@gnorberg 7 жыл бұрын
Fantastic presentation. Excited for the future of the web!
@DenisTRUFFAUT
@DenisTRUFFAUT 7 жыл бұрын
Great video !
@filemot25
@filemot25 7 жыл бұрын
Really exciting news
@channel-vt3ib
@channel-vt3ib 7 жыл бұрын
Hello world,these are my latest development on chrome.
@rajashahja8975
@rajashahja8975 6 жыл бұрын
he dont know about web assembly ;-)
@DylanIsSoSpooky
@DylanIsSoSpooky 6 жыл бұрын
Lol I love you google
@DylanIsSoSpooky
@DylanIsSoSpooky 6 жыл бұрын
Wait this chrome
V8 Today and in the Future (Chrome Dev Summit 2017)
24:13
Chrome for Developers
Рет қаралды 9 М.
lit-HTML (Chrome Dev Summit 2017)
29:44
Chrome for Developers
Рет қаралды 47 М.
路飞做的坏事被拆穿了 #路飞#海贼王
00:41
路飞与唐舞桐
Рет қаралды 26 МЛН
The evil clown plays a prank on the angel
00:39
超人夫妇
Рет қаралды 46 МЛН
Instant Loading: Building offline-first Progressive Web Apps - Google I/O 2016
46:14
Workbox: Flexible PWA Libraries (Chrome Dev Summit 2017)
25:18
Chrome for Developers
Рет қаралды 40 М.
Speed Essentials: Key Techniques for Fast Websites (Chrome Dev Summit 2018)
29:21
Real World WebAssembly (Chrome Dev Summit 2017)
27:54
Chrome for Developers
Рет қаралды 18 М.
Learn Web Development And ACTUALLY Get A Job | Ultimate Guide
1:33:52
James Cross
Рет қаралды 1,5 МЛН
The Web for the Entire World (Chrome Dev Summit 2017)
27:30
Chrome for Developers
Рет қаралды 4,8 М.
Frameworks Panel (Chrome Dev Summit 2017)
36:12
Chrome for Developers
Рет қаралды 12 М.
WordPress + PWAs = 💖 (Chrome Dev Summit 2017)
30:03
Chrome for Developers
Рет қаралды 36 М.
Fast By Default: Modern Loading Best Practices (Chrome Dev Summit 2017)
34:08
Chrome for Developers
Рет қаралды 49 М.
路飞做的坏事被拆穿了 #路飞#海贼王
00:41
路飞与唐舞桐
Рет қаралды 26 МЛН