Honestly even the as-is directX with Wine is already quite good. With Vulkan, game over :-)
Honestly even the as-is directX with Wine is already quite good. With Vulkan, game over :-)
Switched to arch linux last november, didn’t had to launch my backup VM Win10 at all. I even managed to play at StarCitizen with better performance than under Win 10…
Just wow the progress of Linux, Wine & co since my last linux try (Ubuntu, around 2010).
I just need now to find a linux way for my music stack and all the VST (my steinberg usb card is recognized and play properly oO) and Windows will be history at home…
From me for example. I follow this studio and team since many years and i’ve participated to the funding of Divinity: Original Sin (DOS) more than a decade ago…
They got money from several sources but mainly because (or i should say thanks to) they delivered good products, they have being able to survive and work on BG3. Luck is not the reason, they’ve worked hard to achieve that…
Well, we could argue than having everyone in the same building is also a risk (traffic/weather issues could block all operators to come for example).
So having operators dispatched in several towns with probably multiple Internet providers could reduce this risk. In case of real big crisis, I agree it’s better to have everyone at voice reach, in the same room.
But, while a global internet outage could be a real risk for operators at home, having everybody able to join from everywhere can mitigate that.
And in case of a global internet disruption (another big risk that could happen), well classic mobile users would have also issues to contact 911 as lot of 4G/5G towers use internet instead of internally owned network to transmit our calls and data (the old copper landline disappear more and more).
Note that I agree with yours points too, their is pro and cons everywhere :-)
it’s even worse.
i could add also that he had a fire extinguisher hide in his pant (to be able to access the footage if the plane was still on fire i presume), the original motor was may be replaced before the crash, the plane door was not properly lock (to facilitate his jump)… ha and yes, he had a jumpsuit (no fitting a normal pilot activity)…
Well, all of that was badly done. He’s a piece of shit that should never flight again.
Was going to say that.
@OP:
One of the main skill a developer must have is being able to troubleshoot properly how their code behave.
Break your code in small pieces, check all of them with unitary test (formal or not) to validate their behavior then move to the next step. Never test everything in one shot or you will be overwhelmed by side effect bugs whom will distract you from the real root cause.
Being a programmer is not just coding but also testing and deploying (even locally).
That won’t avoid you being blocked by a silly mistake for hours, everybody did that at some point in their career, but that will reduce your frustration against yourself when you discover why the bug existed.
Do a pause, go walk, change the topic and the next time you look at your code, you will spot the obvious bug :-)