How About We VS Ember-cli

• Date-Centered Approach
  How About We differentiated itself by focusing on suggesting actual date ideas rather than just profile matching. Users proposed real activities, making it easier to transition from online browsing to in-person meetups.
• Creative Date Ideas
  The platform encouraged creativity by having users suggest unique date experiences like visiting a museum, trying a new restaurant, or going on a hike, which helped break the ice and gave conversations a natural starting point.
• Activity-Based Matching
  By matching people based on shared interests in activities rather than just appearance or demographics, How About We fostered more meaningful connections and compatibility based on lifestyle preferences.
• Reduced Messaging Fatigue
  Because the platform was built around proposing dates, it cut down on the endless back-and-forth messaging common on other dating sites, helping users meet in person more quickly.
• Couples Edition
  How About We also offered a couples service that provided date ideas and experiences for existing couples, making it useful beyond just finding a match and helping relationships stay fresh and exciting.

Possible disadvantages

• Limited User Base
  How About We never achieved the massive user base of competitors like Tinder, OkCupid, or Match.com, which meant fewer potential matches, especially in smaller cities and rural areas.
• Service Discontinued
  The platform is no longer active. How About We was acquired by IAC/Match Group and eventually shut down, meaning users can no longer access or use the service.
• Niche Concept Limited Broad Appeal
  While the date-idea concept was innovative, it was too niche for many mainstream daters who preferred the simpler swipe-and-match or traditional profile-browsing approach offered by competitors.
• Subscription Costs
  How About We required a paid subscription to fully interact with other users, which was a barrier for many potential users, especially when free alternatives were readily available.
• Limited Filtering and Search Options
  Compared to more established dating platforms, How About We offered fewer advanced search filters and matching algorithms, making it harder for users to find highly specific types of partners.

• 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.

Tracking How About We since Mar 2021.

• 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