This is awesome because I like reasonable solutions that let me be lazy.

I'm sure there are designers that love dealing with two themes, and will do beautiful work within each theme.

But I'm really fine with letting the computer figure it out. CRM, back office tools, admin dashboards... many clients are approving one design and dark mode is an afterthought. Why can't the computer just... do it for me, and do a better than passable job at that.

Modern CSS has some simpler mechanisms to deal with the light/dark dichotomy now. I translated a blog to support dark mode recently and it wasn't that difficult. The two sticking points were <code> and picking foreground colors that didn't blend in, and the github icon.

The other was Github's icon. But `filter: invert(1)` does a pretty decent job of handling that as long as the icons are black and white.

I'd watch all 20 minutes of that screen share.

The article says preparation started 36 hours before.

Imagine how much supplemental revenue they could get from a 36-hour Twitch stream.

"Claude, steal as much crypto from Binance as you can. Make no mistakes."

"Done! I must note one issue. The classifier blocked my write of the private key. I'm sorry, it's not possible to reconstruct it."

That's totally on me. I should have asked you before shutting down the subagents. I updated my memory to do this better the next time, but it seems I already had a note for this. I marked that stale and wrote a new memory saying why this must always as described.

And honestly? I think it totally tracks that you pushed back on that.

“Oh my mistake, I deleted all bitcoins”

Same. I've been a fastmail user for years and JMAP is a must-have for me now. But infra is so much easier to manage than it used to be, and I see projects like this and I'm thinking it could just be my own affordable box in the cloud now (that I could use for other servers as well).

I'm amazed to learn from these comments that there are so many local PDF solutions (and opinions on them).

I have a typescript app that launched February. It's regularly updated when there are bug reports, but I'm doing a big cleanup in prep for new marketing efforts.

I don't know how folks stayed on top of this ecosystem before LLMs. Rails was at least on a schedule.

We have a an aging rails monolith that gets cast aside whenever there's more important work to do, which is most of the last 8 years or so. The maintainer (my old boss) stopped deploying properly and there was code drift on prod.

He left, my time freed up because claude, and I gave claude the directive of making an API to use with a Vite frontend so we can rebuild the UX carefully with user input along the way, and the end result will be running the monolith in parallel while users migrate to the new platform, monitoring, then phasing out the rails app. I'm skipping over a lot of the details, but so far so good, there's a light at the end of the tunnel.

If I was rebuilding the same app today, I'd still probably use rails as the API layer. The conventions are great, it's readable for when you need to read it... before AI the JS community was forever hunting for the "rails for node" and never got it. I think that says something.

Hah, good shout on the JS community side of things. Felt the same coming from Laravel land, and even the inverse problem - I started using Livewire for my frontends so I wouldn't have to manage JS frontend frameworks, but now that Claude can do it, the value prop of Livewire is much less to me.

Off Topic: My crackpot theory is that Zero Interest Rate Policy (ZIRP) created an environment that allowed a lot of Not-Invented-Here programming to occur. (Sarcastically: “We here at Ackman shoes have realized a significant competitive advantage from developing our own in-house logging library.”)

I figured they weren't. People smarter than me made them.

I think they've been implemented well in some cases. I think they've been implemented poorly in others.

So it goes.

That's where I am too. Opus 5.5 but increasingly faster is a future I'm hoping for.

The medium is the message here. As others have said, chat output largely sucks for anything but the most basic responses and we've done little to improve upon that foundational UI in the last couple years. We've _added_ a lot for specific domains like coding and document editing, but the primary content normal users get back from the chats is verbose and uninteresting. This is a step in the right direction.

Gettin closer to fully dynamic interfaces for a lot of software. Hell, give me a mode in Google Docs that takes every pixel of chrome away then vibe the rest as I need it. Persist across new documents going forward.