DacoTaco

I know, hence why i said youre not wrong but the example was wrong :p
Also, its more complex than that. Some teams can, some cant. And if they can it all depends on what project or context. The business world isnt that cut and dry hehe

Not saying youre wrong, but you took the wrong project as an example hehe.
Visual code is not open source. Its core is, but visual code isnt. The difference is what visual code ships with, on top of its core.
Its like saying chrome == chromium ( it isnt ).

Visual code comes with a lot of features, addins and other stuff that isnt in the core.
.net debugger for example, is not found in vscodium ( build of the vscode core ). And there is more stuff i cant think of now but have come across. Source: been using vscodium for a few months instead of vscode

Fair, and ill edit my post accordingly!

There are teams that are allowed, and within those companies are teams that are directly related to foss projects because those companies are in the foundation or supports of the foundation. However, thats doesnt mean every (product) team in the company is allowed to or that they can do or change whatever they like. Its a complex mess

Thats just dual booting. That wont work with the law if the contract says anything created using company hardware is theirs.
And yes, some companies need to give you a green light to work on projects in your free time, because they might have a team doing similar things somewhere, it might compete in something they would like to do in the future or like you said, might use company know how which is a huge nono. Its bs imo, but those clauses and rules are found in some employment agreements.
Remember, always read your employment agreements!

Yes, but not all devs within microsoft are allowed to work on non-ms foss projects. I assume wsl devs are allowed to send stuff to linux but visual studio devs probably are not.

And not every team is allowed to do that.
Also, youre telling somebody who has worked with big companies not allowing it in their employer contract that he is lying? Riiiight...
A lot of google devs also are not allowed to do any linux work outside of work without explicit permissions because of all the internal docs, teams and other work being done on linux from within google. Development rights is an absolute mess, legally.
I usually dont care and do what is right, despite what my emploter contract says, but i have gotten in trouble for it

Thats an excuse of an argument and you know it. Things like yuzu and cemu had no reason to turn a profit like they did for what they had. The devs were fine and yet they did what they did. And on the other end of the spectrum there are homebrew devs that need money ( and i donate to ) but dont sell their stuff because its better free.

I never tried to make a profit out of priiloader or any of my successful free projects either, despite wanting more money sometimes.

There is a difference between a product and a project.

This.
Let alone those tools can be used from within nintendo, and have been in the past.
As somebody who helps manage a part of homebrew tools, im totally fine with that. Means they did something right and it means nintendo wont just shut it down and believes it is useful too. So good job on you then!

Now if they used some ip, or copyrighted code, in the tools, then its game over. Instantly.

This story sounds familiar. Plague tale? Pied piper of hamelin? Its really familiar lol

Everything after w7, id agree. Windows 7 was actually legit. It ran fine on my amd athlon with 512MB ram. Ran dolphin back in the day too. Now after that it was all shite

Most of what i know is from year and years of working on the console and are found on wiibrew.org haha