Packages were first long before blueprints cam along. I’ve used them forever. And I’ve never used a blueprint at all.
I doubt yaml will ever completely go away and I am one of the ones that would find doing everything thru the UI more than tedious (point-click-scroll-click, point-click-scroll-click, etc., etc., ad nauseum…).
And limiting…there is a reason why you don’t have an exclusively point-click-scroll-click word processor program. It’s way faster to just type it out (I have nothing against auto-complete tho. I’m not a total Luddite. )
Blueprints are made for one function - create an automation or scene with only the options provided in the blueprint. no more/no less.
If you need additional/less options then you need to manually edit the blueprint…which is written in…you guessed it…YAML.
Blueprints are OK if you have no idea what you are doing and only want to do exactly the same thing as the blueprint allows but they are completely limited beyond that unless you know how to edit them…in yaml. And have you actually LOOKED inside a blueprint to see all of the stuff that’s in there in order to “make it easy” for the next person to use? I understand yaml and even I fear to tread in there myself at times. And those are usually the simple blueprints. Bigger ones are just…
The only thing that is officially “going away” in yaml are some built-in integrations.
For everything else yaml is likely here to stay because of those inherent UI limitations. And we are starting to see some of those limitations even in some integrations configured thru the UI. I think there were some options that were available in the yaml config and weren’t implemented in the UI because they were too complex to accomplish. But I can’t remember where I saw that tho so take that as hearsay.
I think you are mistaken.
the user still needs to manually create all of those things. the advantage to packages (as has been pointed out) is that all of the various bits for a logical “function” are all stored in the same location instead of you needing to open many different files to find all the related stuff.
Becauise packages are inherently non-singular use things. You can literally do anything you want in the package (that is supported by the HA infrastructure of course).
need 3 helpers, 2 switches, 15 sensors, 4 automations and 5 scenes? done…by you…in yaml.
it really only depends on how you want you HA structured.