MyFeelback VS git-fastclone

• Customizable Surveys
  MyFeelback allows users to create highly customizable surveys that can be tailored to specific business needs, enabling more precise data collection.
• Real-Time Analytics
  The platform offers real-time analysis of survey data, which can be critical for making quick, informed business decisions.
• Multi-Channel Distribution
  Surveys can be distributed across various channels including email, SMS, and social media, broadening the scope of data collection.
• Integrations
  MyFeelback supports integration with multiple CRM systems and other marketing tools, allowing for seamless data flow and enhanced functionality.
• Rich Reporting Features
  Offers detailed and rich reporting features that help in visualizing the collected data through various formats such as graphs and charts.

Possible disadvantages

• Cost
  The platform could be considered expensive for small businesses or startups that have limited budgets for customer feedback tools.
• Learning Curve
  New users may find the platform complex to navigate initially due to its wide range of features and customization options.
• Limited Free Plan
  The free plan is quite limited in terms of features and the number of responses, which could hinder small-scale operations.
• Support Response Time
  Some users have reported that customer support response times can be slow, which could be problematic in urgent situations.
• Language Limitation
  While the platform supports multiple languages, some features and documentation may primarily be in French, limiting accessibility for non-French speakers.

• Faster clone times
  git-fastclone speeds up cloning of repositories with submodules by using reference repositories and caching, avoiding redundant downloads of shared objects across multiple clones.
• Efficient submodule handling
  It automates the recursive cloning and updating of git submodules, reducing the manual overhead typically involved in managing nested repositories.
• Local object caching
  By maintaining a local cache of repository objects, it minimizes network usage and disk space when cloning multiple repositories that share common history or dependencies.
• Simple drop-in usage
  It is designed to be used similarly to the standard git clone command, making it easy for teams to adopt without significant changes to their existing workflows.
• Useful for CI/CD pipelines
  Its speed improvements are particularly beneficial in continuous integration environments where repositories with many submodules are cloned repeatedly, reducing build times.

Possible disadvantages

• Limited maintenance
  The project has seen infrequent updates and community activity in recent years, which may raise concerns about long-term support and compatibility with newer git versions.
• Narrow use case
  It is primarily beneficial for repositories with many submodules; for simple repositories without submodules, the performance gains are minimal or negligible.
• Additional complexity
  Introducing a caching and reference mechanism adds complexity to the clone process, which could lead to unexpected issues if the cache becomes corrupted or outdated.
• Dependency on Ruby environment
  Since git-fastclone is implemented as a Ruby gem, users need a working Ruby environment installed, which can be an extra setup requirement for teams not already using Ruby.
• Potential caching pitfalls
  Improper cache invalidation or stale cached objects can potentially lead to inconsistencies in cloned repositories if not carefully managed.

Myfeelback Employee Reviews - Q3 2018

More videos

No git-fastclone videos yet. You could help us improve this page by suggesting one.