myersguy

Reasons are usually just newest kernel/mesa/etc. Most of the time the difference is very small, and often inconsequential. However, every now and again there is a major development that might make it worth it (IE: The graphics pipeline that all but made dxvk-async obsolete)

I see you all over this thread and I want to share something you might find interesting.

You keep mentioning the server can't handle the anti cheat because it needs to trust client data. Here's an interesting thought: how is client anti cheat supposed to work when it needs to trust input data?

Look up direct memory access cheats. TL;DR Two computers are hooked up such that PC 1 runs the game, PC 2 reads memory from PC 1, and can then output keyboard/mouse inputs, as well as wallhacks/esp. How is the client side anti cheat supposed to know that the keyboard and mouse inputs are legitimate? How is the client side anti cheat to know wallhacks are being used when they are being rendered on an entirely different machine?

As a C# developer on Linux, I wish this was more true than it is. Working on a multi project dotnet solution in VSCode is still far behind Visual Studio / Jetbrains Rider.

Its also worth pointing out that the more you add to VSCode, the slower it becomes. If you add the toolkits to make it compete with Jetbrains products, it isn't nearly the same lightweight editor anymore.

Won't speak to Webstorm, but hard disagree when it comes to Rider. VSCode/Zed really fit into an entirely different category from Jetbrains IDE's. Lightweight editors vs full fat development environments. There are use cases for each.

The truth about abs workout and diet is the same order tonight and tomorrow is fine but most importantly I will send you the best way to get the latest Flash player to play with my family 😁🐱

The plugins would almost certainly work in a VM, but I imagine that latency would become a big headache. For my purposes, I picked up a Beelink mini pc and called it a day.

So in terms of DAW (Digital Audio Workstation), Linux already has Bitwig, Reaper, Arour, LMMS, and possibly others. Personally, I find the bigger issue comes from plugin developers (the DAW is your main program, and you add your sounds/effects through plugins). Most companies are not delivering anything Linux native. Many of these plugins can be bridged with compatibility software, and will work fine that way. However, most of these plugins now are also using their own install/activation software center, and they are often a nightmare in Linux.

Music production is the one thing I currently keep a windows mini PC around for these days. It's not impossible to make the transition to Linux, but the last thing I want when pursuing a creative endeavor is technical software challenges holding me up.

You can say that speaks volumes about the character of the author (though you are the one assigning said "shame"). You were asking why this report deserves credence. The points raised in the report have citations such that you can decide where you fall on the presented issues.

It looks pretty well cited to me. The fact that it was written anonymously doesn't really take away from that.

I agree, but you could have posted the link with your comment, no?

90% sure wireguard (the VPN server) is going to need an open port if you want to connect from the outside.