But honestly this splitting makes sense even at a glance AND looking more closely? Like they tried to become another Devolver Digital and realized they just weren't cut out for that and are splitting things up into manageable and functional sections again.

The mega-huge licensed-IP stuff is wildly different from the mostly indie stuff that "does well but not LOTR well" and coffee stain always seemed like a PR-based side-hustle acquisition.

Likewise them acquiring a tabletop game company never made any sense at all.

I don't know if Asmodee will survive or not, depends if they Vulture Capitalist'ed it or not but that's... really not one I care about? Never did when they snagged it, don't either now that they're letting it go.

The "keep cranking out licensed IP sequels" company can focus on that, those series have really turned into the modern-day Madden franchises at this point mostly, so if anything their growth is limited but it's so huge it's safe.

And Coffee Stain is still a fair bit of an industry darling among players, not quite Zachtronics levels of good-will but respected and broadly a safe bet it'll survive and likely thrive just fine.

Honestly I was surprised they raised the minimum to 144Hz instead of 120Hz myself, because for broad-spectrum use outside of purely twitch-reflex gaming 120Hz is WAY better since it can do 24hz, 30hz, and 60hz without any odd frame doubling issues so it works far better than 144Hz for watching movies and shows, and avoids that weird 'this cutscene feels particularly OFF' effect that can happen when a game has it's cutscenes locked to 30Hz but keeps rendering at the vsync rate.

My point was there's a cheap as hell brute force solution of "Stop trying to run the signal down 10 feet of wire right along the noisiest electronics." not that it's the ideal one.

This is entirely a design problem because they want to just blindly run the antenna from the middle of the rear of the roof down 10+ feet of the cheapest cable they can find to the back of the radio.

You can decode AM or FM radio with something on the order of an RP2040 level CPU, if they just mounted that near the antenna and did the decoding there then just send the audio digitally to the front radio that would entirely solve the problem.

Hobbyists have done this with the original RPi Pico even, decoding-only AM or FM is not computationally expensive at this point but the 'standard design' of a 10-foot-plus dumb wire from the antenna to the radio? That's the issue.

But they _DO_ have a redirect to your usual profile URL (which is the one you choose and can be a custom domain and very memorable) if you just slap /rss on the end of it, to get to your actual RSS URL. So it's as trivial to get someones RSS URL as it could possibly be.

I've never in my life had a good experience with Android Auto.

On-wheel controls and working bog-standard bluetooth audio are light-years more important to me than any of the vendor-specific garbageware.

My phone stays in it's mount and generally it's screen is wildly more visible than the car-radio screen in sunlight anyways.

If I didn't need a screen to setup bluetooth pairing more conveniently I wouldn't even want the car radio to have a screen itself.

"Inboard brakes" is the term.

It's been used in high-end cars here and there, the downside: Have to dismantle the axle off to replace the brakes not just pop the wheel off.

But in a pure EV scenario the mechanical brakes would get far less use, so I could see 'inboard with >250k before replacement' being a thing just to meet legal requirements and catastrophic electronics failure scenarios.

For a lot of them it requires a USB cable link so you can't charge your phone while using it with Android Auto because the US head unit vendors dragged their feet enormously on supporting wireless Android Auto.

And the same geniuses refused to support anything higher than 5V@0.5A "USB Standard" charging on their USB-A ports.

Subaru and Toyota at least at the low end were still doing this until a few years ago or requiring custom apps that were trying to 'compete' with Android Auto instead of supporting it directly until as recently as roughly 2020 model years for some models.

Most don't "use" anything at all for nav. They pair their phone for bluetooth MAYBE, but their phone in a mount (suction-cupped to the windshield or dash) is what they use for nav directly, Android Auto by and large works like shit on most stock OEM US head units in my experience, car geeks are constantly clamoring to get the head units the EU or other foreign models have because they by and large work a lot better.

And they still did hire a voice actor, this wasn't machine-generated whole cloth just used in effect a glorified fancier version of autotune to match the other voice actor more closely to the deceased one.

They're using double-speak here.

By 'friendly' they actually mean 'You can trap a co-worker at their cubicle and force the issue.'

Zoom? They can take their headset off, mute you, or just leave the call.

So you don't harass equal level co-workers 1-on-1 over Zoom because you really can't.

So any 1-on-1-ish interactions between equal level co-workers the pushy ones are forced to play much more 'friendly' by that metric.

And I get that Google can't scale up to the millions and millions of users to have a full-sized account recovery team while the service is free.

But having a "Pay $100 to open a case with a human being about regaining access to an account." option at least would cover 99% of the edge cases.

Yes, I said $100. A big fat high-ish number to both pay for a few hours of someone's time and deter abuse.

Even SATA or SAS 6G drives can saturate ridiculously large pipes when you have enough of them. Spindle count (which applies to SSD's too) is a force-multiplier people forget about.

Even just 6 * 2.5" HDDs can fully saturate a 10-gig network link for sustained transfer. Mine do, they only need to push ~250MB/second per drive in RAID-5 to do so in fact.

If you even just expand it to 8 * 2.5" HDD's it only needs to push 200MB/second even if you jump all the way to RAID-6.

Once you're talking even just 24 or 48 (a commonly available JBOD chassis for 2.5" drives, two rows of 24 drives in a 2U, rear row 'tilts up' for swaps) you're talking >40-gig worth of drive bandwidth even if only drive hits about 125MB/second, which even 5400RPM drives can reliably do.

The literal only downside of HDD's is the huge random read seek latency these days. Writes you can mostly avoid the issue just with various modern journaling filesystems that write from one end of the storage to the other, then start back over at the start, so writes become very sequential. Caching can help on the random reads if you have enough, but even there you don't need wall-to-wall NVMe storage, the bottleneck will still be the network links.

Your math is wildly off and nonsensical.

https://www.samsung.com/us/com...

Eight of those would fit in a single 5.25" bay.

https://global.icydock.com/pro... to minimize cabling nonsense even.

Even worst case if you somehow found 15mm tall 2.5" SSD's? You could still fit four in a single 5.25" bay.

Hell I've had a six-pack of 2.5" 2TB HDD's as one of my primary NAS boxes for almost 8 years now, single 5.25" bay.

If you want really high density you can fit TWELVE M.2 22110 or smaller format SATA SSD's into a single 5.25" hot sway bay, though the bay itself costs about $500 then unfortunately.

...but it's purely minimalistic contact info.