Changeset View
Changeset View
Standalone View
Standalone View
src/docs/concepts/behaviors.diviner
| Show First 20 Lines • Show All 173 Lines • ▼ Show 20 Lines | The two major downsides to the behavior design appear to be: | ||||
| - They have a higher setup cost than the ad-hoc methods, but Javelin | - They have a higher setup cost than the ad-hoc methods, but Javelin | ||||
| philosophically places a very low value on this. | philosophically places a very low value on this. | ||||
| - Because there's a further setup cost to migrate an existing behavior into a | - Because there's a further setup cost to migrate an existing behavior into a | ||||
| class, behaviors sometimes grow little by little until they are too big, | class, behaviors sometimes grow little by little until they are too big, | ||||
| have more than just glue code, and should have been refactored into a | have more than just glue code, and should have been refactored into a | ||||
| real class some time ago. This is a pretty high-level drawback and is | real class some time ago. This is a pretty high-level drawback and is | ||||
| manageable through awareness of the risk and code review. | manageable through awareness of the risk and code review. | ||||