Backtrader VS Ember-cli

• Versatility
  Backtrader supports a wide variety of data sources and formats, as well as different types of financial instruments, allowing for extensive backtesting and live trading capabilities.
• Community and Documentation
  The platform has a strong community and comprehensive documentation, making it easier for new users to get started and for experienced users to troubleshoot and optimize their strategies.
• Python Integration
  Written in Python, Backtrader allows users to leverage Python's extensive ecosystem of libraries for data analysis, machine learning, and other financial computations.
• Open Source
  As an open-source project, users can modify and extend the platform to meet their specific trading and testing needs without restrictions, and contribute to its development.
• Flexibility in Strategy Design
  Backtrader offers a flexible and intuitive framework to design complex trading strategies, enabling users to test multiple strategies with different parameters efficiently.

Possible disadvantages

• Steep Learning Curve
  Despite its flexibility, new users may find Backtrader's extensive features and options overwhelming, requiring a significant amount of time to learn and effectively utilize.
• Performance Issues
  For very large datasets, Backtrader might experience performance bottlenecks or require additional optimization, as Python is not the fastest language for high-frequency backtesting.
• Limited Technical Support
  As a community-driven open-source project, Backtrader might lack the formal technical support and customer service that comes with commercial trading platforms.
• Complexity in Live Trading
  Transitioning from backtesting to live trading can require significant additional setup and potential custom development, especially in integrating broker APIs.
• Outdated Resources
  Some educational materials and tutorials may be outdated, leading to confusion due to interface or feature updates that are not well-documented.

• Convention over Configuration
  Ember-cli enforces strong conventions for file structure, naming, and project organization, which reduces decision fatigue and makes it easier for developers to jump between different Ember projects with minimal onboarding time.
• Built-in Tooling
  Comes with a robust set of built-in tools including a development server, testing framework integration (QUnit), asset compilation, and live reload, reducing the need to manually configure and integrate third-party build tools.
• Addon Ecosystem
  Ember-cli supports a rich ecosystem of addons that can be easily installed and integrated into projects, allowing developers to extend functionality without reinventing the wheel for common features.
• Blueprints and Generators
  Provides powerful generator commands (blueprints) that scaffold components, routes, models, and other application pieces quickly, speeding up development and ensuring consistency across the codebase.
• Stable Long-term Support
  Ember-cli follows Ember's release cycle with clear LTS (Long Term Support) versions, providing stability and predictability for teams maintaining large applications over time.

Possible disadvantages

• Steep Learning Curve
  The strict conventions and unique architecture of Ember-cli can be difficult for newcomers to learn, especially those coming from more flexible frameworks or with no prior Ember experience.
• Smaller Community Compared to Alternatives
  Compared to tools like Vite, Webpack, or CRA used with React/Vue, Ember-cli has a smaller community and ecosystem, which can mean fewer third-party resources, tutorials, and community-driven troubleshooting.
• Build Performance
  For large applications, Ember-cli's build process can become slow, and while improvements have been made with embroider, some developers still report slower build times compared to more modern bundlers.
• Rigid Structure
  The opinionated nature of Ember-cli, while helpful for consistency, can feel restrictive for developers who prefer more flexibility in structuring their applications or adopting non-standard patterns.
• Migration Complexity
  Upgrading between major Ember-cli versions or migrating to newer build systems like Embroider can be complex and time-consuming, particularly for older or heavily customized applications.

No analysis of Backtrader yet.

Backtrader Python Review

More videos

No Ember-cli videos yet. You could help us improve this page by suggesting one.

• My reality of trading and how i wish i had never started.

  I do like what I see and hear about backtrader.com. I would say they are a notable exception to my general rule of not trusting or using backtesting frameworks. However, I still think it is important to understand how the framework you... Source: over 3 years ago

• My reality of trading and how i wish i had never started.

  What about backtrader.com? And I feel like it would be step 2 after you at least have something to backtrade and test haha. Source: over 3 years ago

• I need to know what can go wrong with my 'masterplan'

  Backtesting is basically applying your strategy on historical price data to see if it makes money. I've used Backtrader it works decently well: https://backtrader.com/. Source: almost 5 years ago

• Help! Why does chrome console inner text and my program inner text not return the same values? (spent nearly the whole day trying to extract an element). Turned to reddit as its always had the best community. Any help is MASSIVELY appreciated. Puppeteer!!

  The webpage is LinkedIn.com. While this isn’t a framework, I know that are using https://cli.emberjs.com/release/. Source: about 5 years ago