You have to have rules before you can enforce them...
It looks like part of the label [1] will include a QR or link to a public registry, so in theory you can easily confirm the device has actually been certified.
I have current products using raspberrypi and i.MX parts, and have worked with teams using TI and Renesas parts. Some fully custom boards, some SoM based.
Their BSPs all suck to different degrees, but you can work around the issue with enough effort. If I had to choose ignoring cost, I'd pick an i.MX part, but they're priced for the industrial consumer where price isn't a big concern.
Stay away from any asian parts (Allwinner) or phone parts since they seem to have no vendor or community support.
Like others have said, some of the SoM vendors do a pretty decent job of hiding the evil, but that often comes with very opinionated BSP layers which limit your product design. We've had to ignore/replace all of our SoM vendor's layers, borrowing the few useful parts as needed.
I've installed doors with that system, or a very similar Menard's carries.
Given the choice, I'd opt for it since it is easier to fine tune, but I'm not convinced it's safer than the traditional way. You still have to secure the door against unintentional movement and ensure everything is assembled correctly before tensioning.
The only "safety" feature I see is it eliminates the appeal to use an inadequate tool to tension the spring, so resist the urge to use a flimsy old screwdriver and you'll probably have similar risk either way.
My experience with students that have used various learning software has been mixed.
They're not good for absolute beginners because it can't give you feedback on the bad physical habits that lead to repetitive strain injuries, or just make it hard to play.
Once you're past that point, you're usually far enough to find a tab or chord sheet and figure it out.
For a motivated intermediate level student there can be value in the smooth difficulty progression and forced introduction of new concepts, but that's a pretty small window where they add value.
I've been teaching beginning guitar lessons for about seven years. Guitar is a little different in that, outside of classical guitar, there's very little traditional pedagogy, but from experience I think these things are generally true about most instruments.
1. When you start learning you sound terrible... for a long time. It's very difficult to stay motivated when you can hear your problems.
2. It's very difficult to judge your own progress. I've started recording short videos during lessons which I can show to students weeks or months later when they're expressing frustration with their progress.
3. You have to enjoy practicing, since you have to pick up the instrument most days to maintain the dexterity, callouses, etc. It's very easy for a pushy parent to beat the joy out of practicing.
4. You have to understand the difference between playing that song you can play great, and practicing something you suck at so you improve. It's very easy to stagnate if you only play.
Really it boils down to, you're going to suck for a while, then you're going to think you suck even when you don't, and you have to keep enjoying the process even when you think you suck.
As a full-stack web engineer who's ended up being competent with Yocto, I think a major factor is which companies need embedded Linux or proper microcontroller embedded work.
They're not you VC, SASS, zero marginal cost software first company. They're hardware manufacturers with physical product margins. The embedded project I work on only ships on a few thousand units/year, and it's only a small component of the overall system.
I think within that group of companies, the comp for embedded vs "software" isn't significantly different. "Software" just has FANG/VC backed salary inflation making the averages look crazy.
My grandparents owned a food processing business until the early 90s. One of their main businesses was slicing potatoes to be used in grocery store potato salad.
They had a room dedicated to removing eyes before running them through the peeler.
From the stories I've heard they'd use anything. Potatoes where half the bag is rotten mush, sure. Rotten potatoes where the sprouts have big enough spuds to process, use the sprouted spuds.
I think those were the extreme cases, since they're stories I've heard, but I doubt any similar facility isn't cutting out eyes and processing them today.
Step one is to understand the architecture of the system. What are the different hardware components? How do they interact?
A simple emulator boils down to:
While(true)
Emulate_one_cpu_cycle()
For each cycle you have to produce any side effects from the various peripherals (serial comms, update the display, generate audio, etc.), process any external changes (button presses, serial data), and emulate the next CPU instruction (basically a big switch).
I recommend "The Ultimate Gameboy Talk (33c3)" [0], for an overview of the Gameboy and it's internal peripherals.
There are various test ROMs available that you can use to verify the basic functionality. [1][2]
My parents owned laundromats my whole life, and I was being taken along to help install and service laundry equipment when I was pretty young.
Aside, being the one to climb down into the bulkheads in a laundromat is a good inventive to go to college.
I agree the laundry business is changing and probably declining overall, but I think 2005 is a bad baseline.
In the late '90s some laundry equiptment manufacturers put together unreasonable financing deals for building or renovating laundromats. If you see a laundromat from that time that has Maytag or Speed Queen signs out front it was probably built using one of those packages
The financing was sold with revenue or utility saving estimates that were completely out of line with reality, and many of those stores ended up collapsing under the debt and closing within 5-10 years of being built, and so probably had a peak number of them around 2005.
I saw this first hand having helped build then disassemble more than one store in Wisconsin and Illinois.
For your reference the fourth paragraph from WashPost story:
>Burlington Electric said in a statement that the company detected a malware code used in the Grizzly Steppe operation in a laptop that was not connected to the organization’s grid systems. The firm said it took immediate action to isolate the laptop and alert federal authorities