wanector

@SorryBella @Spotty Thanks for the info!!

Linus' shortcircuit unboxing of the Whale PC for LTX 2023 was really fun. What was the OEM base case used for that starforge PC?

I am looking for a traveling gaming set up and I am so glad framework is making a "gaming" laptop. My wishlist is an RTX 4070 to compete against the Asus Zephyrus GU604

Who are these people calling in?! Was this a random tech support line they got access to? were these friends of LTT? NVM, seems like there was a tweet asking people to participate on the challenge

You are right about consistency. Once I have gotten used to a mouse, the feel of any other mouse is a bit off or wrong. This kind of data is a chance to understand how off a mouse really was. If lets say you want to change to a different mouse, you can confidently know what the difference would be, and be prepared for it. I have the G502 wired, but a family member has the G Pro SuperLight. It felt light and really smooth, but my brain couldn't really tell what really was different between the two. Without bringing my mouse over and match my own settings, its hard to tell exactly non-subjectively how they perform side by side. Or simply buy it and try it out.

I was watching Optimum Tech's video on DPI drift and the level of detail and analysis was top notch. He used a setup that accurately and repeatedly tested the DPI drift at 800 and 1600 against popular wireless mice on the market. Its such a good video. But, apart of me wished he would have compared it against popular wire mice, or at least at more DPI levels. I use 1200 DPI, and I selfishly wished he included that. I am not sure what priorities the LTT Labs teams are focusing on, but I would like to put my vote on this kind of data. Mice have such subjective marketing and I feel data like this would help clear things up.

I can see migrating from an SDR to HDR workflow to be very expensive and major work-stoppage, especially with large channels like LTT. For smaller groups, ripping the bandage early would be risky if it cost too much, but great learning opportunity and investment in "future" increasing readiness in their workflow. If I were to start a youtube channel, I personally would like to dive head first into HDR as a learning opportunity.

I just checked GPU-Z and I have memory temp! yay. I got the EVGA 2070S

I just watched the NVIDIA, this is NOT ok! video and I've not thought about my GPU Mem temps ever. Last time I removed my GPU for cleaning, the back plate was VERY HOT. Im concerned I am hurting my GPU so I was using my usual apps to find the GPU Mem Temps. Unfortunately, HardwareInfo64 (HWiNFO64) nor MSI Afterburner provides graphs on the GPU Mem Temps. Does anyone know what apps would provide these measurements? Does anyone know what app they used in the LTT video?

On April 16th WAN show, I noticed a significantly better video quality coming from Luke's feed. I found a LMG Clip of Linus comment on how Luke finally upgrade to a better web cam set up, but I could not find details of the upgrade itself. Does anyone know what Luke upgraded to? His twitch still has old computer details, but nothing about his cameras

original reddit post:

Reddit has picked this up. Some of them have screen grabs of the mess.

Microsoft has shut down all new issue creation on VSCode's repo because people were not being nice, "violating community guidelines".... Unfortunately for those just tuning in, the original community response has been deleted, so are all the other funny response issues.

Microsoft's open source text editor, vscode, came under fire morning of Dec 19, 2019 when user "Christian-Schiffer" made a github issue declaring the santa hat was offensive to Jews and should be removed. Microsoft engineer "kieferrm" apologized and removed it the next day. However, majority of the community members disagreed with that action and wrote responding issues to appeal that decision. vscode issue tracker on github is all messy now. Original issue: https://github.com/microsoft/vscode/issues/87268 Community response and other retaliation issues on their github repo: https://github.com/microsoft/vscode/issues/87291