280 karma · joined November 19, 2017
> Wi-Fi and Ethernet clients are equivalent peers on the LAN. > Wi-Fi and Ethernet clients aren’t equivalent peers on the LAN.
To be honest I don't know what this is supposed to be telling me. They can or can't be on the same VLAN? They could have different or the same QoL? If we hammer traffic on both at the same time bad things may or may not happen?
> Only IPv4 is running on my LAN. > Only IP is running on my LAN. > Okay, only IP, IPX/SPX, Phase IV, AppleTalk, VINES, NetBEUI, or SNA are running on my LAN. > Seriously?
Practically I'm not sure how this affects someone writing a networked application. Sure, IPv4/IPv6, but if I get a bug report in the year 2026 that my application is broken because it doesn't work on the AppleTalk network, it gets a WONTFIX.
Sure, maybe if I'm writing a low-level network driver or maintaining a mainframe application these are things I have to care about. I think that may be the difference between the other posts and this post - non-experts in Onomastics and Chronology deal with names and dates all the time, hence resulting in issues like government websites not accepting Ng as a last name because it is less than 3 characters or not allowing entering February 29th as a birthday.
Though if a component dies due to ESD from an imperceptible spark then the manufacturer skimped on ESD testing
That's actually not bad, last time I checked the only ones that were in stock cost 300+ (IIRC all x570). My plan then was to maybe get a new case and rebuild it on a micro ATX board which are generally more available and seem to have a few decent options in the ~80 price range.
Anyway, again it's a question of is it worth it spending several hundred and the time it takes to rebuild. It currently "works" fine except it takes 5 minutes to boot and is unable to save any BIOS settings like XMP, fan curves, and so on (and yes I changed the CMOS battery - there's a long thread on the ASRock forums of others having the same issue even after the battery is swapped). The non-optimal settings probably eat a few % of performance but other than that it's mostly annoyance, so it still feels like if I'm going to invest any more in it, it better be more worth it
I've built two PCs in the last 5 years and both have had parts that were broken from the factory... There is something to be said about being able to hand off troubleshooting and replacement. I had ASRock pointing fingers at everything else to the point where I had swapped out CPU, PSU, and RAM, until they relented and replaced the motherboard (the replacement which is broken again now 5 years later by the way...)
This is one of the biggest reasons my wife and I switched away from non-stick too. We moved from replacing non-stick pans after a year of use to our carbon steel pans working better after 5 years of use than when we got them... or buying 80 year old cast irons from a thrift store for 5 bucks. We have more types of cookware now, but none of them have an expiration date
Depending on where we are going and what we are doing, I also bring this thing: https://www.amazon.com/dp/B08YDPB8RZ which is kind of an extension cord + USB charger + all-in-one converter as well. The plug is at a right angle and very flat, so it can fit behind furniture and such that straight cables can't.
- Disable iGPU in BIOS because on a cold boot the system would "latch on" to the iGPU (iGPU was GPU 0 and dGPU was GPU 1, which some programs I guess interpret as "GPU 0 == primary GPU"). Everything is fine on a warm reboot where it assigns dGPU to the 0 slot and iGPU to the 1 slot
- Get a special dongle to get 4k120Hz support over HDMI because the driver doesn't support it. The dongle should also enable VRR but needs multiple kernel patches to do that. Applying the patches causes varying levels of graphical glitches
- On waking from S3 the HDMI audio is dead. I tried various kernel arguments related to power management that various people had reported working for them but ultimately none of them ended up working for me so this one is still broken. Gave up on HDMI audio out and used an SPDIF cable instead (my AVR has been a magical problem solver here but most people aren't going to have a separate device to do that for them)
- On waking from S3 the wifi doesn't automatically reconnect. Solved with a systemd unit that just toggles it off and back on
- The audio out kept changing away from the one I set. As far as I can tell there's no easy way to set the "default" like you can in macOS or Windows, so I had to fudge the priorities of the built in devices a bit with a Wireplumber config
While debugging all the issues I've been bouncing back and forth between various kernel versions and patches. The fact that you can do that is awesome, but the fact that you have to do it to fix and debug issues is unfortunate. Just as an example, while debugging the audio problems I found a ticket that looked like it could be related on the amdgpu driver issue tracker where someone reported a similar problem, and the response from AMD was "please bisect the kernel"... That's just not something that most people are going to be willing or able to do. AMD GPUs are even supposed to be the well supported platform compared to Nvidia. I will say though, this whole debacle with the dongle sure had me wishing I could just stick an opaque-but-vendor-supported blob in like you do with Nvidia and get HDMI 2.1 working out of the box.
At least on Windows, IME Microsoft ironed out a lot of these types of driver issues in the Windows 7/10 era so that things like sleep just tended to work. It's been a while since you had to track down the right driver for your hardware manually. They just kept going downhill from that point forward with boneheaded decisions like sticking React Native or whatever in the start menu and forcing shovelware down people's throats. Even though I was having all these problems with Linux I personally won't go back to Windows, but I'll think twice about recommending it to my non-tech friends and family.
I was expecting them to show code samples or something, but to me it looks more like these were two projects that ended up coming up with similar looking features, even with different implementations of these features. I don't see how Nous Research owes them any explanation, especially since at least from that linked issue they were coming in really hot with accusations of plagiarism. If I owned a large OSS project that amassed issues/discussions/PRs at a rate of ~4k per month I would probably also treat this kind of thing as spam.
Sure, you could argue that they didn't mean it would be positive for the economy to save that money, but "we will save 350M/week" is what's on the buses and their website. Even if we assume the average voter clicks through here and reads everything point by point, or goes onto the website in the first place rather than by the headline, it is at the very least heavily implied... Otherwise what is the argument?