Dota was always going to be f2p, and maybe you could buy the beta access, but I, like many others, never paid and just got invited. So I would not consider it to be a paid game going f2p

Which ones ? Apart from CSGO, the others have always been free (on the technicality that Fortnite BR is different from the original game)

(sorry I took some time to come back to this) I’m not entirely sure the #5 of OSD would apply to the binary results (even though they are considered derivative work). GPL does restrict the license of the binary, but it seems MPLv2 allows licensing the binary differently as long as you don’t restrict the code further:

You may distribute such Executable Form under the terms of this License, or sublicense it under different terms, provided that the license for the Executable Form does not attempt to limit or alter the recipients’ rights in the Source Code Form under this License.

How can Firefox not be open source if its sources are under the MPL2 ?
It has always been the case that Firefox is a trademark and you can’t distribute it under that name. However if the code is open source the project is too.

Or work together and do the job in half the time and enjoy the rest

The north and south will make contradictory statements about it and the federal decision will be somewhere in between

I mean for privacy things it makes sense to avoid leaking anything. But I fail to understand where the danger is to have anonymous data that says a user installed “Ubuntu-24.04-wappity-whatever.iso” to “KINGSTON DATA TRAVELER 32GB” at some point.

Thanks for taking the time to explain it. Indeed the new runtime method does not guarantee when the resource will be cleaned, so something like that Drop trait would be quite useful

Not sure if that’s what you are referring to as destructors, but they added a new way to have code run at resource collection in go 1.24

For Android tv there’s also Smart tube next

Initially read that as you were talking about the physical windows keyboard key and was quite confused

Go had the same behavior until recently. Closures captures the variable from the for loop and it was a reference to the value.
They changed it because it’s “common” in Go to loop over something and run a goroutine that uses the variable defined in the loop. Workaround was to either shadow the variable with itself before the loop, or to pass the value as an argument.
It’s been a long time since I wrote c# so idk if the same is expected from the avg dev, but in Go it’s really not explicit that the variable will be a reference instead of a plain value

In my experience, they really don’t stick together. They stick enough to print, but if you exert pressure on the part they will delaminate.
It works great to print the support in Petg, and the part in pla (or the reverse)