Just in case you were unaware, the RP2040 is available on dozens of ready-made, arduino-compatible boards like the Pi Pico, the Adafruit feather boards, of the Seeed XIAO RP2040 boards. Those have all (or at least most) of the IO already mapped to pins, USB headers, booatloaders, reset buttons, etc already mapped.
Things like the Pico are really easy to solder onto a designed PCB as well because of the castellations, so it's easy enough to design a board around the footprint and then just solder the entire pico onto your PCB with a soldering iron, avoiding the need to use something like a hot-plate or reflow oven. This has been my preferred way of working with it.
He's acknowledged some of the short-comings of the most recent iteration of the doughnut tutorial on twitter before. Blender 4.0 should be coming out later this year and he's stated he'll be releasing a new version then: https://twitter.com/andrewpprice/status/1631529825717604353
Not sure about his more recent content but he used to have a policy that the VODs could be uploaded in full as long as they were uncut and not modified. If you go watch some older VODs he says so at the beginning.
I'm a casual embedded-electronics user at best, most of my projects haven't advanced much past turn a simple servo, light some LEDs, maybe read a sensor and POST to an endpoint. For these tasks, Arduino has been pretty good for me and removed a lot of the complexity. The `setup()` and `loop()` model makes a lot of intuitive sense. That being said, I've spent no small amount of time on `String` vs `char*` (as an inexperienced C/C++ developer) and found the guardrails of the Arduino ecosystem to be very frustrating.
Do you have any recommended resources or additional search terms to explore to learn more about hobbyist-level embedded electronics outside of the Arduino ecosystem? FreeRTOS looks interesting but it seems to add a lot of overhead versus something simple like Arduino. Similarly, I've looked at STM32 programming before but my searches were very generic and the STM ecosystem is massive. Specifically, I was trying to figure out if I could reprogram some old drone flight controllers (equipped an STM32F103CBT6 with a bunch of useful embedded sensors, running old versions of "betaflight") for personal projects but the entrypoint to STM programming (STM32Cube?) and the setup code was considerable.
That price is for a V6 (not ecoboost), single-cab, short-bed F-150 that doesn't even have power locks or windows. Those trucks aren't generally sold to consumers. Minimally, you're looking at at least $35,515 for an XL Super Cab, but more than likely you're looking at a minimum cost of $41,755 for an XLT. KBB's data [1] reported that the average cost in 2018 for an F-150 was $47,174 before fees.
Beyond just the storage constraints, there are performance concerns with the 256GB model [1]. At least with the 13" M2 MBP Apple has switched to using 256GB SSD NAND chips which means that anything less than 512GB has only a single channel of flash to read and write from. It's unclear if the new Air will have this same constraint but it's something to consider.
NASA puts out a new video called "What's up" at the start of every month with all the interesting, predicted events for stargazing. They post them to both Twitter [0] and YouTube [1] as well as on their Skywatching page [2], the latter of which is a great resource with daily guides. It's a fun start-of-the-month ritual for me to check out the latest events and add them to my personal calendar.
For actual notifications, most stargazing apps probably have some sort of news feed or notification system. I can't recommend a specific one but a quick Google search tells me Star Walk 2 [3] seems to support push notifications
Have you looked to see if your microwave has a volume control menu? After years of listening to my microwave blare across the house I saw a tweet that informed me that most microwaves have a menu setting somewhere to control the volume and sure enough, my Frigidaire microwave actually does. I had just never thought to look.
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.
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.
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.
Things like the Pico are really easy to solder onto a designed PCB as well because of the castellations, so it's easy enough to design a board around the footprint and then just solder the entire pico onto your PCB with a soldering iron, avoiding the need to use something like a hot-plate or reflow oven. This has been my preferred way of working with it.