I'd guess the same, but they didn't have this problem a few years ago... :(
Hi, I'm speculating but my guess would be that they fear the update might replace dynamically-linked files (“plugins”) on your hard drive with new ones that would be incompatible with the FF binary that is already loaded in memory.
Yes, that started getting really annoying. I've disabled automatic updates using https://support.mozilla.org/en-US/questions/1304175#answer-1350120 so I can do them when I anyway restart my system
Oh how I despise this "Restart to keep using Firefox" message that FF throws when it got updated. If I want to keep using it, why should I stop using it in order to do so? Why is this software trying to force such things upon me, and not let me choose to do so when it's convenient to me.
Didn't understand correctly, but maybe there should be a question related to this. Will post in a day or two :)
`l3draw` is in fact a bit slower than `pgf` (`l3draw` is more comparable with `pgf` than Ti*k*Z), but it uses a complete floating point engine for every operation in which that is possible, and hence doesn't have issues with "dimension too large" unlike `pgf` (without its `fpu`-module, that shouldn't be activated during drawing, iirc)
:) yes, the result isn't particularly surprising ... but one does not use Ti*k*Z for the speed :P
just measured a bit myself (using `\benchmark_tic:`/`\benchmark_toc:`), for me `pxpic` package loading (with all its dependencies) and image drawing doesn't even take 0.1s in total, while loading PixelArtTikz and its dependencies takes almost a second, and drawing the parrot takes another second.
@निरंजन remember when I told you, that there is no reason to use `expkv-opt` when you don't use any key=value option. Well, starting with the last release (and pretty up to date LaTeX kernel versions starting with 2022-10-01 if I'm not mistaken) this is no longer true if you have options that don't need to be known during load time, see `\ekvoProcessFutureOptions` (same would be possible with the new `\ProcessKeyOptions` of the LaTeX kernel starting with `2022-06-01` or so).
you could also remove all the trailing `-` from the end of each line for a bit more speed.
though output of that package looks good :) I just don't like the necessity for another file.
``` \documentclass[border=3.14]{standalone} \usepackage{pxpic} \begin{document} \pxpic[colours={4=black,1=red,9=white,2=brown,3=yellow,6=blue},skip=-] { {------4444------} {----44111144----} {---4111111114---} {--411111111114--} {--411111111114--} {-41991111119914-} {-49999444499994-} {-49499444494994-} {-41999444499914-} {--411944449114--} {--411144441114--} {---4111441114---} {--431111111134--} {-46311111111364-} {-46611111111664-} {-46611111111664-} {-46411144111464-} {2242444224442422} {2222222222222222} {2222222222222222} {-----411114-----} {------4114------} {-------44-------} } \end{document} ```
I listened to an interesting podcast about Mark Spencer this morning https://www.bbc.co.uk/programmes/m000sz1m He had a pet duck called Daisy while growing up :)
Package in the spotlight: [PixelArtTikz](https://www.ctan.org/pkg/PixelArtTikz) 

Well, for the project I'm working on as my dayjob the rule of thumb is: Don't change anything that once ran. Last summer I did a (presumably) harmless change to have identical code only in two instead of 10 places, and butchered support for a complete vehicle family...
You certainly spent some time lately on chatGPT. Is it just me or the results are quite stunning (for simple stuff) ?  
It even has a duck! Brilliant! 
yes, last time only took me a full year... :P (well, a year in which I've bought a house and started renovating it, so maybe not a "full" year)