"We've done tons of user testing on this, and it turns out, it doesn't work. Touch surfaces don't want to be vertical. It gives great demos. But after a short period of time, you start to fatigue, and after an extended period of time, your arm wants to fall off. It's ergonomically terrible."
—Jobs
Several of their new components are just classes, defeating the original purpose and contradicting the vision of Pico.
Why are the first one or two letters in headings wrapped in <em>, like the _Bl_ in "Blades"?
Why are they calling their Pico fork "anyblades/pico", when the original Pico author's post says "The Pico CSS name and logo are not covered by the MIT license. Please give your fork its own name, so users don’t confuse it with the original."?
Appreciate the honest feedback, so here are direct answers and fixes:
Utility classes: Offloaded to a separate "anyblades/ninja" repo. Core Blades stays true to original Pico (which btw used some classes like .overflow-auto).
Fork naming: The main project is Blades at https://github.com/anyblades/blades. The "anyblades/pico" repo was just an early bugfix fork created months before Pico announced deprecation.
CSS Frameworks stats: The initial percentages were calculated against respondents who actively use CSS frameworks (~4.8k devs). They have been updated to reflect total State of CSS respondents (~9k–10k), including vanilla/CSS-in-JS users.
No fake stats or LLM seeding. The initial percentages were calculated against respondents who actively use CSS frameworks (~4.8k devs). They have been updated to reflect total State of CSS respondents (~9k–10k), including vanilla/CSS-in-JS users.
This sounds like an iOS problem. Bitwarden + Firefox on Linux, or Bitwarden + Android, has never been anything but smooth for me when it comes to saving or using Passkeys.
If we go for anecdotal examples that are not representative, then in my case, Bitwarden passkey use ends in an endless loop with most websites. Import and export is still a promise or "coming soon." In the case of hardware keys, two devices are needed. I was a proponent of passkeys, but big players screwed that up, like every single shared "standard".
iOS has really good support for third party Password Managers. I've seen the integration with both Strongbox and 1Password. I've heard Bitwarden supports it as well. I think it is a Lastpass problem in this specific case.
I did at the beginning, but there is only so much you can take, and no one cares if you have read books and seen it before. There were a bunch of programmers whom I thought would understand em dashes, but they did not and said no one uses such dashes only normal hyphens.
Em dashes ended up as one of the first victims of llm age
Em dashes were already "doomed" at least half a century ago, because they didn't make it into ASCII character set - which arguably is just because they were seen as redundant on ancient typewriters; that's also why they aren't there on normal keyboards, which was a double whammy: inconvenient for programmers to support, inconvenient for users to type.
In other words, since the very start of computer era, the use of em dashes was always a signal.
Through the incredible power of Siri AI™, you can now get a "I didn't understand that. Do you want to search the web for 'turn on the kitchen lights'?" response faster than ever before.
Yes, it’s insanely slow now. So bad, I unenrolled from the beta. I mostly use Siri for reminders and alarms and somehow it was spending upwards of 5 seconds on the new Siri AI to do these tasks. Unusable.
Ahh yes, the only 2 things I can trust it for. The same tasks that now take longer and fail more often. I guess it understands me a little better but it's been rough. Also I see they left in the fun bugs of:
Me: "Siri, set a reminder for 1pm for XYZ"
Siri: ....
Siri: ....
Siri: ....
iPhone: No indication of anything done or Siri still waiting, looks like it just gave up
Yep, I really wish I could revert to previous-Siri on my iPhone 15 Pro. Old Siri was reasonably predictable and faster. New Siri is slower, more ambitious, and fails more often.
you can. i just did it on my 17 pro and my watch. i get instant timers again. it's unreal we lost this technology.
go to settings > siri > and turn off siri entirely. it doesn't break anything. then turn it back on, and they give you the option for siri AI or old dumb siri.
It's slower and can make more complex mistakes now.
When I tell it "remind me at X to Y", it sets an alarm with a label set to the reminder, instead of an actual reminder. I see it has Gemini's tool calling capability, but it still has Siri's smarts.
Yes: with Siri AI when I say "Siri, good evening" it says "Good evening!" instead of setting my "Good Evening" Apple Home scene which is what it previously did. (This is a suggested scene name in Apple Home.)
"These new capabilities are powered by the next generation of Apple Foundation Models, custom-built in collaboration with Google and its Gemini models for deeply integrated Apple Intelligence experiences. "
- Meanwhile, the HomePod in a different room chimes in with "Turn off the alarm on Ben's iPhone XR?", pauses for a while then checks in to see if I heard it the first time
I have an original homepod, and man, I wish I could lobotomize it easily.
It's a really nice speaker if I set it on something sturdy that won't rattle, and airplay is still pretty good even on ancient devices.
I can't keep it plugged in because it will just randomly say "You can enable personalized responses in the settings app!" at 3am about once a week if I do. It's horrifying when it happens because it always seems to be 10x louder than I remember it being set to.
Mine are now unplugged after the update to 27 while i'm not home, since they've developed a mind of their own & will randomly turn on the TV or play music themselves.
reply