haydenkshaw

Something really irks me about how this site is using the word 'roast'. Feels like any of the following words, with relevant dictionary definitions, would've been more intuitive: analyse, improve, critique, assess, evaluate.

Instead, let's take a slang word, re-define it's accepted meaning by removing the interesting nuance of it's usage, and try and piggyback of it's coolness. Not to my tastes.

Not sure on the name a18n, because it looks like a numeronym, like i18n is, but doesn't seem to be, had me trying to guess what the 18 characters are between a and n.

I get it's a18n like Automated18n like AutomatedI18n.

You can use HTML <picture> elements to provide provide multiple image format versions for an <img> element e.g. preferentially use webp if browser supported, and fallback to using a widely supported format if not. Sounds like doing that might be of interest to you.

The author's absolutely earnt the right to call themselves a CSS expert on their personal site, I had no idea CSS could do something like this!

Splitwise user here. Interface is clear and easy to use with most of the required functionality.

Personally I find the per-bill itemised expense part of Splitwise essential, being able to split a receipt into it's items and then charge particular participants for only certain items. Uploading images of receipts to each bill is also essential imo.

Big fan of this, excellent idea. EOL is always non-trivial to find for each project.

I think a good addition could be a feed of some sort available for each project e.g. https://endoflife.date/ruby/feed. You could then poll that from readers or Slack integrations and be notified when particular projects have entered EOL. Maybe an early warning for could be useful too, 3 months before EOL or something like that?

I ran into the same issue here too. They've fixed it in their nightly builds which I've found pretty useable: https://sequelpro.com/test-builds

Would probably use CloudWatch Logs for this personally