Interesting! However, I offer a perspective. When Tesla stretched the envelope to include Autonomous Feature and allowing people to prepay for the future option, they warned (correctly) that software to accomplish AD would be a some future date. Tesla then withdrew from the configuration site as time stretched on and allowed those who still wanted to configure "off-menu". I can understand those who paid "up-front" and had to wait were frustrated.... However, it seems incongruous to complain waiting for promised software and also complain that it has "bugs" when released because they rushed it to market.
This is complex software which has to operates in the complex and multi facet environment -- we are no longer at 1+1= 2. Tesla is a vanguard for Autonomous Driving. Each iteration over the last few years required hardware (cameras, sensors and processors) that didn't exist a couple of years ago. It is no longer simple calculations, but Artificial Intelligence computing varying levels of probability decision making -- exactly the way drivers maneuver in traffic . My 2016 Model X was suppose to attain Autonomous Driving someday -- only to realize the single camera, the 1 Tera flop processor, the software and the sensors were inadequate to make the decisions needed every second that a human driver performs as second nature. How far they have come in 3 years!
"BETA" simply means both the provider and user understand the product is NOT the final level and agree by turning on the feature, the user accepts that it is not final, may have bugs, may require updates, or complete revisions. That what the owner/driver is accepting when moving the slide to "ON". It is not a cop-out, but a mutual understanding which is common in the software world. Software users always have the option of not implementing "BETA" versions, and foregoing what ever features are currently available by electing to wait the final version on some future date that is fully-tested and debugged by the "BETA" community.
Having attended many Tesla Owners' Brunches and other owner sessions at the local Design and Sales Centers here, I was amazed at the number of request that were written down, (none refused) and passed on to Tesla. Some, I thought were "ridiculous" (like the person that wanted the navigation system to direct and calculate long-distance travel; this was in the days when we used the trip-planer app to help to find where to charge en route -- print it out and take it with you. Now it is integrated in the Nav System and on the "Go Anywhere Tesla" website. Tesla also offered a "feedback" mailbox for the new navigation system -- I sent several observations and recommendations being glad to provide the feedback solicited. I would like, but don't expect confirmation or updates of my recommendations -- understanding it would be a challenge to give feedback to hundreds-of-thousands of users -- providing status; therefore, I accept the one-sided communication. Owners can always send recommendations on their "MY TESLA" sign-on. I remind myself that I never heard from Ford for over 20 years of driving their SUVs.
Just an in insight for those not familiar with SW development (no I am not an expert coder, but managed the SW Process for a large computer company) ... updates/changes implementations are not random, but planed for when the "module/app" is being re-codded and then extensively tested through a set of proven and continuously-updated debug scenarios. It is a complex process to get from Development to ALPHA and BETA code levels and eventually to generally available SW. A bit easier to make a minor change in existing available legacy SW.
My point is not to say the frustrations and recommendations are incorrect, but to provide a perspective of the complexity of doing something like fully AI/Autonomous Driving. Thanks.