Speaking about the specification, it's a proposal. Yes, some run ahead and implement proposals under experimental flags, doesn't make it any more/less hypothetical as the proposal can still be rejected rather than progressing.
I'm not very familiar with Nuxt or SvelteKit but this is exactly what React and NextJS provide with server components. Any JS related to server components isn't shipped, only client components which effectively represent the islands. The only real difference is you're not mixing technologies, it's all React.
With a switch you expect an immediate effect to occur. The expectation is that I toggle the switch then get on with my day.
Checkboxes don't have side effects, they're expected to be form based. Once I toggle a checkbox the expectation is that I need to then also submit that selection in some way.
This feels like an enormously loaded set of expectations you are bringing here. If one in one hundred thousand people could reproduce this answer I'd be surprised.
This question of immediacy feels like it applies to any form control. I don't see how the slider is in any way clearer or more obviously immediate.
IMO this just comes down to Apple having switched to mainly using sliders, and wanting that to be a look people can use. And it so happens that Apple doesn't have "save" or "submit" or "done" on any of their forms: on Apple it so happens that almost all their form controls are live. But these are two separate decisions, aesthetic and function, and wanting to couple them is just forcing your prejudice, and there's not any actual reason cause or substance for it.
I have the same expectation - that's what a switch does, both in real life, and on devics. You toggle it, the thing happens. So I don't think this is 1 in 100,000.
For what it’s worth, I have the same expectation and have been applying it to forms since IOS 3 or 4.
If we’re going to have a switch-looking thing, it’s because it brings some skeuomorphic affordance with it: I think “off/on with immediate effect” seems like exactly the thing it should bring to differentiate from a checkbox.
Having a weird design language expressly for immediate-effect entities is absurd & dumb. There's other context we should be using to set expectations, rather than creating parallel systems that do the same thing but through gentle skeuomorphisms imply something. Currently we have checkboxes and checkboxes alone as distinct, but it feels like this line of logic should be extended further if this is the implication.
I think it's still 1 in 100,000 in any broad sense of people, not just Apple-fans on HN. Especially not folks who are already reading the thread.
The YouTube app on our Sony TV kills me. Out of a variety of apps installed (Netflix, HBO, Disney, Apple, Prime) it's the only one that we need to adjust volume for EVERY SINGLE TIME because they decided 15 should be loud vs 30 on all the other apps. Especially frustrating when a lot of the time the first play experience in YouTube is being blasted with some kind of rapid-fire ad sequence.
I don't know if "transformed my life" would be the right term but I always harp on to colleagues about my Polycom. I was skeptical when originally buying it but the purchase has ended up being one of my favourite things on my desk.
My laptop is docked and closed so using the built in mic and speaker isn't a great experience on remote calls. I don't like the experience of using headphones for a call because of the effect they have on how I perceive my own voice.
With the Polycom on my desk I just join a call, have everything set up automatically and get a great speaking/listening experience. Connectivity issues have been extremely rare and I can't remember the last time I needed to mess with settings unlike my Airpods which feel 50/50.
I personally have the Plantronics P7200 but there's many good options out there. Plus points for being able to expense it to my employers work from home allowance.
reply