Display_Name

Thanks for the quick response as always but I'm not sure that the message of the video is fully explained here (I hope you didn't just read the comments, jk :D)
 
What I would really like to know is why data driven content doesn't get the time to add the seemingly required polish given it's a pain point raised by many of the LMG Team and are there any plans to address this from a production standpoint?

Thanks for the quick response as always but I'm not sure that the message of the video is fully explained here (I hope you didn't just read the comments, jk :D)
 
What I would really like to know is why data driven content doesn't get the time to add the seemingly required polish given it's a pain point raised by many of the LMG Team and are there any plans to address this from a production standpoint?

Thanks for the quick response as always but I'm not sure that the message of the video is fully explained here (I hope you didn't just read the comments, jk :D)
 
What I would really like to know is why data driven content doesn't get the time to add the seemingly required polish given it's a pain point raised by many of the LMG Team and are there any plans to address this from a production standpoint?

Thanks for the quick response as always but I'm not sure that the message of the video is fully explained here (I hope you didn't just read the comments, jk :D)
 
What I would really like to know is why data driven content doesn't get the time to add the seemingly required polish given it's a pain point raised by many of the LMG Team and are there any plans to address this from a production standpoint?

Thanks for the quick response as always but I'm not sure that the message of the video is fully explained here (I hope you didn't just read the comments, jk :D)
 
What I would really like to know is why data driven content doesn't get the time to add the seemingly required polish given it's a pain point raised by many of the LMG Team and are there any plans to address this from a production standpoint?

There won't be a big WAN Show segment about this or anything. Most of what I have to say, I've already said, and I've done so privately.

To Steve, I expressed my disappointment that he didn't go through proper journalistic practices in creating this piece. He has my email and number (along with numerous other members of our team) and could have asked me for context that may have proven to be valuable (like the fact that we didn't 'sell' the monoblock, but rather auctioned it for charity due to a miscommunication... AND the fact that while we haven't sent payment yet, we have already agreed to compensate Billet Labs for the cost of their prototype). There are other issues, but I've told him that I won't be drawn into a public sniping match over this and that I'll be continuing to move forward in good faith as part of 'Team Media'. When/if he's ready to do so again I'll be ready.

