infinite-mac VS nomulus

Check https://infinitemac.org - some of the Macs there seem to have an Ambrosia folder. Hopefully it's what you meant? :)

(I alrady found another (Apple Slicer) on https://infinitemac.org/ ), on PMUG PD-ROM 1995).

Is there a collection of Linux virtual machine images I could use to run these old browsers? There's https://infinitemac.org/ for MacOS and Windows 3/95/98 VMs, but I've had a hard time getting Linux binaries from the early 90s working.

Has been done already, in a way. Check out https://infinitemac.org

Not the same thing but sometimes I like to use infinity Mac on my iPad. https://infinitemac.org

It's possible to register at the root, but ICANN has disallowed it for gTLDs (countries see ccTLDs as TLDs they "own" so ICANN isn't interested in trying to impose too many rules on them - http://ai. )

And companies have definitely purchased their own TLD for use cases that don't violate ICANN. For example:

https://blog.youtube

https://applecard.apple

https://pki.goog/

https://goo.gle

and of course https://registry.google / https://blog.google which was the domain submissed.

https://github.com/google/nomulus

That's at least 10 engineers maintaining one component. Add in SRE and product executives, you are looking at expenses in the two digit millions minimum.

The decision is definitely short sighted but somebody high up no longer wants it as a loss leader.

I don't know what to say other than that my experience here is precisely the opposite of yours. Different areas of the company? I use a LOT of third party libraries in the course of my employment, and third_party in my experience is full of legitimate third party libraries, not ones that are developed by Google.

Anyway, here's the list of dependencies for my project. There's a lot of third-party stuff in it: https://github.com/google/nomulus/blob/master/dependencies.g...

Indeed that is correct. For more information see:

https://registry.google

https://nomulus.foo (our open source software that runs our TLDs)

You can escalate to legal for edge cases, but you should be able to handle base cases yourself. As an example, I work at Google on an Apache 2.0-licensed open source project, and we have dozens of third party dependencies: https://github.com/google/nomulus/blob/master/core/build.gra...

It wouldn't remotely scale across Google if we had to escalate to legal every single time we pulled in a new dependency. Instead, there's a company-wide allowlist of accepted software licenses, and you only need legal help for exceptions beyond that.

So yes, we do have to know some basics of software licensing. It's just part of being a SWE.