There are a bunch of aluminium Lily58 cases out there, they're not cheap tho.
Most of the time keys popping out means your plate is too thick or the switch holes aren't a good fit. You can often improve it (and the sound) with some foam between the plate and the pcb - you can buy laser cut neoprene plate foam for lily58s, or you can always freehand it with a knife and a sheet of 2-3mm foam (it's not that hard and doesn't have to be perfect).
It's pretty common for Alice-style keyboards to have two Bs (the one in the pic in the article does) as on a normally-staggered keyboard the B key is basically equidistant from the home keys so it's common to use either.
But it would be a bit of a problem for keycap sets, some come with extra Bs to accomodate Alice keyboards, but none that I'm aware of have extra G/H/T/Y. That would mean you'd be into buying two sets or using weird keys, so it's probably unlikely to be a popular choice.
That said, there's so many custom keyboards out there, and it's easier than you think to design and build your own - if you feel strongly about it go for it.
I did have that problem a little when learning to type on a split, but I very quickly corrected after hitting the table a few times haha. I actually think it's arguably easier to learn to type on a split as it'll quickly force you to break some bad habits.
Yeah that OSMC box is just running Debian with their stuff coming from its own package repo. You can get a root shell. I realise I could have built something myself (and have in the past) but it's absolutely worth the money to me to get everything in a tiny package and working perfectly from day one.
I wouldn't recommend Kodi for streaming, it kinda works but the experience isn't great. I use it exclusively for playing stuff from my server full of legally acquired public domain videos (ahem).
I do watch YouTube videos on it, but I use TubeArchivist (basically a fancy wrapper for yt-dlp) to pull them onto the server first, and a script to organise them into nicely-named directories.
Yeah I have a couple of recent Samsung OLEDs and they're fine without an internet connection despite reports that they wouldn't be. If I press one of the annoying streaming service buttons on the remote it'll give me a setup popup which needs to be dismissed, otherwise they work fine, albeit without any built in streaming support.
I'd read reports that Q-Symphony (audio from the TV speakers and soundbar simultaneously) wouldn't work, but it does.
I stuck an OSMC (https://osmc.tv/) box to the back of both of them so they can play stuff from my NAS. They're not the cheapest solution and I realise Kodi/XBMC on which they're based isn't everyone's jam (I grew up with XBMC on an Xbox so it is very much mine) - but they play everything, have wifi, HDMI-CEC, integrated RF remote, and work out of the box.
Model numbers if anyone cares: Samsung QE65S95C, Samsung QE77S95F. I believe S95, S90 and S85 (at least up to F) are all very similar so they should all work but ofc ymmv.
My experience of working with Perl as a primary language from late 90s to today: Perl was dead long before Perl 6/Raku was a real thing. By the time that happened it had already lost massive ground to PHP, Python, Java, etc.
PHP had replaced CGI as the easiest way to get code on a webserver, Python and Java were easier to read and understand, easier to structure large systems with, and generally easier to use. Ruby came along and MVC frameworks became the thing for complex web platforms.
Meanwhile Perl was sorta keeping up, the "Modern Perl" movement helped dispel myths about "write only" code, things like Moose, DBIC, Catalyst, Mojolicious, etc meant you could write pretty modern stuff with it. But the community was smaller, fractured by Perl 6 and dominated by some ahem divisive characters which made it intimidating for newcomers, and it just slowly died from there.
By the time Stack Overflow came along it was easy to see that other languages had vibrant communities surrounding them and for me it never really recovered.
This is the approach I take too. If I need it and I can do it then I'm going to. If you don't want me to then block me.
I must say I've had some raised eyebrows over that approach but if the alternative is not getting my shit done then I'm gonna do it unless explicitly forbidden.
SSH tunnelling is an utter necessity in the ridiculous corporate environment I work in. Incredible amounts of bureaucracy and sometimes weeks of waiting to get access to stuff, get ports opened, get some exception in their firewalls and vpn so someone can access a thing they need to do their job.
This guide mentions -D but doesn't really articulate quite how powerful it is if you don't know what it does.
ssh -D 8888 someserver, set your browser's SOCKS proxy to localhost:8888 (firefox still lets you set this without altering system defaults). Now all your browser's traffic is routed via someserver.