DacoTaco @ DacoTaco @lemmy.world

The real deal y0

---

Read more

Posts

2

Comments

574

Joined

2 yr. ago

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

I agree they should have sent a patch to the grub source, but keep in mind big software companies like microsoft, Verizon, ... do not normally allow their product teams to send a patch or PR to open source projects. This is because in their contract it states that all code written on and during company times is owned by the company. This means that it is impossible for them to make a patch or PR because it would conflict with the projects licence and fact its open source.
This changes when the team explicitly works on the foss product/project like the ms wsl team or the team working on linux supporting azure hardware, but that is an exception. I do not believe the microsoft kernel/bootloader team is allowed to send patches to grub.

Its a terrible thing, and it shouldnt be, but thats the fact of the world atm.

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.

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

And not even continuous ram! The wii had 2 bits, 24MB fast memory ( mem1 ) and 64 MB of slower memory (mem2) haha

Except he is. He lives in portland now afaik

Yes, but in reviews the handbrake benchmarks didnt even get close to the 40% amd claimed

Youre confusing comparison of os' with hardware reviews. It makes no sense to use an arch benchmark for a public is majority windows based gamers. The arch benchmark would make sense for a journalistic piece about windows having terrible performance.
Hence why id love for gamers nexus to investigate this using a linux to windows comparison for the same task. However, this would no longer have anything to do with zen5

But the numbers would mean nothing for the consumers. You abstract away too much and reduce it too far for anyone outside the loop to make sense

This is... Interesting. I would love for gamers nexus to investigate this tbh. Means something is horribly wrong in windows ( shown by the wtf steps reviewers had to go through ).
Im also curious at the performance uplift of zen5 in linux in regard of handbrake. Amd claimed a 40% uplift there which i guess might have been in linux and with a very specific clip?

In the usb world its "host" and "device", not "master" and "slave".
But yes you are right

Same, afaik it was a case of not rendering correctly and in all versions since they just went with it. Cant find a source though...

Euh, sword art online s2 exists haha

Haha ye. It is super interesting to see all those OS principals and seeing how nintendo implemented them. Stuff i will never forget either and some design patterns i have implemented in my actual job too

I have. Mostly on embedded devices that have no OS and you need something very specific.

... Or that one time i was reverse engineering a console kernel. I wrote arm asm then. Was actually fun to do tbh