Skillslinux, c++, lua, racket, lisp, embedded, js
Joined devRant on 2/20/2018
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Today, January 13th 2019, marks the one year anniversary of the initial release of DXVK.
Through DXVK, I've personally seen compatibility like never before with running Windows games on Linux. Some games which I had never been able to play on Linux before, games which tied me down to keeping a Windows desktop around - no longer bind me.
At the same time, today marks one year remaining for Microsoft's support of Windows 7 - which will be cut off at January 14th 2020. At which time those shackles would bind to a corpse.
I felt it appropriate to celebrate with a DXVCake!1
So I'm flabbergasted at the current trend of non-native Linux gaming becoming so stable and performant. In these past few months, I've witnessed stability akin to native support on games I had never expected to run well on Linux before.
DXVK had its initial release in January 2018, and so far every single game I've thrown it at has run so well that I forget it's non-native.
With front-ends like Lutris, it's easier than ever to get these non-native titles configured perfectly - to say nothing about what Proton offers for UX.
What will the 2nd year of DXVK bring? Extended Support for Windows 7 ends in one year - and I've never seen such stability and capability from Linux gaming parity.2
...because by the time I've finished my sentence the framework has changed.
Me: "It's a balance between three things: you either optimize for computation, memory use, or programming effort. Computers don't have a infinitely fast processors with an infinite amount of memory."
Coworker: "Did anybody tell Java?"3
That feeling when you need to use a scanner for the first time on your linux system, and it just works.2
*working on a programming assignment for a graduate-level course*
"We will provide you code that implements the protocol in the server. You do not need to touch this code."
*provided file has syntax errors, including a block comment which doesn't close before EOF*1
I hope that when I wake up in the morning, the racket code I just wrote from midnight to 3am makes as much sense to me as it does at the time of writing.
Banana Language always seems to flow easier when exhausted.