The Wednesday Wellness threads are meant to encourage users to ask for and provide advice and motivation to improve their lives. It isn't intended as a 'containment thread' and any content which could go here could instead be posted in its own thread. You could post:
-
Requests for advice and / or encouragement. On basically any topic and for any scale of problem.
-
Updates to let us know how you are doing. This provides valuable feedback on past advice / encouragement and will hopefully make people feel a little more motivated to follow through. If you want to be reminded to post your update, see the post titled 'update reminders', below.
-
Advice. This can be in response to a request for advice or just something that you think could be generally useful for many people here.
-
Encouragement. Probably best directed at specific users, but if you feel like just encouraging people in general I don't think anyone is going to object. I don't think I really need to say this, but just to be clear; encouragement should have a generally positive tone and not shame people (if people feel that shame might be an effective tool for motivating people, please discuss this so we can form a group consensus on how to use it rather than just trying it).
Jump in the discussion.
No email address required.
Notes -
What are your must-have browser extensions?
Mine are the following:
Don't accept webp
What's wrong with webp?
Compatibility issues aside (which are ridiculous because the format is more than a decade old), .webp is actually a good format on its own merits. Far better compression and quality than JPEG, and quite close to PNG in terms of the latter.
It's funny/sad the creator actively participates in Twitter threads trying to clear his name when it's being maligned, but it's not really his fault that software devs are too lazy to implement it. It makes for massive savings in image size for hosts, and for little loss in quality, you'd hope they'd have picked up on that by now.
WebP wasn't awful for 2014 -- though it wasn't as clearly beneficial as Google tried to argue, the major alternatives were either obnoxious to implement (JPG2k/JPGXR) or had annoying licensing issues (HEVC) -- but it's since been badly outmatched by more focused variants. Google has been pushing AVIF as the next step, with good reason, and while JPEGXL isn't without its downsides (how many fucking flags can the example implementation have?!), if you were building a new project from the ground up (or especially with a lot of pre-existing jpgs to transcode) and didn't absolutely need motion video support, I'd almost always recommend it.
And it does have some obnoxious limitations. Pixel size is the one that's bitten me in the butt the most often -- yes, 20k+ pixel dimension images probably should be done in a mipmapping/tiling format like JPG2k, yet there's a surprising number of use cases it still comes up -- but the fixed chroma subsampling is the most incomprehensible.
I think WebP gets more of an unfair rap than format deserves, largely downstream of how aggressively Google pushed it and the extent it's been used as justification to cut off support for other formats in Chrome- and Chrome-derived browsers. But it's really frustrating what Google and Chrome developers have done as a result of the format.
More options
Context Copy link
More options
Context Copy link
It's often incompatible or partially compatible with other programs and websites.
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link
More options
Context Copy link