This is the automatic transmission defense. Some people don't know any better, or are too lazy/scared/inept to learn anything else. Others just enjoy putting it in Drive, and hitting the gas.
I've found that forth works best when you use it to create a DSL for your problem domain, and you write your application code in that DSL. That DSL becomes the critical abstraction that helps prevent your codebase from becoming an unusable/unmaintainable mess. This isn't a new idea; the book that got me thinking about when/how to use forth was (oddly enough) http://thinking-forth.sourceforge.net/ . It's a good read even if you never intend to build a forth project.
As a side note, I've done image processing with forth: I helped build a commercial HD video camera with it that shipped in the mid 2000s, and I found it well suited once we had the problem reasoned out well enough to build our DSL. Overall the product ended up being composed of forth/C/hand written assembly, and a bunch FPGAs. We shipped things with < 10 people, and I think the interactive/extensible mindset that forth gave us helped us get the product out the door successfully.
To add 'color' to the comments: I've got strong positive opinions about forth, when used properly. I've helped save several embedded/early-stage board bring-up projects with it.
More than one person has called forth a programmer "amplifier". If C++ has the capacity to blow off your whole leg, forth is more than capable of forming a black hole beneath you and sucking you in.
Wiring isn't under control of the home/business owner until it hits their NID, which is already on-prem. Getting the connection to the NID is where the expense is, and it's why AL is putting money into the process. Without this, someone has to spend the thousands of dollars pulling permits/digging trenches to run fiber to your house.
I too have worked with major automotive OEMs, and all the 'security' I've seen is nothing but lip service. The quality of embedded software in the automotive world is laughable. Forget anything advanced, they're just getting into the what-do-you-mean-bounds-checking stage of computer security.
In this case, I don't think that's it: this package wasn't due for delivery until the following Monday. I was pleasantly surprised when I got the text saying it had been delivered.
If how it's deployed doesn't influence the way you write software, you're either: a) developing something trivial, or b) deploying something that's not going to work well in the long run.
Hopefully the community will continue moving forward by getting actual work done. These technologies are all cute, but nothing here, except the scale of marketing, is groundbreaking.
I've seen these types of customizations worked out with /some/ rental property owners, depending on lease terms. Akin to commercial 'tenant improvements'.
Could you please expand on this statement? Why do you think this that only this community could rebuild them?