I just hope the functions in that library don't suddenly stop working due to changes made by the developers.
I think you misunderstand.
BEEM is abandoned. There will be no changes.
Even if there were any - it's on github and you can always clone into an older version - the one that was working for you.
As long as there are no significant changes to how Hive nodes work, it will keep working, especially if you stick to the core functions, like I showed above.
Problematic with BEEM are the more abstract, higher level functions - some of them broke, when Hive changed.
The core features still work all the same and never changed since block 0.
I mean the HIVE developers, not @holger80. His API is reliant on the base infrastructure code being as it was (3 years ago). Am I getting this wrong...?
I think you misunderstand.
BEEM is abandoned. There will be no changes.
Even if there were any - it's on github and you can always clone into an older version - the one that was working for you.
As long as there are no significant changes to how Hive nodes work, it will keep working, especially if you stick to the core functions, like I showed above.
Problematic with BEEM are the more abstract, higher level functions - some of them broke, when Hive changed.
The core features still work all the same and never changed since block 0.
I mean the HIVE developers, not @holger80. His API is reliant on the base infrastructure code being as it was (3 years ago). Am I getting this wrong...?
Hive's core features still work all the same and never changed since the first block, 8 years ago.
Likewise, BEEM's core functions (inherited from Piston) also never changed for those 8 years.
If you stay away from the higher level, abstract classes of BEEM, or at least use them consciously, you can probably use it forever.
OK,... I was under the impression some BEEM functions might stop working due to HIVE tinkering.., good to know.