I think they’re just stopping operations of the company in Brazil.

But I don’t think they’re going out of the way to prevent Brazilian IPs from connecting.

This is a good book on how Google treats production environments at their scale.

Cattle, not pets.

Google operates on a trunk model, according to this:

https://dev.to/tbodt/comment/1j4e

The entire TotT series is pretty good.

In the case of Google, the trade off is compensation.

You can work for for Google in NYC and make $300k+ per year, or work for Google in London and make half as much at best.

It’s the USA.

Yes, they can just fire people.

I mean, it’s GPL code.

Anyone could just upload it, possibly with branding changes if “GBA4iOS” a trademark, as long as they publish the source code with their changes

And my example of knowing critical systems for the web written in Python is somehow different from your argument?

What a joke

You have no idea. Python (and Ruby) are used widely in the industry. Large parts of YouTube are written in Python, and large parts of GitHub are written in Ruby. And every major tech company is using Python in their offline data pipelines.

I know of systems critical to the modern web that are written in Python.

Dynamic typing is not a fad.

Python is older than Java, older than me. It is still going strong.

That’s not “source available” because the software is not released through a source code distribution model.

Companies may have access in order to produce better drivers or handle security incidents, but those are back-room deals, not part of Windows’ distribution model.

I didn’t think the Windows source is widely available, only the compiled form.

.Net core is open source though.

Source Available < Open Source < Free Software

These terms have specific definitions, where each greater term is more specific than the lesser*.

SSPL is in the “Source Available” tier.

The OSI defines the term “open source,” and the FSF defines the term “free software.” The number one term of open source, greater than the availability of the source code, is the freedom to redistribute.

https://en.wikipedia.org/wiki/Comparison_of_free_and_open-source_software_licenses

* Free Software isn’t exactly a subset of Open Source. There are a few licenses which are considered Free but not Open: the original BSD license, CC0, OpenSSL, WTFPL, XFree86 1.1, and Zope 1.0.

Of course Microsoft implemented it “for Windows”.

The Mono project implements many of the .Net APIs in a portable way for other operating systems, including an implementation of WinForms on X11.

OP specifically mentioned that they were using Mono.

Mono has some docs that imply they have implemented WinForms on X11.

https://www.mono-project.com/docs/gui/winforms/

While the tone of the comment is dismissive, they have a point.

It’s not the engineers that are the problem, or even limited to the tech industry. Dark patterns are top-down business decisions, motivated by money.

It’s not that the “tech industry doesn’t understand consent,” but rather that greedy people do evil things. And software is just a low hanging fruit for that kind of business.

deleted by creator

Safety. Yes, Rust is more safe. I don’t really care.

I think this is honestly the crux of Drew’s argument.

If a compiler is to prove safety of a program in a language with low level memory management, then there is a lot of inherent complexity. Drew doesn’t like complexity, therefore Drew doesn’t like safety.

This is a really good doc for understanding the GCP APIs.

But don’t take this as gospel for your APIs. It works well for GCP, but it isn’t the only option.

Searching across repos was disabled for anonymous visitors in 2016.

Searching within a repo was disabled for anonymous visitors in 2023.