News for hackers. Stuff that matters.

A comment on Understanding Google Zanzibar and Why it Shines at Building Permissions. Parent comment

Re:Understanding Google Zanzibar and Why it Shines at Buildi... by sowbug on Sunday June 25, 2023 @05:47PM (#36472944)
This tired trope has jumped the shark with this comment. Not only is it off topic, but even if it did refer to an actual Google product, it's disingenuous because its only point was to be snarky.
[ Parent | on HN ]
Re:Understanding Google Zanzibar and Why it Shines at Buildi... by lopkeny12ko on Sunday June 25, 2023 @08:25PM (#36474157)
It's not disingenuous. Unless you've been living under a rock, Google has a very reliable track record of killing projects [0]. It's a very reasonable question.

[0] https://killedbygoogle.com/

[ Parent | on HN ]
Re:Understanding Google Zanzibar and Why it Shines at Buildi... by esafak on Sunday June 25, 2023 @08:41PM (#36474269)
Zanzibar is a system described in a public paper, not a product; it can't be killed. Indeed, it has been implemented as a service by numerous other companies.
[ Parent | on HN ]
Re:Understanding Google Zanzibar and Why it Shines at Buildi... by kweingar on Sunday June 25, 2023 @09:15PM (#36474523)
I'm confused as to why anyone outside Google would care about the possibility of Google deprecating Zanzibar. It's an internal-only project that handles authorization across Google services. It's totally invisible to all users and customers. I can't think of a reason why anybody would be affected by Google switching to a new global authorization system.

What are you concerned about here: a potential impact on users, or the internal impact for Google engineers that could come from switching to a new system?

[ Parent | on HN ]