I can relate to the frustration, like when I try to migrate a process into Bika and get stuck due an unforseen blocker. E.g. Not being able to export a view as a csv/xlsx file, no regex support, or not being able to have local single variables or reference values from an external Bika database in a formula.
That said, Bika is immensely complex software from a development perspective. Building something thoughtfully and correct is much more important than building it quickly imo. Fixing bugs and improving the foundation should generally take precedence over adding new features (unless they are features I requested!! 
).
Over time it has noticeably improved and become more robust overall. If it’s noticeable at the surface level, it’s likely involved a lot of improvements under the hood. This appears to be confirmed by the changelog, which I wasn’t aware of until it was linked above.
I believe every bug I’ve submitted has been addressed and fixed. Fairly certain every topic I’ve posted here has been replied to by a team member also.
It’s very impressive as-is imo, just need to give the chefs more time to cook in order to support all the workflows we want, remove blockers etc. Personally, I’m super optimistic about Bika - it’s probably at the top of my ‘tools I am optimistic about’ list haha.