> Some things are worth the fight, some are not.

That argument goes both ways. If the Chrome team were unionized/organized in some form, and said "hell no" to the cookie change, then I doubt Google's management would shrug and replace the whole team with fresh H1B workers just to get this small change in.

I also find it fascinating that so many people bring up children as a reason to give up your ideals. My dad gave up a well-paying job for a more fulfilling one, and it would never occur to me to blame him for it; if anything it's inspiring. This was in Europe, with a reasonable safety net, but I don't think that Xooglers would hit rock bottom anyway.

This isn't just about cookies though. When Google designed HTTP/2 they kept cookies in favor of a separate authentication mechanism. Arguably because otherwise people would end up removing cookies altogether making themselves harder to track and with Google losing ad money in the process. Now Google have seemingly decided they want to have their cake and eat it too, just only for themselves. This isn't one incident but Google manifesting thier direction for themselves and the Internet. (Just recently they also disabled sign out from their YouTube app for instance). If you disagree with this direction that is certainly a good reason too quit sooner rather than later. Pretty much everyone I have ever talked to that ended up changing e.g. jobs because of a disagreement wish they did so earlier. It is very easy to sit in the same position and hope that things will get better and hard to see what else is out there even if it is very clear in hindsight.

>Do you just say "fuck it", and quit, ignoring all your responsibilities? Over cookies?

If you follow the news about Google at all, you'd know its obviously not just about cookies.

>Of course, when its not about cookies, but about something more drastic

It's about the the greatest surveillance apparatus in history encroaching towards total informational awareness.

for the individual developer getting asked to implement this, it is over cookies. The decision is "Do I implement this, or do I tell my kids I dont know how to feed them"

>for the individual developer getting asked to implement this, it is over cookies

No, cookies would be the straw that broke the camel's back. The context you're ignoring the the countless other straws beneath it.

>The decision is "Do I implement this, or do I tell my kids I dont know how to feed them"

False dichotomy