Both of these methods are needed for development. There will always be a way to use them, but it will likely require more elbow grease.
If you know how to install/run any python package, you can run HA without needing installation instructions. This is equivalent to core.
Youāre right, and I appreciate the clarification. I didnāt mean to sound dismissive. I was just reacting out of concern. Thanks to you and the team for taking the time to respond and for all the work you put into the project. Itās really appreciated.
You can still use it! Itās just not supported and at your own risk. That is your freedom to choose, and itās their freedom to choose what not to support.
It sucks when those things dont align,
Nothing is permanent.
But that shouldnt stop a tinkerer like you! Limitation are just a creative design challenge. Now you can try all kinds of new things with the Pi2 
I have a core installation on a Raspberry Pi4. I am incredibly disappointed by the decision to deprecate core installations. I have invested time and effort to navigate the Python dependencies that are always ahead of the current stable OS, and likewise SQLite 3. I have no experience of Docker and no time or desire to learn how to use it. HAOS is not an option because I run several other important to me services on the Pi. Needless to say I had not opted into analytics, because I never do.
I guess the only way core users like me can protest is to turn on Analytics and hope that the statistics change to indicate that many more people are using core than was previously reported. My HA Analytics are now on.
The problem is that you wonāt see people like myself reflected on that side anymore, since Iāve migrated away from Core.
I get you on the Docker points. I still plan on writing a summary of my migration experience and how I had to deal with many exceptions and workarounds which was pretty easy under a Core installation. My only other viable option was Docker though and now that itās done, itās not much different.
Nothing will change for you.
Iām sorry you took that as a criticism. I didnāt intend it that way, and in fact meant it more as a realization on my part.
I routinely disable reporting on all software I install. In this case, I realized the earlier point that the number of container installs is probably underreported, because we turn automated feedback off, is entirely likely. So, I resolved to make sure I am sending that data, because: if you donāt vote, donāt grouse.
btw, itās not ālikeā comparing apples and oranges. Itās a metaphor, and the entire point of a metaphor is that itās not ālikeā.
Damn, that is so disappointingā¦ Iāve been running supervised for years, the premise that the entire device has to belong to HA is flawed IMHO, Iām running multiple services on the same device (a mini PC) and can even use it as a desktop computer in the living roomā¦ The alternative is to buy a device that does nothing else except HA which is wasting money and electricity.
I guess Iāll stick with the last version that works as long as humanly possible
If youāre already running other services on the host, youād be a good candidate for HA Container. You could also run HA OS in a VM.
Nothing will change for you.
Ya, I want the option to run other services on my server, not just locked to HA OS. And what about driver support?
Then run the Docker version.
Probably the best alternative installation is that you can run the Home Assistant Operating System image in a Virtual Machine (VM) under practically any other OS using a number of different VM virtualization hypervisor platforms/applications. It does in practice not take much more CPU or RAM resources than running just the HA container. This solution results in both an easy and a very good experience:
Virtualizing virtual machines is super simple to maintain when have pre-configured virtual appliance images like HA OS and provide all the benefits without the downsides. Recommend read up on the concept of of using virtual appliances for scenarios like this:
Iām trying to use the devcontainer for addon development, but its been very hit and miss (mostly miss) since March this year. The devcontainer currently uses supervised - is that why it is broken? Will the addon development documentation be updated? It currently leads to a dead end.
You just donāt understand complexity of VM, Dockers and rest of the stuff. Layers upon layers of different guests, containers and everything elseā¦ Here people are not ugly because they are rising valid points about HA devs making bad architectural decisionsā¦
Youāll still be able to run core after the deprecation. Itās impossible to make this method stop working. Itās the foundation of python packages which python itself controls. If you know how to install and run a python package/module, you can run home assistant core whenever you please.
Thank you Petro, will try that. I am all for core and simple pip installation of HA. Rest can be up to meā¦ Will try
To quote a certain Petro: āMy manā¦ā
Google my handle before you make more assumptions about my skillset. I definitely understand this space.
I personally preferred HA Core for its simplicity, but it really isnāt the end of the world to run HA Container in this case.
Please mind your language: Youāve already called things stupid and have made personal remarks. You might not agree with the decision, but calling it bad is a stretch.
Let it rest. None of this will change anything.
Run Core if you wish. Itās been said repeatedly: You must just be willing to maintain it and not blame the HA team if it breaks.
And then how do I use add ons?
Also just saw this:
If it works with camera feeds it might be sufficient for my needs
HA Container doesnāt support HAās official or 3rd-party HA add-ons directly, so you need to install your own containers for that software (which, it needs to be said again, are applications separate from HA), or install it old-school directly on the OS.
All of this has been said before, so please read the topic.