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.
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.
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.
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.
The main thing is mostly about protecting your data from flawed implementations. Like, AES has not been broken theoretically, but a particular implementation may be broken. By stacking implementations from multiple vendors, you reduce the chance of being exposed by a vulnerability in one of them.
That's way overkill for most businesses. That's like nation state level paranoia.
Yep. This fucking loophole in the American tax system.
You borrow against your existing wealth, then the cost basis of your investments resets upon inheritance. So your estate can sell the investment to pay off the debt, and no capital gains tax is ever paid.
Because of this, in America, capital gains tax only applies to the middle class. The rich have a clear and obvious loophole.
multiple time the sum of the wealth of all the top 10 richest individuals on earth???
Do you mean the $78B fine or the $300B debt?
In either case, you're way over exaggerating. All of the top 14 wealthiest people have over $100B each. Jeff Bezos (#2 richest) has close to $200B alone.
Even if they were such a thing as a cookie banner law, and there is none, companies in the USA would not have to comply in their country.
It would be only for Europe.
This is a pretty naive take.
If you operate in Europe, you must comply with GDPR. To selectively show a cookie banner, you have to be able to identify the (location of) the user.
It is totally reasonable for a company to operate in Europe but not wish to implement a full identity or location detection system. And so they just show the opt-in prompt to everyone.
And you can't just implement that by using the browser's location API, because European users can totally choose to not share their location with you using that API. But you still need to comply for those users.
There has been for years a proposal for a standard, designed in 2009 (!), still available in all the popular web browsers (except safari) that can make for a seamless experience: the DNT header.
The diversion about the DNT header is irrelevant.
Firstly, it is not codified in law that the DNT header is canonical. What if a user forgets to check the box? What should the default be? What kind of UX should be presented to users? This stuff needs to be spelled out in law for DNT to be a valid way to express opt-in.
Secondly, it's not a robust per-site permission. Browsers only let you set it globally.
Thirdly, it's actually bad for privacy. By making your headers different from the majority, you are easier to fingerprint. This is why Safari does not implement it.
Be mad at companies
I get the spirit of the article.
But the GDPR has pushed the problem of consent to the users, and they haven't done anything to make this easy or convenient. Therefore cookie banners are inevitable. Like, you can't blame companies for acting in their own self interest; that is entirely counter productive.
The EU needs to solve this.
First, go after the data brokerage industry so that it is no longer profitable to sell user data.
Second, regulate how websites can seek permission. Ideally by specifying a consent API and requiring browsers to implement a sane UX.
It will be much more productive to try to solve this with the handful of Browser vendors than trying to regulate each and every consent banner.
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.