MrXeno

Yeah that's a concern as well. but i can always use a pci-e riser and move it around, might just be more janki bu i can make it work.

Thanks for posting this comment, always good to have both sides of a story to make sure you get it all.

I fully respect this comment and your work at LMG plus the whole team at LMG does do great stufff. 
I can see how the videos are better made and it is going the right way forward. 
I look forward to see how the Labs will come and what content they will release.
 
Love your work and the work LMG does as a whole.

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.

So I have given Linux to my girlfriend which is a windows user and gave her ubuntu, which she found super easy to use (The KDE Version). The only thing I had to do was to enable nvidia's shitty drivers. Beside that she didn't have any issues using Kubuntu at all. She has never touched the CLI at any point and I haven't had to do any support for it at all. Everything just "works" out of the box. My experiance with Ubuntu is good but I am a linux user from the start. I first started using windows back in WIndows Vista (nightmares are coming back)
 
For you OP I would recommend either Linux Mint or Kubuntu as they have solid support for most hardware. If you are willing to pay for it I would say go with a Red Hat official version as that is rock solid 99% of the time. And yes I learned linux / unix BEFORE windows and I rarely touch the CLI now days. Only if I break something by modding something but that is my own fault lol

1. Power bill, I don't game more then maybe 2 hours a day out of 6 hours in total of my free time
2. I upgrade my gaming machine far more then I upgrade my ubuntu machine which gets an upgrade every 4-6 years give or take

My ubuntu machine is something I always use for my everyday stuff like banking, office work, IT hobby etc so I rarely upgrade it and i need it to always works which is something I don't see with a VM when the host breaks I need to setup a new VM host for it which is more work then I want to deal with. 
 
If i wanted to run it in an VM style I would throw it on my proxmox server with a small gpu pass through and call it aday. I just don't like VM's for everyday machines. For services its fine and perfect just not for everyday compute work (If you ever have had to deal with Citrix you know the amount of pain there is to this)
 
I do run my Arch in an VM as I tend to break it alot when learning lol

What UEFI Secure Boot protects is the part of the boot process that comes after loading your motherboard's firmware. It ensures the integrity of the UEFI images your motherboard hands the system over to after you select a boot device. Those UEFI images are typically a piece of software called a bootloader, but they can also be an operating system kernel that boots directly, without using a bootloader. Those files mentioned in the instructions you linked, e.g., loader.efi and systemd-bootx64.efi, are UEFI images.

Turning on UEFI Secure Boot just means that your motherboard will refuse to boot UEFI images which are not cryptographically signed by some trusted key. The idea is that whatever party (e.g., Microsoft, Red Hat, Canonical) builds your bootloader and operating system kernel marks it with a secure seal which says ‘I made this, and this how I intended to make it’. If an attacker tries to modify or replace your bootloader, they'll be unable to reproduce that seal (cryptographic signature) because they don't have your OS creator's keys, and so the motherboard will say ‘wait a minute, this is unsigned!’ and refuse to boot the bootloader that has been tampered with by the attacker. Similarly, when you enable secure boot on most Linux distributions, the kernel then enforces the same kind of signing for all kernel modules, so the operating system will, for example, refuse to load unsigned drivers.

systemd-bootx64.efi is the bootable UEFI image for systemd-boot, which is the bootloader Pop_OS uses to load Linux. Systemd-boot is the program that presents you with a boot menu so you can choose whether to boot in failsafe mode or whatever. Your motherboard loads it, then it loads the Linux kernel. The mucking about these instructions have you do with this file is something that lets you sign those files yourself.

All of that is to say: Secure Boot is about ensuring the integrity of the lowest-level parts of your operating system, not your motherboard itself. It doesn't protect your motherboard, and in fact if your motherboard were infected with malware, that malware could probably covertly disable or bypass your Secure Boot configuration.

 
 
If Secure Boot is important to you but you're still kinda getting your feet wet with the command line and you're not comfortable following written instructions using the terminal, you should consider using a Linux distribution that supports Secure Boot natively. Boot systems can be tricky, and when they're misconfigured it really sucks, because then you can't boot your damn system.

Fedora and openSUSE both support Secure Boot out of the box. Maybe give each a try and go with whatever you think looks the best or has the most active forums (or whatever— both are good).

I am moving over to Flatpak as programs like Spotify has already moved over there permanent now. Flatpak seems easy to use so no big issue there.

It seems to work fine for my need. I have just changed it to flatpack as most of the programs I need has a flatpack version
I generally just need something that works and doesn't require me to do a lot of terminal work for day to day use
 
When it comes to xfc, mate etc. I generally don't like them because of me not being use to them. I was one of the few that liked Unity interface for Ubuntu. But gnome does most of what I need and has a easy UX/UI flow
 
I generally don't care about if the package is snap or flat. Just need to work pretty much
 
The main reason I went with Pop!_OS for the next week is because of pre-installed nVidia drivers so less work for me

Well I'm giving Pop!_OS a try (seems to be working some what fine but some stuff is broken like the bottom bar)
and if Pop!_OS doesn't do it for me I will give Ubuntu a go or Kubuntu. Heck I might even Mint a go again after these many years

Just for your info I run a Core i9 10900KF and a RTX 3090 in Ubuntu and it all just works nicely.

Ah oki yeah that makes sense. I need to learn Docker first but it shouldn't be to hard just takes time really. 
I will look into that thanks!

yeah i saw that, i will for sure look around and see what is there. thanks for the reply