JS engine hacking: Function.prototype.bind() bug fixes & spec compliance

preview_player
Показать описание
Follow along as I fix a bug in the implementation of bound functions in LibJS, and then another. Yay for more spec compliance! :^)

  1. Linus Groh
Рекомендации по теме
JS engine hacking: 0:42:49

JS engine hacking: Function.prototype.bind() bug fixes & spec compliance

The Origin of 0:44:20

The Origin of Array [@@species]: How Standards Drive Bugs in Script Engines

Browser hacking: Fixing 0:34:22

Browser hacking: Fixing error propagation in LibWeb

How to debug 0:11:35

How to debug an Ember.js application

Compiler Compiler - 0:58:38

Compiler Compiler - Part 1: Fixing a bug

4. Self-hosted JS 0:35:59

4. Self-hosted JS - Andy Wingo

Compiler Compiler - 1:08:21

Compiler Compiler - Part 3: Debugging SpiderMonkey continued

10 security vulnerabilities 0:40:38

10 security vulnerabilities every JavaScript developer should know

Getting Over It 0:01:45

Getting Over It Developer Reacts to 1 Minute 24 Second Speedrun

Implementing array methods 1:02:16

Implementing array methods from scratch - indexOf, forEach and map

Deno JS Kills 0:05:08

Deno JS Kills Node JS?

Why is JavaScript 0:04:47

Why is JavaScript not used for classical application development (compiled software)?

JS Suicide: Using 0:42:57

JS Suicide: Using JavaScript Security Features to Kill JS Security by Ahamed Nafeez

A Walk Through 0:53:14

A Walk Through Electron's Internals - Brendan Forster

High Speed History 0:17:42

High Speed History of JavaScript

Headless Browser Hide 0:44:25

Headless Browser Hide and Seek - OWASP AppSecUSA 2014

Debugging at Full 0:39:17

Debugging at Full Speed with Michael Van De Vanter

Advanced JavaScript Techniques: 1:00:53

Advanced JavaScript Techniques: Closures, Prototypes, Async/Await | Live Q&A with Senior Develop...

Simple Floppy Robin 0:23:07

Simple Floppy Robin Cocos2d Javascript Lite #1 Getting Started

What it takes 0:36:19

What it takes to be good at bug bounty hunting at DefCamp 2021

Browser hacking: Let's 0:41:02

Browser hacking: Let's bring XMLHttpRequest closer to spec!

Reacting to changes 0:14:18

Reacting to changes with Firebase, and how to interop

Node Intro 0:25:20

Node Intro

Some reason why 0:02:40

Some reason why I'm looking forward to EBF 4

Комментарии
Автор

Would appreciate the code tour! It would make new contributors more confident to get started. Thanks Linus.

phsilvabr
Автор

Very great work Linus! I must admit the “uncommitted changes” message in your editor would seriously distract me. I always disable the SCM integration plugins. Impressive that you are able to not be distracted by it :^)

psynetFM
Автор

Gosh! the current spec is a _loooong_ way from Javascript 1.5 :)

I remember waking up at 4:30am after I ran a JS Syntax check on some code in a _dream_ ! And going to work to impliment it. Yes I worked so closely with cross-browser cross-platform JS in 2000 that I could Parse generic Javascript while I slept :)

There is no way I could fit the current JS Parser Spec in my sub-conscious nowadays :)

paulwratt
Автор

Who knew that all it took to get me interested in Javascript is implementing it in C++?

Michael_
Автор

41:52 "1 TODO? Commit. Wait what..."

devashishjaiswal
Автор

Seeing you guys focus on spec-compliance, rather than performance, and "cross-referencing" it with how slow some parts of LibWeb is (i.e., the time it takes to Discord to load, as Andreas has show), makes me wonder, is it possible to have both right from the start? A spec-compliant code that's also performant?

joao-pedro-braz
Автор

Oh my gosh how many years has --include-untracked been a thing for git stash? My whole life has been a lie.

anthonutty
join shbcf.ru