Hacker News

3943 readers

3 users here now

This community serves to share top posts on Hacker News with the wider fediverse.

Rules

0. Keep it legal

Keep it civil and SFW
Keep it safe for members of marginalised groups

founded 1 year ago

MODERATORS

haxor@derp.foo

-1

Changes we're making to Google Assistant (blog.google)

submitted 10 months ago by haxor@derp.foo to c/hackernews@derp.foo

8 comments fedilink hide all child comments

There is a discussion on Hacker News, but feel free to comment here as well.

you are viewing a single comment's thread
view the rest of the comments

[–] lvxferre@lemmy.ml 2 points 10 months ago* (last edited 10 months ago) (2 children)

It's hard for Google to claim that they're focusing resources (e.g. dev time), given the list of features being removed. As one of the HN comments said, quite a few of them "seem to fall under the umbrella of "features that actually make the assistant an assistant"/connecting the assistant to other apps". In other words, integration - that's core functionality for an assistant and they likely know it.

[–] _wizard@lemmy.world 1 points 10 months ago

Let's not forget they terminated A LOT of the Assistant developers within the last week.

[–] stepintomydojo@sh.itjust.works 1 points 10 months ago

I would define the core capability as "takes audio, extracts meaning, matches to intent, executes intent". Everything else is an implementation of a specific intent/action. Some of them are likely fragile and depend on integration APIs that may be changing or going away.

Ultimately, yes, it is corporate-speak to sugarcoat what looks like a net negative for users at the current time with nebulous claims of a better future.