Mixin可否用这个直接代替flux等架构了?

**Kenshinhu** · November 19, 2015, 9:36am

Mixin特性主要用于在多个组件中共同一个方法,让我们可以更加方便的定制组件
那这个可否我直接用这个Mixin直接作网络层(或Action 及Controller…等)
那会不会可以更加简单地搭建React应用呢?

**jiyinyiyong** · November 19, 2015, 11:14am

Mixin 只是个共用代码的方案, 并不推荐作为架构当中某个组件用, 如果某些地方觉得比较方便, 依然不能作为架构的一部分.

**pinyin** · November 19, 2015, 11:39am

之前尝试过，不好用，坑。

对了，网络层并不取代Flux，而是取代Relay

**leozdgao** · November 19, 2015, 12:17pm

关于Mixin这里有两篇文章讲到：

github.com

acdlite/flummox/blob/v3.5.1/docs/docs/guides/why-flux-component-is-better-than-flux-mixin.md

Why FluxComponent > fluxMixin
=============================

In the [React integration guide](react-integration), I suggest that using [FluxComponent](/flummox/docs/api/fluxcomponent) is better than using [fluxMixin](/flummox/docs/api/fluxmixin), even though they do essentially the same thing. A few people have told me they like the mixin form more, so allow me to explain.

My argument can be broken down into three basic points. Note that these aren't my original ideas, nor are they unique to Flummox — they are the "React Way":

- Declarative > imperative
- Composition > inheritance
- State is evil

Declarative > imperative
------------------------

This is a no brainer. Remember the days before React, when you had to write one piece of code to render your application and another to update it? HAHAHAHA. That was awful. React showed us that expressing our views declaratively leads to clearer, more predictable, and less error-prone applications.

You might feel like fluxMixin and FluxComponent are equally declarative. They do have similar interfaces: a single argument/prop, that does (almost) the same thing. Still, as nice as fluxMixin's interface is, there's no beating a component in terms of clarity. A good rule of thumb in React is that everything that can be expressed as a component, should be.


Composition > inheritance

This file has been truncated. show original

总得来说趋势应该是Mixin最终被淘汰，至于将来是不是Hight Order Component，很难说，至少现在HOC是趋势，自己在实践的时候，思考共用代码方案的时候，也基本用HOC+decorator。

90% of the time you don’t need mixins, in general prefer composition via high order components. For the 10% of the cases where mixins are best (e.g. PureRenderMixin and react-router’s Lifecycle mixin), this library can be very useful.

不知道大家怎么看？

**Kenshinhu** · November 19, 2015, 5:09pm

但这个不会就因为增加组件灵活度而牺牲了代码的重用性吗?这个好像有点违背了单一法则

**leozdgao** · November 20, 2015, 2:01am

但这个不会就因为增加组件灵活度而牺牲了代码的重用性吗?这个好像有点违背了单一法则

@Kenshinhu HOC是存在一些缺陷，毕竟还不是官方方案，现在React感觉也处于过渡期，ES6 Component和Mixin功能本身不兼容。不过针对你说的缺陷，不知道能不能举个例子说明？