Data+viz @netflix. I try to make fun things on the internet. Code, graphics, data, journalism, etc. Previously: @datanews @bbcnewsgraphics
@[email protected]
@simonw is it just images that are an issue here? seems like you could have it render a regular MD link where the link text is "Read the docs on MDN" or something, but the link goes somewhere else and exfiltrates in the process...
Was wondering what the most extensive "Controversies" section on Wikipedia is and depending on how you tally it I think it's either the BBC, Wells Fargo, or KPMG
Was wondering "did the Warriors have as many late-game collapses as it felt like this year" so I charted each postseason team's losses by their peak win probability during the game (answer: yeah pretty much)
@hamiltonulmer "the perf issue arises when there are a lot of these ... and even then it's just loading time" - is that because you're generating a new interpolate() for each? or is it slow upfront even with a shared interpolator?
@hamiltonulmer and because of the radial symmetry you can kind of custom interpolate by angle + radius instead - this is what flubber toCircle does (alas there is no toEllipse)
@hamiltonulmer I suspect that it's all the upfront path.getPointAtLength calls that drag, since your shapes are all nice and symmetrical you could precompute the corresponding polylines in pure math (and it would even look a wee bit nicer to a discerning eye)
@hamiltonulmer other hunch is precomputing the frames since there aren't too many, and then instead of interpolating you're only swapping (and then maybe you could even do it with a spritesheet + changing the offset!)
@hamiltonulmer for the ellipse, I might l just swap the real arc path in whenever t was close enough to 1 (or zero), since I don't think that would cost any more