Person B: Well, it didn't go away, they just changed the access method to Google Drive.

Saved us that conversation here, Thanks. No matter what mental gymnastics we may do, it is pretty clear where this is heading.

On a different note, the source download form requires you to accept Google's privacy policy for the information you submit.

Is it ok to tack on accepting additional policies as requirements to access what is allowed under OSS licenses.

How many of those features were really organic, driven by actual pressing need and not driven by Google's needs.

I'm sure many other players will play top dollar to be the default on a browser that virtually commands all the market. That'll let us discover the real price of search engine defaults because the Mozilla payout is partly due to antitrust reasons.

In that case, I think we'll also see a visible decrease in "bugs" affecting Firefox on Google's properties.

I've seen this so many times where the same individual introduced and fixed the bug, it is now funny.

This is corporate team level equivalent of "Socializing losses and privatizing profits".

If questioned, I can already imagine someone defending that sort of agreement as a standard consumer, contractual terms and practices of the time.

The policy and the keyword should have been collaboration and not cooperation.

Was your past employer trying to make best of the situation by hoping to fish for information about your next employer's projects via the consulting gig?

It has been the opposite for us. It is now being weaponized by PMs and leads to add more work for developers and not less in terms of documentation and sign-offs.

Now stories automatically have additional 10 subtasks for documentation and tracking. These are created automatically through "skills" and the task of detailed documentation and updating those extra tasks is a chore. When complained, they just say "use AI". Every JIRA task these days feels like submitting a petition to the government bureaucracy.

PMs are happy because they did something new, leaders are happy for more tracking, developers are expected to be happy with "productivity gains" due to not having to write much code.

If any of those vim extensions support link+split, and allow interaction with splits that would be even better.

Yes, that is what I meant. They should be hesitant to lockdown completely and (grudgingly even) allow alternative options and/or workarounds due to legal concerns like anti-trust.

Firefox was existing before Chrome, but in this case we either need a different OS or need an android based option like Graphene/3rd party stores gain enough marketshare to trigger anti-competitive laws.

We don't need anything to completely capture the market, it has to be just enough to make Google hesitate or make it hard for Google to do it for legal reasons. Like how Firefox is ideally supposed to be for Chrome.

It doesn't have to be a replacement. Anyone who has ever been in the physical presence of an expert reciting sanskrit verses knows that this can never replace that experience.

It will only make the language and the chants more accessible.

Having a spoken reference that too as a chant makes it easy to recite the verses.

I think the vocal minority advocating for tipping are probably the ones that receive (unaccountable) higher tips while the ones that are scraping by would actually feel more comfortable with a good wage than unpredictable tips.

Gmail in its early stage had a simple surface area. These days a Google account could mean a gateway to entire digital life for some. It requires much more focus and responsibility to handle and Google never had plans to do any of that from the beginning.

Yes acceptance may have gone up, but I think thats a side effect of normalizing digital transactions popularized by UPI.

Or simply put, can wild animals eat tomatoes safely(on evolutionary timescale) in winter if they don't normally grow in winter.