jaffathecake

5 ms·

61.
by jaffathecake 6mo ago
The Chrome model requires either "16 GB of RAM or more and 4 CPU cores or more" or "Strictly more than 4 GB of VRAM", and "22 GB of free space" (it uses around 4.4GB but it doesn't want to use the remainin
62.
by jaffathecake 6mo ago
The rate of model development is an issue here. Once there are many cross-origin models, it becomes a fingerprinting vector. Also even the small models are many GBs.
63.
Mozilla's opposition to Chrome's Prompt API(github.com)
663 points by jaffathecake 6mo ago|231 comments
64.
by jaffathecake 7mo ago
A lot. My scores: - 0.0028 on my MacBook pro screen - 0.0045 on my Dell monitor - 0.0033 on my Pixel 10 pro And those scores are pretty consistent.
65.
by jaffathecake 7mo ago
The associated deep-dive article is great https://www.keithcirkel.co.uk/too-much-color/
66.
by jaffathecake 8mo ago
fwiw, if you serve your page with: Content-Security-Policy: require-trusted-types-for 'script' …then it blocks you from passing regular strings to the methods that don't sanitize.
67.
by jaffathecake 11mo ago
Fwiw, JPEG XL takes around 2.5x the time to decode as an equivalent AVIF, and has worse compression https://jakearchibald.com/2025/present-and-future-of-progres...
68.
Importing vs. Fetching JSON in JavaScript(jakearchibald.com)
5 points by jaffathecake 1y ago|0 comments
69.
by jaffathecake 1y ago
I know this isn't quite what you mean, but when you first hit the page, the list is in a random order, but it's then stable across reloads. I considered the 'vs' approach, but I worried that there might be a lot of itera
70.
by jaffathecake 1y ago
Author of the app here. This was quickly thrown together, and something we'd like to improve on next year. Any & all feedback is welcome. We've already been looking at the results, and it has influenced the direction of multip
71.
by jaffathecake 1y ago
Author of the app here. This was quickly thrown together, and something we'd like to improve on next year. Any & all feedback is welcome.
72.
by jaffathecake 1y ago
Browsers don't want to add new ways of running script. That said, I wonder if `<?xml-stylesheet type="text/javascript" href="script.js"?>` could work. It's kinda weird, but `xml-stylesheet` can alrea
73.
by jaffathecake 1y ago
Alpha channel support in x265 is very interesting, as this was only previously possible with paid-for Apple software (and the resulting file sizes were high). Some details from when I last looked at it https://jakearchibald.com&#
74.
by jaffathecake 1y ago
That document order thing doesn't sound right to me. Here's a demo where the popover appears before the anchor https://codepen.io/jaffathecake/pen/MYargba?editors=1100
75.
by jaffathecake 1y ago
`position-anchor` is a high-level simple way of doing it, and it comes with the restrictions you mention. However, the `anchor()` function, which is also mentioned in the article, gives you the kind of flexibility you want. https:/&#x
76.
by jaffathecake 1y ago
I guess you're being downvoted as a general nay-sayer, but you're right. I tried this feature last month and a bunch of browser bugs and design issues got in the way. I reported them, and they're being worked on https:/
77.
by jaffathecake 1y ago
> odd that the original post didnt have it either Totally honestly, it was a lot of work, I got bored, and it was diminishing returns for the later parts.
78.
by jaffathecake 1y ago
I linked to it without realising that. I didn't know Aaron personally, but I remember people speaking fondly of him.
79.
by jaffathecake 1y ago
Right, but it should be easy for the reader to decide whether to divert to the additional content. A superscript number tells you nothing about the additional content. Whereas on the web, link text or a details summary can help you make a d
80.
by jaffathecake 1y ago
There are absolutely accessibility issues https://adrianroselli.com/2022/09/brief-note-on-super-and-su...
81.
by jaffathecake 1y ago
It's ok, but you're still being taken out of the flow. Especially as the notes appear arbitrarily on the left or right. And yeah, you have to find your place again afterwards. It's way better than scrolling solutions though.
82.
by jaffathecake 1y ago
The other issue is the poor link text (a superscript number) which gives no clue as to the content at the other end of the link. Like I said, it just becomes a test of your curiosity. Whereas the other examples have headings relevant to the
83.
by jaffathecake 1y ago
> Perhaps the author meant that a footnotes's form, i.e. a number or symbol, doesn't provide context for the note itself. Yes. I was referring to the uselessness of the linking text being a superscript number, which is as bad,
84.
by jaffathecake 1y ago
Fwiw this technique is covered in the article, with an example, and the UX issues are discussed. The simpler solutions presented do not have these issues.
85.
Give footnotes the boot – alternatives to footnotes on the web(jakearchibald.com)
41 points by jaffathecake 1y ago|33 comments
86.
Animating zooming using CSS: transform order is important sometimes(jakearchibald.com)
2 points by jaffathecake 1y ago|0 comments
87.
by jaffathecake 1y ago
A couple of us on the Chrome Dev Rel team made a minesweeper clone that aimed to be a bit visually fancy on most devices, but would still run on basic feature phones https://proxx.app/ It was a lot of fun to build.
88.
by jaffathecake 2y ago
I think the main issue is you're using "reactive" to mean something specific that you're not stating. The web is always going to have the DOM as its tree, so a system where one thing updates in reaction to another thing
89.
by jaffathecake 2y ago
> I think they should always be mirrored because they shouldn't be two separate elements That maintains one of the problems I'm worried about. If you have a mouseenter listener on something in an <option> that triggers a
90.
by jaffathecake 2y ago
The issue is that the "selected <option>" and "the <selectedoption> in the <button>" need to be able to render at the same time, behave independently, and be independently styled. If you have a psuedo-e

More ›