How is this not false advertising?
Gemini "duck" demo was not done in realtime or with voice
71–80 of 683 posts
Re: Gemini "duck" demo was not done in realtime or with voice
#72Shame on them :(
Re: Gemini "duck" demo was not done in realtime or with voice
#73It’s not live, but it’s in the realm of outputs I would expect from a GPT trained on video embeddings. Implying they’ve solved single token latency, however, is very distasteful.
OP says that Gemini had still images as input, not video - and the dev blog post shows it was instructed to reply to each input in relevant terms. Needless to say, that's quite different from what's implied in the demo, and at least theoretically is already within GPT's abilities.
Re: Gemini "duck" demo was not done in realtime or with voice
#74Re: Gemini "duck" demo was not done in realtime or with voice
#75I have used Swype texting since the t9 days. If I demoed swype texting as it functions in my day to day life to someone used to a querty keyboard they would never adopt it The rate at which it makes wrong assumptions about the word, or I have to fix it is probably 10% to 20% of the time However because it’s so easy to fix this is not an issue and it doesn’t slow me down at all. So within the context of the different…
Its honestly pretty mind boggling that we’d even use querty on a smartphone. The entire point of the layout is to keep your fingers on the home row. Meanwhile people text with a single or two thumbs 100% of the time.
No, that is how you're told to type. You have to be told to type that way precisely because QWERTY is not designed to keep your fingers on the home row. If you type in a layout that is designed to do that, you don't need to be told to keep your fingers on the home row, because you naturally will.
Nobody really knows what the designers were thinking, which I do not mean as sarcasm, I mean it straight. History lost that information. But whatever they were thinking that is clearly not it because it is plainly obvious just by looking at it how bad it is at that. Nobody trying to design a layout for "keeping your fingers on the home row" would leave hjkl(semicolon) under the resting position of the dominant hand for ~90% of the people.
This, perhaps in one of technical history's great ironies, makes it a fairly good keyboard for swype-like technologies! A keyboard layout like Dvorak that has "aoeui" all right next to each other and "dhtns" on the other would be constantly having trouble figuring out which one you meant between "hat" and "ten" to name just one example. "uio" on qwerty could probably stand a bit more separation, but "a" and "e" are generally far enough apart that at least for me they don't end up confused, and pushing the most common consonants towards the outer part of the keyboard rather than clustering them next to each other in the center (on the home row) helps them be distinguishable too. "fghjkl" is almost a probability dead zone, and the "asd" on the left are generally reasonably distinct even if you kinda miss one of them badly.
I don't know what an optimal swype keyboard would be, and there's probably still a good 10% gain to be made if someone tried to make one, but it wouldn't be enough to justify learning a new layout.
Re: Gemini "duck" demo was not done in realtime or with voice
#76I have used Swype texting since the t9 days. If I demoed swype texting as it functions in my day to day life to someone used to a querty keyboard they would never adopt it The rate at which it makes wrong assumptions about the word, or I have to fix it is probably 10% to 20% of the time However because it’s so easy to fix this is not an issue and it doesn’t slow me down at all. So within the context of the different…
Re: Gemini "duck" demo was not done in realtime or with voice
#77Earlier quoted context omitted.
How do you tell a plausible wrong answer from a real one?
By testing the code it returns (I mostly use it as a coding assistant) to see if it works. 95% of the time it does. For technical questions, ChatGPT has almost completely replaced Google & Stack Overflow for me.
Re: Gemini "duck" demo was not done in realtime or with voice
#78Earlier quoted context omitted.
Does swype make editing easier somehow? iOS spellcheck has negative value. I turned it off years ago and it reduced errors but there are still typos to fix. Unfortunately iOS text editing is also completely worthless. It forces strange selections and inserts edited text in awkward ways. I’m a QWERTY texter but text entry on iOS is a complete disaster that has only gotten worse over time.
Hard disagree. I could type your whole comment without any typos completely blindly (except maybe "QWERTY" because uppercaps don't get autocorrected).
It's even worse on the watch somehow. I take care to hit every key exactly, the correct word is there, I hit space, boom replaced with a completely different word. On the watch it seems to replace almost every word with bullshit, not just technical terms.
Re: Gemini "duck" demo was not done in realtime or with voice
#79The video itself and the video description give a disclaimer to this effect. Agreed that some will walk away with an incorrect view of how Gemini functions, though. Hopefully realtime interaction will be part of an app soon. Doesn’t seem like there would be too many technical hurdles there.
People don't really pay attention to disclaimers. Google made a choice knowing people would remember the hype, not the disclaimer.
I'm not saying there have been no improvements in AI. There is and this includes Google. But the reason why ChatGPT has really taken over the world is that the demo is in your own hands and it does quite well there.
Re: Gemini "duck" demo was not done in realtime or with voice
#80The bloomberg article seems to have been taken down and is now going to 404. https://www.bloomberg.com/opinion/articles/2023-12-07/google...