http://www.linusakesson.net/scene/machine-yearning/index.php
Steps to reproduce:
Something in the dependency tree will yell at you that it is deprecated or discontinued. That thing will not be one of your direct dependencies.
NPM will tell you that you have at least one security vulnerability. At least one of the vulnerabilities will be impossible to trigger in your particular application. At least one of the vulnerabilities will not be able to be fixed by updating the versions of your dependencies.
(I am sure I exaggerate, but not by much!)
Why is it like this? How many hours per week does this running-to-stay-in-place cost the average Node project? How many hours per week of developer time is the minimum viable Node project actually supposed to have available?
https://andrewkelley.me/post/zig-cc-powerful-drop-in-replacement-gcc-clang.html
https://tube.arthack.nz/videos/watch/6137f830-f77c-45ef-b779-27a8ee44565f
Doesn't seem like that acronym is used for anything important at the moment, I'm sure we can grab it.
That's right folks, I want to see you post your... old dreams.
Many AI image generators, including the big UIs for Stable Diffusion, helpfully embed metadata in the images so that you can load them up again and get all the settings you need to regenerate the image.
But Lemmy's built-in pict-rs image hoster, and most image hosters that resize or re-encode images or that try and stop people from doxing themselves with photos' embedded GPS coordinates, will remove all the metadata. This is counter-productive for AI image generation, because part of the point of sharing the images is so other people can build on the prompts.
What are some good places to host images that don't strip metadata?
@planish
@sh.itjust.works