Fast prototyping for code I'll throw away anyway. Sometimes I just want to get something to work as a proof of concept then I'll figure out how to productionize it later.
The only time, for me, this is true, is when it's empty and I have very few items. If there's a line, I'd rather wait for the cashier. Self-checkout seems to get clogged up with people waiting for the supervising human the busier it is, so to have a human or two (one ringing one bagging) when I've got a cart and there's a line, is advantageous.
I'm also pretty anti-social and actually prefer the robotic banter of quickly checking out with a person to the anxious nightmare of just trying to buy something real quick and now waiting because the machine hates life more than me.
Oh and many of the folks doing the bagging at some of the stores are disabled, and I dunno - I hope we're taking care of people in those jobs.
For ninety nine out of a hundred scenarios, I've never had to wait for a supervising human at all. Maybe it's where I shop, but generally speaking, I've almost never had a problem with people needing to see my checked out items.
It's a marginal improvement perhaps, but nothing to write home about. And for other things (e.g. booking travel) the self-service experience can be worse.
Not sure about that, I prefer to know all aspects of booking travel that I would not trust to another agent, human or otherwise. Therefore, I believe your statement applies to some people and not others.
This is essentially Microsoft's Fluent UI [0], right down to the translucent glass rectangular prisms (not to say that there haven't been glassmorphic UI systems since forever, including Apple's own Aqua).
Even before that, mobile UI frameworks are retained mode GUIs, not immediate. They aren't drawing to a blank framebuffer 120 times a second if they don't have to. Redraws only happen when something changes (e.g. "Dirty" rects).
Oh even immediate UI framework don't paint non-stop. If the UI has not been interacted with, or if there are no animations/gifs, it has no blimey reason to repaint, and it will not. It will repaint the whole screen, of course, but that's already a win.
What are people using for realtime transcription and diarization specifically? I'm thinking something like Zoom's transcript feature but Zoom itself has the advantage of knowing exactly who is speaking at what time so they don't need to diarize from raw speech at all.
So far I've seen DiCoW-v2 work pretty well, it's a diarization finetuned Whisper [0], also paid options like Speechmatics work well and are fairly cheap.
Most SaaS contribute to economic productivity though. I see the uptime of local services that our IT maintains, let's just say it's not good. By paying a monthly fee for Slack, we get a working communications system which much better uptime than what we could get from self-hosted.
This is very specific contribution in economic productivity, as the company gets no work done when the communications system is down.
> "Experimenting" with no-build web apps makes it sound like web apps require build steps by default. The opposite is true.
It's not that it's required per se, just that when it seems like most people use applications with a build step, experimenting is the right word to use when going the other way, even if it is the default. It might even be the case that the author hasn't made apps without a build step so again in their case, they indeed are experimenting with it, even if to others it doesn't seem like an experiment. In any case, as with any experiment, they are learning something new.
