Preact instead of React?

[11111000000]

Preact aims to deliver on a few key goals:

• Performance: Render quickly & efficiently
• Size: Small size, lightweight (approximately 3.5kb)
• Efficiency: Effective memory usage (recycling, avoiding GC thrash)
• Understandability: Understanding the codebase should take no more than a few hours
• Compatibility: Preact aims to be largely compatible with the React API. preact-compat attempts to achieve as much compatibility with React as possible.

[11111000000]

What's Missing?

• PropType Validation: Not everyone uses PropTypes, so they aren't part of Preact's core.
  PropTypes are fully supported in preact-compat, or you can use them manually.
• Children: Not necessary in Preact, because props.children is always an Array.
  React.Children is fully supported in preact-compat.
• Synthetic Events: Preact's browser support target does not require this extra overhead.
  A full events implementation would mean more maintenance and performance concerns, and a larger API.

What's Different?

Preact and React have some more subtle differences:

• render() accepts a third argument, which is the root node to replace, otherwise it appends. This may change slightly in a future version, perhaps auto-detecting that a replacement render is appropriate by inspecting the root node.

[Wildhoney]

👍 +1 for Preact.

[neverfox]

It would still support React, right?