2,003 karma · joined July 18, 2011
Those threads are a good example of what's wrong in TC39. A simple AbortSignal could have been added, but by the time it's reconciled with SES, large speculative APIs like Governers, or the original attempt to add a parallel throw mechanism just for cancellation, nothing actually gets done.
It's been 10 years since CancelToken was first discussed and we're still debating it.
Also I love rats and totally agree they're tough pets because they don't live long enough. We had many of them growing up and spent a fortune removing tumors.
Right now Chrome is much more focused on AI related APIs (sigh) and not stuff like FontMetrics.
https://drafts.css-houdini.org/font-metrics-api-1/
RIP eae@.
https://github.com/tc39/proposal-module-declarations
Unfortunately the JS standards folks have refused so far to make this situation better.
Ex. it should just be `new Worker(module { ... })`.
It's not just the menu bar icon (which can definitely be spoofed), but an on screen dot where the system is controlling pixels directly bypassing any OS level drawing on the screen.
Related: https://www.reddit.com/r/iphone/comments/1in0681/iphone_16_m...
The DOM is not a static interface, it changes both across browsers based on implemention status and also based on features enabled on a per page load basis.
The multi browser ecosystem also mainly works because of polyfills.
It's not clear how to polyfill random methods on a WIT interface or how to detect at runtime which methods exist.
OTOH the JS bridge layer we use today means you can load JS side polyfills and get wasm that's portable across browsers with no modifications. There's more to the ecosystem than just performance.
Building a system that's fast on day one will not usually be rewarded as well as building a slow system and making it 80% faster.
Fwiw the original Streams API could have been simpler even without async iterators.
interface Stream<T> {
// Return false from the callback to stop early.
// Result is if the stream was completed.
forEach(callback: (chunk: T) => Promise<boolean | undefined>): Promise<boolean>
}
Similarly adding a recycleBuffer(chunk) method would have gone a long way towards BYOB without all the ceremony.If we're optimizing allocations we can also avoid all the {done,value} records and return a semaphore value for the end in the proposed API.
(Web) API design is really difficult and without a voice in the room pushing really hard on ergonomics and simplicity it's easy to solve all the use cases but end up with lots of awkward corners and costs later.
If you look at DOM benchmarks it's extremely fast. Slow web pages come from slow layers on top.
Perhaps an overly aggressive attempt to block bots.
Large tech companies have plenty of engineers to fix bugs, but most of them are on projects trying to 10X things instead of paying down debt.
Apple used to be unique in it's immunity to it, they even shipped an OS update claiming it was only big fixes and not features which is unthinkable these days. Over time there's much less focus on polish from them though.
Allocators are an interesting place to focus on for security. Chris did amazing work there for Blink that eventually rolled out to all of Chromium. The docs are a fun read.
https://blog.chromium.org/2021/04/efficient-and-safe-allocat...
https://chromium.googlesource.com/chromium/src/+/master/base...
Relevant to that comic specifically: https://www.reddit.com/r/xkcd/comments/mi725t/yeardate_a_com...