To my team (and my CEO's team, but realistically I was at the helm for all of these errors, so I need to own it), I stressed the importance of diligence in our work because there are so many eyes on us. We are going through some growing pains - we've been very public about them in the interest of transparency - and it's clear we have some work to do on internal processes and communication. We have already been doing a lot of work internally to clean up our processes, but these things take time. Rome wasn't built in a day, but that's no excuse for sloppiness.

Now, for my community, all I can say is the same things I always say. We know that we're not perfect. We wear our imperfection on our sleeves in the interest of ensuring that we stay accountable to you. But it's sad and unfortunate when this transparency gets warped into a bad thing. The Labs team is hard at work hard creating processes and tools to generate data that will benefit all consumers - a work in progress that is very much not done and that we've communicated needs to be treated as such. Do we have notes under some videos? Yes. Is it because we are striving for transparency/improvement? Yeah... What we're doing hasn't been in many years, if ever.. and we would make a much larger correction if the circumstances merited it. Listing the wrong amount of cache on a table for a CPU review is sloppy, but given that our conclusions are drawn based on our testing, not the spec sheet, it doesn't materially change the recommendation. That doesn't mean these things don't matter. We've set KPIs for our writing/labs team around accuracy, and we are continually installing new checks and balances to ensure that things continue to get better. If you haven't seen the improvement, frankly I wonder if you're really looking for it... The thoroughness that we managed on our last handful of GPU videos is getting really incredible given the limited time we have for these embargoes. I'm REALLY excited about what the future will hold.
 
With all of that said, I still disagree that the Billet Labs video (not the situation with the return, which I've already addressed above) is an 'accuracy' issue. It's more like I just read the room wrong. We COULD have re-tested it with perfect accuracy, but to do so PROPERLY - accounting for which cases it could be installed in (none) and which radiators it would be plumbed with (again... mystery) would have been impossible... and also didn't affect the conclusion of the video... OR SO I THOUGHT...
 
I wanted to evaluate it as a product, and as a product, IF it could manage to compete with the temperatures of the highest end blocks on the planet, it still wouldn't make sense to buy... so from my point of view, re-testing it and finding out that yes, it did in fact run cooler made no difference to the conclusion, so it didn't really make a difference.
 
Adam and I were talking about this today. He advocated for re-testing it regardless of how non-viable it was as a product at the time and I think he expressed really well today why it mattered. It was like making a video about a supercar. It doesn't mater if no one watching will buy it. They just wanna see it rip.  I missed that, but it wasn't because I didn't care about the consumer.. it was because I was so focused on how this product impacted a potential buyer. Either way, clearly my bad, but my intention was never to harm Billet Labs. I specifically called out their incredible machining skills because I wanted to see them create something with a viable market for it and was hoping others would appreciate the fineness of the craftsmanship even if the product was impractical. I still hope they move forward building something else because they obviously have talent and I've watched countless niche water cooling vendors come and go. It's an astonishingly unforgiving market.
 
Either way, I'm sorry I got the community's priorities mixed-up on this one, and that we didn't show the Billet in the best light. Our intention wasn't to hurt anyone. We wanted no one to buy it (because it's an egregious waste of money no matter what temps it runs at) and we wanted Billet to make something marketable (so they can, y'know, eat).
 
With all of this in mind, it saddens me how quickly the pitchforks were raised over this. It also comes across a touch hypocritical when some basic due diligence could have helped clarify much of it. I have a LONG history of meeting issues head on and I've never been afraid to answer questions, which lands me in hot water regularly, but helps keep me in tune with my peers and with the community. The only reason I can think of not to ask me is because my honest response might be inconvenient. 
 
We can test that... with this post. Will the "It was a mistake (a bad one, but a mistake) and they're taking care of it" reality manage to have the same reach? Let's see if anyone actually wants to know what happened. I hope so, but it's been disheartening seeing how many people were willing to jump on us here. Believe it or not, I'm a real person and so is the rest of my team. We are trying our best, and if what we were doing was easy, everyone would do it. Today sucks.
 
Thanks for reading this.

Buy a new key switch. They cost like 5$ on laptopkeys or replacementlaptopkeys

You have to unlink your LTT forum account from floatplane then you'll have the option to subscribe on floatplane.  Once your sub is purchased relink your LTT forum account.
 
 

I would get a Gear S3.It's one of the best ones out there.
Is the watch supposed to be a tech item for you or a fashionable timepiece

i got an LG Watch Style with my G6 and its pretty nice, but it has no heartbeat sensor which is a real bummer. other then that its pretty good, not that i have any experience with smartwatches though. display is bright, good size, battery life way beyond a day of usage and i havent noticed any slow downs or hanging with it either. probably not your best option but its not a bad one at least

A lot of people are getting pissed off (for good reason) that Linus is not treating AMD products fairly. I know, it sounds stupid, and I used to agree - but there's some really notable things here. He isn't specifically bashing AMD but sort of pretending they don't exist, or pushing their tech under the rug.
 
In the last week or so of videos, 3 things have stirred up controversy. The previous WAN Show ignored one of the biggest topics of the week, AMD's yearly major driver update, until after the outro (at which point it was half-arsed to say the least). The review of a Korean 100Hz FreeSync Curved Ultrawide monitor was done with an Nvidia GPU, there were 2 complaints about tearing and FreeSync was only acknowledged when reading the title of the product (and a terrible excuse was in the comments). In the most recent WAN Show, AMD's event showing a huge amount of Ryzen details and some Vega updates was discussed by mostly mocking the name and then talking about Thunderbolt in the new MacBook. 
 
There's a point where it just seems like some obvious avoidance of AMD products. Even if this is not deliberate, this sort of reporting is misleading - I'd hate to see the next 'fake news' debacle involve LTT. I'll elaborate on the 3 examples from the past week below with links and timestamps. Of course, on their own these aren't too significant, but considering there are now 3 examples in the last week that have got quite a few concerns, it's worth mentioning.
 
1. WAN Show ReLive: https://youtu.be/7oEpez1ruis?t=1h8m11s
This update is AMD's yearly major update and a very good example of a discussion worthy topic for the WAN Show. They added a much better built-in zero-overhead recording thing (and separated from Raptr), added WattMann support to older cards and more. The show had quite a few questions about it in the Twitch chat. They were acknowledged after the outro, at which point Linus just mumbled some specs from the download page and ended with "There ya go, now we covered it." Watch the segment, it's the most half-arsed coverage of anything I've ever seen.
 
2. Cheap Korean Curved Ultrawide Monitor: https://www.youtube.com/watch?v=0vvdvjralvs
This one is possibly the most damning. In this video, he takes a FreeSync monitor, says "You don't get the tearing resistance of GSync" (1m55s), uses an Nvidia GPU to test it (5m07s) and complains about tearing (5m50s). I've not facepalmed so hard in a while. Then in the comments, there's this lovely post: http://prntscr.com/di7bl9 Here he says no AMD GPU can run 100FPS on AAA titles so he wont and reviewed the monitor as if you used an Nvidia GPU with it. I shouldn't have to explain why this is bad reasoning (and why this should be explained in the video), but FreeSync is useful from 45FPS on this monitor, it offers higher refresh rates at lower resolutions, Furys can run games such as the tested CS:GO at that res no problem (which is what most people want them for) and there are countless other options like reducing the settings a little or just not running at 100FPS while testing that part of the monitor. It's also very clearly a monitor review, so he should test the features of said monitor, particularly since one would pair a cheap GPU with a cheap monitor. It's just such irrelevant reasoning, and there was a lot of flak for that given in response if you care to find the thread. 
 
 
3. WAN Show RyZen: https://www.youtube.com/watch?v=k6Hugyu2CME
In this video, he starts by covering the basics of Ryzen in the event which is fine, and then goes on to discuss the use of Thunderbolt (since it's an Intel-exclusive tech) and where it could be useful. I assumed at first the event would be returned to, but they moved straight on from it. There was no time given to discuss it, no mention of Vega, no mention of the surprisingly in-depth benchmarks they gave. The dislike bar shows this, as well as the top comments. This topic is by far the biggest of the week, but it was also glossed over and had an irrelevant Intel technology made the focus (as with GSync in 2).
 
I really like this content, but please, start covering AMD products fairly. It's pissing off quite a few of your viewers and preventing you from being considered a trustworthy source. The comments on YouTube are filled with people annoyed about this. The thread for #2 is also filled with complaints: https://linustechtips.com/main/topic/704937-microboard-korean-curved-ultrawide-100hz-gaming-monitor/?page=2 There was also a thread on the front page of r/PCMasterRace with some good discussion: https://www.reddit.com/r/pcmasterrace/comments/5hscps/linustechtips_has_been_showing_a_concerning_bias/
 
 
 
 
 

How can you roast NVIDIA fanboys?
 
Lock them in a case with an R9 390X.

Mine is a three way tie between - 
2015 Macbook Pro IE80's at 50% off Box of Kleenex next to my desk during this cold