Thanks for clearing this up. Last year I was shopping for used phones and looking at S8/S9, and getting very confused when I saw S21 starting to pop up. "How many of these did they make, anyway?"
Tangentially related, Reminds me of this: In Los Angeles there's a few very prominently displayed billboards at a shopping center for the Galaxy S4 that has somehow remained up [1]
Stack Exchange (and by extension, Stack Overflow) publishes all their data (anonymized) for download and offline usage as part of the Archive.org project. If you wanted, you too could have a copy of it locally to search while the site is down.
I think this is a feature for a lot of people. It's the perfect "same but better" phone for parents, grandparents, and other less demanding markets. All the cases and accessories continue to work as expected and the home button is exactly where it's always been.
I'm not sure which CPU you have specifically but the lowest-end model of the X1 Carbon Gen3 has an i5-5200U [1] that lists Intel Quick Sync Video support.
From the wiki page for Quick Sync [2]:
> Intel Quick Sync Video is Intel's brand for its dedicated video encoding and decoding hardware core. Quick Sync was introduced with the Sandy Bridge CPU microarchitecture on 9 January 2011 and has been found on the die of Intel CPUs ever since.
I can't confirm but I'd guess your performance issues lie elsewhere than in the h264 decoding specifically.
If you check out the generation-codec table in that wikipedia article [1], under Broadwell (I believe that's the 5200U's generation name), it says there is support for AVC (which I believe is H264, I'm not a codec wiz), so that's a really good point. I'm not sure why I've consistently had issues with this on my machine then. I wonder if this is something with a configuration on Linux then?
Thanks for pointing that out. I've looked at this table before and payed attention to HEVC, not AVC, so I believe that's where my mistake came from.
Accelerated video decode is often disabled by default on Linux versions of browsers and can be quite dependent on versions of drivers/mesa/X-vs-Wayland/etc.
Do you have any more information about how you're doing this? Whenever I've tried to use Docker as a remote development environment the process felt very foreign and convoluted.
They publish the CAD files (both mechanical and electrical) on GitHub with instructions on how to manufacture your own expansion cards. I believe the interface within the expansion cards is just standard USB-C. If someone could manage to squeeze all the necessary components within the physical dimensions, it should be possible to make your own soundcard expansion card.
Maybe addional hardware wouldn't even be needed. Onboard soundcards should be good enough for ASIO (they work fine on Hackintoshs and Core Audio on MacOS). The reason why it's not offered is the licensing I think, it's properietary technology from Steinberg, a German company who invested into Windows pro audio early on and kinda got a first mover advantage there.
I don't know how much licensing would cost, but Framework could possibly offer a driver for the internal card as an addon. Then the slot could be used for a small headphone amp which would be more third party friendly I think.
Modern Chromebook with their "Linux containers" are really, really close to being a wonderful developer experience with the same level of user accessibility, support, and refinement of any of the other "major" operating systems out there. I'm surprised Google hasn't capitalized on it further.
If you haven't tried again recently the neovim team has done a ton of work updating the documentation on nvim-lspconfig [1]. There's also projects like kickstart.nvim [2] which aim to provide a very simple starting point for new users. It's "batteries-included" neovim which notably includes LSP, TreeSitter, completion engines, and some basic git functionality.
