I know, provoking headline but I would like to understand something. Every now and then when I work with Kirby I stumble over the issue that I don’t get why the build in image handling is so rudimentarily.
Why do I have to override the image tag if I would like to have something as srcset and sizes? Shouldn’t that be default in 2020? I know that it needs to be configured but why not have a default fallback - people setting up Kirby should be able to understand that they need to configure that stuff to their needs.
I now there is something like the srcset plugin but that won’t override the image tag, then you have to deal with different image tags…
I’m not a full time developer, I just like to fiddle around with stuff, but this is something I’m always struggling with and I’ve the feeling that this isn’t something we should deal with in the first place to build something.
This should be build in; with background image resizing; maybe even wepP support. Make it as easy as possible to build a fast website - delivering text and images to browsers in the fastest possible way using the lowest needed bandwidth, without the need to deal with plugins (and get the plugins to work with each other. Having a flash on first load or no thumbnails at all before they are requested; even in the panel? I deal with people that get confused when an image doesn’t show up there immediately.
Let people who would like to use external services and plugins use them, I get that there is a need to make it as customisable as possible. But shouldn’t the default be, that images are not the reason you can’t get a 100% in lighthouse without jumping through hoops.
Maybe also look at it from a sustainability point of view the default shouldn’t be that a bare Kirby delivers large images to devices that can’t handle them, extending load time and bandwidth.
Is it just me, is everyone else fine with that, am I just missing something? 
@bastianallgeier @texnixe