NekuSoul

My current toolkit (as a 3D printing hobbyist) on Linux currently includes:

• FreeCAD: Takes some getting used to, is a lot stricter, but that might even improve your CAD skills in the long term, as it forces you to think more about what you’re actually doing. The closest thing to Fusion360.
• OpenSCAD: You’re basically programming your models. Very powerful if you need parts with repeating sections and/or want something with easily adjustable parameters.
• Blender: Useful when I have to do some quick&dirty modifications to a model I’ve downloaded from somewhere.

Fun fact: Mario Kart 8 released more than a decade ago and is still the most current one. At least for a few days.

Good catch. Never used Remote Assistance, so I don’t know how different it is, and if it actually requires telemetry.

Although the broader issue isn’t the why, it’s that it does those things at all without clearly communicating them to the user. Even their documentation has severe lack of any kind of explanation.

I thought so as well for a time, but that tool in particular is what finally made me lose faith that there might be any good debloat tool out there.

Basically, someone mentioned that it does a weird thing, so I’ve decided to take a look closer, and stumbled about a whole lot of dumb choices. To exemplify, I’ll just repost that part of my comment from back then:

Oh yeah, I’ve just skimmed what else the “Disable Telemetry” script does to the registry, and I honestly can’t classify it as anything other than batshit insane.

A few highlights:

• The popup delay of nested context menus and mouse hover popups
• Disables the prompt when there are open programs when shutting down
• Switches the explorer from the default view to This PC
• Enables long file paths
• Expands the file copy dialog by default
• Straight up disables RDP???

And this is only one script out of a few dozen this “tool” has. Not to mention this is listed under “Essential Tweaks” that are, according to the documentation “Essential Tweaks are modifications and optimizations that are generally safe for most users to implement.”

Problem is, there are no good debloat scripts. It’s all written by amateurs who don’t know what they’re doing, messing up the system in subtle ways that then take ages to figure out.

I’m sorry, but if you see a 25% difference in a benchmark, that means your methodology is somehow flawed. A few percentage in either direction would be believable, but this difference would be so comical if true, that extra wariness is needed.

There’s a few thing that look a bit off to me, but most importantly it seems like your OBS settings are wildly different between systems. It’s a bit hard to make out, but it seems like you’re doing CPU-based encoding on Linux and GPU-based encoding on Windows.

I don’t know of any report, but just like the first one it’s still using Unity, so I wouldn’t worry from a compatibility perspective.
That said, the performance is apparently pretty bad, so if you care about that the experience will probably be awful on any OS.