-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
27 changed files
with
95 additions
and
97 deletions.
There are no files selected for viewing
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
--- | ||
layout: talk | ||
title: "Blitz: a truly modular, hackable web renderer" | ||
authors: "Nico Burns" | ||
date: "2024-06-03T16:30:00" | ||
dateiso: "2024-06-03T14:30:00" | ||
imgsrc: "/img/talks/nico.webp" | ||
imgalt: "Nico Burns" | ||
--- | ||
|
||
Blitz is new web rendering engine that doubles down on Servo's promise of modularity and hackability by combining a mix of Servo, Rust UI ecosystem, and bespoke components. It also (currently) eschews JavaScript scripting in favour of a Rust scripting API that can be driven directly by Dioxus or other Rust state management / reactivity frameworks. | ||
|
||
This talk covers how Blitz's approach differs to a traditional web engine, use cases, challenges, progress, and future plans. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,15 +1,12 @@ | ||
--- | ||
layout: talk | ||
title: "Fallback Tab Dragging for Ozone/Wayland" | ||
title: "The journey towards stabilizing Chromium's Wayland support" | ||
authors: "Max Ihlenfeldt" | ||
date: "2023-06-05T12:00:00" | ||
dateiso: "2023-06-05T10:00:00" | ||
date: "2024-06-03T12:30:00" | ||
dateiso: "2024-06-03T10:30:00" | ||
imgsrc: "/img/talks/max.webp" | ||
imgalt: "Max Ihlenfeldt" | ||
cancelled: true | ||
--- | ||
|
||
Dragging tabs out of and back into Chromium windows doesn't work on Wayland as on other platforms due to protocol restrictions. There already is a protocol extension that makes regular tab dragging possible, but it requires support from the Wayland compositor. Until all major compositors implement this extension, we need some form of fallback tab dragging that always works. | ||
|
||
Unfortunately, to be able to run automated tests against this new tab dragging implementation, we need to fix some long-standing issues with how these tests are run on Wayland - time for another new protocol extension! | ||
Chromium has had experimental support for Wayland for some time, and is moving towards stabilizing it. Let's take a look at how we got to where we are now, and at what's still missing before it can be stabilized. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
--- | ||
layout: talk | ||
title: "History of WebGPU in Deno" | ||
authors: "Leo Kettmeir" | ||
date: "2024-06-03T16:00:00" | ||
dateiso: "2024-06-03T14:00:00" | ||
imgsrc: "/img/talks/leo.webp" | ||
imgalt: "Leo Kettmeir" | ||
--- | ||
|
||
Deno has supported WebGPU since early 2021, however, there were several challenges in providing a performant WebGPU implementation. This talk will cover the series of events and changes required to achieve support. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
--- | ||
layout: talk | ||
title: "Firefox Wayland post mortem" | ||
authors: "Martin Stransky" | ||
date: "2024-06-03T12:00:00" | ||
dateiso: "2024-06-03T10:00:00" | ||
imgsrc: "/img/talks/martin.webp" | ||
imgalt: "Martin Stransky" | ||
--- | ||
|
||
Mozilla switched to Wayland by default recently. Let's make some retrospective what are advantages/disadvantages of such decision and how it was received by users. Highlight what's working fine and where we still have issues. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
--- | ||
layout: talk | ||
title: "Sustainable Futures: Funding the Web Ecosystem " | ||
authors: "Stephanie Stimac" | ||
date: "2024-06-03T15:30:00" | ||
dateiso: "2024-06-03T13:30:00" | ||
imgsrc: "/img/talks/stephanie.webp" | ||
imgalt: "Stephanie Stimac" | ||
--- | ||
|
||
The web is a vital source of the world’s infrastructure and has shaped the way we work and live in the modern world. Surely such an integral piece of our day-to-day life is being built and maintained in a way that ensures it will last? | ||
|
||
Unfortunately this isn't the case. The current system funding access to the web is fragile, fractured and unsustainable. In this talk, I’ll give an overview of the current state of things, how we currently fund the web, why this is a problem, and possible ways to fix this so that access to information remains stable and sustainable for future generations to come. |
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
--- | ||
layout: talk | ||
title: "LBSE - Status of the Layer-Based SVG Engine" | ||
authors: "Nikolas Zimmermann" | ||
date: "2024-06-03T17:00:00" | ||
dateiso: "2024-06-03T15:00:00" | ||
imgsrc: "/img/talks/nikolas.webp" | ||
imgalt: "Nikolas Zimmermann" | ||
--- | ||
|
||
LSBE is a new SVG engine for the WebKit project that aims to unify the HTML and SVG rendering pipelines. On this talk we'll review the activities around LBSE in the past year plus an outlook to the next months. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
--- | ||
layout: talk | ||
title: "Nova JavaScript Engine - Exploring a Data-Oriented Engine Design" | ||
authors: "Aapo Alasuutari" | ||
date: "2024-06-03T13:00:00" | ||
dateiso: "2024-06-03T11:00:00" | ||
imgsrc: "/img/talks/aapo.webp" | ||
imgalt: "Aapo Alasuutari" | ||
--- | ||
|
||
In this talk we explore the benefits and drawbacks of writing a basic JavaScript engine in Rust using a data-oriented approach. This draws a stark contrast with the naturally object-oriented design of the ECMAScript specification and how most mainstream engines are built. | ||
|
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
--- | ||
layout: talk | ||
title: "The Future of Source Maps" | ||
authors: "Jonathan Kuperman" | ||
date: "2024-06-03T11:00:00" | ||
dateiso: "2024-06-03T09:00:00" | ||
imgsrc: "/img/talks/jonathan.webp" | ||
imgalt: "Jonathan Kuperman" | ||
--- | ||
|
||
Originally developed in 2009, source maps have become ubiquitous, consumed by all major browsers and generated by every bundler in the JavaScript ecosystem. While the support for them is widespread, the specification itself has remained largely unchanged since 2009. Because of this, feature development has been very difficult to navigate. Some browsers have added their own functionality, but without the ability to influence the tools generating source maps, support is limited. | ||
|
||
In 2023, we formed a group specifically dedicated to the completion and modernization of source maps. We presented to TC39 in July and became an official TC39 Task Group. Since then, we've been hard at work rounding out the current specification, looking forward to new features and making sure everyone agrees on the existing features. This talk will be focused on the new and exciting features we’re bringing to the specification. We’re actively working on Debug IDs for easier identification in error monitoring tools, Scopes for improved and consistent variable name and scope information in debugging tools and Range Mappings for helping debuggers find more accurate places in source code. | ||
|
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters