Both can be true and I have both opinions also in me. Love the progress, worry about the consequences of not being careful with it.
He does say in this post:
> I’m getting better at using them and get some boost from the models. It is a new skill, and it’s not like I haven’t constantly been trying them. You have to be really careful, they can increase cognitive fatigue, and all the vibe coded stuff is still slop (where’s all this new magical software that the productivity improvements should imply?).
They didn’t mean that Safari had a problem on rendering, but that their phone is so narrow, it often highlights pages that weren’t tested properly for mobile.
It seems the 13 mini is 375px wide, which isn’t even that narrow. The smallest I normally tested against was the width of the iPhone SE with 320px.
I’ve used asynq [1] at my past job. And although development is not as active anymore, they have a new contributor and we never encountered any bugs. It has been really solid and we relied on it heavily.
I switched to Apple Passwords this week. Really good passkey support, 2FA support, best iOS integration. You can even share passwords with others. Sadly no first party cli support. If you only use Apple devices, it’s really solid.
I only use Apple devices myself normally, but if I'm stranded out in the middle of nowhere and have to borrow someone's Android phone or Windows box in order to connect to important stuff like my bank, I'd really rather not be out of luck. Same reason I don't self-host my vault.
The only thing it's missing for me is secure notes for me to store my 2FA recovery codes in. So I mainly use Apple Passwords now, but still keep Bitwarden going for secure notes.
Why not? I do the same, I tell it the exact content, but I don’t have to do all the rest. My blog is a react based (because I like interactivity) and has no asset pipeline, so it’s not as user friendly to edit the content as e.g. a markdown file.
reply