Just to make clear: my main complaint is: C-O-M-M-U-N-I-C-A-T-I-O-N by the LbF team. It’s totally absent.
Why not have a blog on problems encountered?
As an example: the problem of LbF processes not terminating on Windows after closing the program.
It’s reported here:
This of course gets people frustrated, because you are unable to restart Local. Only after you’ve terminated those processes you can. Does LbF really expect users to go that far and find out?
Not only did the team first not recognize the problem, after a few more posts it was acknowledged that “something has to be fixed in an upstream dependency”.
I replied to that unhelpful answer with:
- What ‘something’?
- What ‘upstream dependency’?
And I would want to add to that:
- What has changed where?
- In that unnamed ‘upstream dependancy’?
- In LbF?
- If the latter, why is it so hard to revert the change?
Mind you, the issue mentioned above never got a solution from a developer. Only the last post in the thread (by @Serena) maybe offers a clue.
Did that get an answer or acknowledgement by a LbF developer? No.
That’s what I mean with Communication.
At the moment, users are just left in the dark.