@SwiftOnSecurity I know this was tongue and cheek, and you're not wrong, but size isn't the only factor!
The DOM *should* be semantic, and deliver information about the content beyond the visual rendering.
Screen readers likely aren't going to work as well on your static image version, for one.
After a week where I mostly felt behind, I managed to get to my favorite task of the week - firing off a smidgeon of internal webdev "journalism" - and made it to the beach for sunset. Weekend's off to a good start. Happy Friday from Trestles.
@_r00k_@LadieAuPair This is definitely in my wheelhouse, and we already had a discussion today about the best way to allow users to set one optionally. Should be in the works 🙏
@tartley@doctorzaius@mortenmertner @ikasliwal This is my stance as well, and I fear it's gotten me the label of 'opposition', which is frustrating. Pointing out the amount of effort involved is not "pushback"; estimating work is the first step to getting it resourced and done.
@ikasliwal @usirin I was very glad we had it as well; particularly happy that argument was shot down...I think it's a knee-jerk reaction that hopefully most would realize is silly after more reflection.
@spencerbeggs@getify I'd argue that once they get over that learning curve, they could move faster with more confidence. But every project is different; what works for some may not work for others.
My self-designated title is Front End Facilities Maintenance, but that's just a joke on my part. This describes what my team does pretty perfectly though, I dig this definition 👍
I would add one thing: documentation of processes, patterns and best practices!