This posting is older than 6 months and can contain outdated information.
The lesson I learnt in the past is that it simply makes no sense to
share plans in advance because it leads to exactly this kind of
situations. It raises expectations that - if not fullfilled in a
timeframe (defined not be me, but by the reader) - lead to repetitive
questions like "why?", "when?", "why not yet?" and "what's the
status?". All of which to answer consumes time that could have gone
into development instead. Additionally, if a plan turns out to not be
feasable, no longer fit into the general direction the product is
taking or turn out to require a fundamental rework of a part of the
product that there's no time to do at the time, complaints are
guaranteed. Last but not least, sharing plans in advance also helps
competitors in their assessment of where a competing product is
heading. ALL of this is harmful and really contradicts the positive
intentions that were behind sharing plans in the first place.
Therefore: I listen to, keep track of and consider all feedback and am
very glad and happy to get it. I *really* appreciate it. But I no
longer comment on future features, development decisions or technical
details that lead to a decision. I no longer comment on the status of
development other than that it's ongoing.
That leads to faster results, allows me to make more points from the
ToDo list a reality in the same timeframe, gives customers more value
and updates for their money and saves a lot of time that'd otherwise
be spent on discussing topics that don't benefit of discussion at all.
Development of Remote Buddy is ongoing. Display of long filenames has
not been forgotten. Answers to why?, when?, why not yet?, can you give
me a timeframe?, when can we expect to see this? are not available.
New features are announced the day they are available.
Thanks for your understanding.
Best regards,
Felix Schwarz
