Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/dailynet/public_html/wp-content/plugins/elementor-pro/modules/loop-builder/module.php on line 200

Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/dailynet/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
Speech-To-Text, 3D CSS Found In Chrome 11 BETA - The Daily Net

Speech-To-Text, 3D CSS Found In Chrome 11 BETA

There is definitely reason to get excited about the latest build of Chrome Browser which is Version 11 Beta. It features 2 new huge inclusions besides the trivial addition of the shiny new Chrome logoSpeech-to-text and 3D CSS!

I’m really excited about the use of Voice-to-text because I use it absolutely ALL the time on my Android Phone. With a limited size keyboard I can see why it’s more useful on a phone than a laptop or netbook that has a full keyboard, but I’ve got some hunches as to why they’re baking this feature into Chrome browser itself.

Android 2.3 Gingerbread is for phones, Android 3.0 Honeycomb is for tablets, and the next version of Android dubbed “Ice Cream” will not only combine code optimized for these two platforms… but also for Google TV. Remember that Google TV is based both on Android and Chrome – I think it’s fair to say there are scenarios when you’re watching Google TV from your couch where you’d like to use Speech-To-Text and watch 3D rendering in web apps.

At Google IO on May 10th and 11th, I’d expect Google to announce some huge additions to both Chrome and Google TV. The inclusion of Speech-to-text for web apps, in my opinion, is a sign of things to come.