The thing that bothers me the most here is that the meme is using 64bit assembly instructions, which did not exist at the time keyboards were using IRQs to communicate. 🤣
fulg
For me what ended up being an important difference is that Remote Desktop is a screen share in KDE (meaning it only works if you’re already logged on, everyone sees what you are doing and the remote view does not adapt to the monitor you’re connecting with). In Gnome it is a real private remote session with virtual monitors.
I am told something like NoMachine will solve this on KDE but I haven’t set that up yet.
Agreed, what Bambu did is essentially steal the work of everybody and close it up, and go against anyone trying to reopen it.
To be fair though, the reason Bambu Lab printers work so well for most is in large part due to the walled garden approach.
I still disagree with it and will vote with my wallet by avoiding them, but I can see the appeal if you don’t know any better (or just don’t care!).
Prusa kind of tries to navigate both sides of the issue (not everything is open source anymore), so you can still get caught there.
They were running ZFS software raid. So ... maybe just use the raid controller instead?
It is generally a bad idea to do that nowadays, because it ties you forever to that controller. If it dies you will need to find an exact replacement or accept that the whole array is lost. With software raid you can run any hardware.
Wendell from Level1Techs is a good reference:
https://youtube.com/watch?v=l55GfAwa8RI
https://youtube.com/watch?v=Q_JOtEBFHDs
BTW: good score, you will have fun with those for sure.
That and the game can flag frames that are too different (camera cuts) to mitigate this problem.
What the game supplies is the current frame + motion vectors, but the framegen bits take over how the frames are displayed onscreen. This is where the extra latency comes from, at worst you are seeing one true frame behind what the game is rendering, while the presentation layer generates the intermediate frame(s).
That is not strictly true, the actual latency increase is half the original frame rate. Because the input is not just the frame image but also the motion vectors (in which direction the pixel moved) for the current frame. Frame gen also knows a lot about the image, like which bits have transparent pixels (which move in multiple directions at once) and when the game is done with the frame yet still has to wait for the GPU (time which can be used for more work with little impact).
Frame gen is much more involved than the old “motion smoothing” of televisions, the so called “soap opera” mode, which did increase the latency much more and had no knowledge of how the source image was built, so processing was much more involved.
Stuff like DLSS5 is supposed to use the same inputs (source images and motion vectors), now that is magic to me.
Yeah that’s why I found an “evaluation” version before. Once I saw it was genuinely great I was happy to pay for a license.
I look at this font 12+ hours a day everyday for work, if this was just for ricing a terminal window I agree it is a bit steep.
I am a big fan of MonoLisa, but it is a paid font.
I wasn’t convinced initially (never paid for a font before!) and found some version of it online, found that I liked it very much, then willingly parted with my money for a license.
I really like the difference between normal and italics, I set up my code editor to use italics for comments.
Don’t dead open inside!
Unfortunately be aware that there are 2 types of cheap replacements, some are identical to the real thing and some are really cheap foam that is nowhere as comfortable. I don’t know how to tell the difference without ordering…
I stand corrected then, thank you! I forgot about Opteron and Athlon (I was an Intel devotee at the time, my AMD phase happened much earlier with the 486 DX2 and DX4).
Cheers!