Typescript is Apache 2: https://github.com/Microsoft/TypeScript/blob/master/LICENSE....
Visual Studio Code is MIT: https://github.com/Microsoft/vscode/blob/master/LICENSE.txt
Typescript is Apache 2: https://github.com/Microsoft/TypeScript/blob/master/LICENSE....
Visual Studio Code is MIT: https://github.com/Microsoft/vscode/blob/master/LICENSE.txt
More on strong vs weak retaliation clauses here: http://www.rosenlaw.com/lj9.htm
Can't believe Microsoft is the good guy here.
Microsoft has always had "good guys/gals" at the company. They have been in action more the good guys then anything else minus Steve Balmer's anti-Linux bias over the years.
The MIT license is problematic with software patents.
I see some projects moving to Apache2 for that reason (one prominent example here is Rust. They moved to an MIT/Apache2 dual licensing model).
The MIT license grants explicit rights to deal in the software without restriction.
I could have found more, but its a big org. Any examples I found that used other licenses where that way because they where related to something else that used a previous license (i.e. all TypeScript stuff is Apache2, hence any new TS is still be Apache2 for consistency).
FWIW, my Android app's codebase has 18 Apache 2.0 dependencies, 1 MIT and 2 BSD. Maybe since the large libraries mostly use Apache 2.0, the smaller Android devs just follow suit?