These are chat archives for stealjs/steal

14th
Nov 2016
Justin Meyer
@justinbmeyer
Nov 14 2016 21:30
So, I'm trying to explain the benefits of having CanJS broken out into individual repositories.
Presentation1.png
Currently, upgrading from CanJS 2.3 to 3.0 might look like that.
A big step.
Cursor_and_Presentation1.png
but if you break that step down ... CanJS 3.0 is mostly CanJS 2.3 ... with a lot of bug fixes, a lot of new features ... and some breaking changes (which account for most of the "step size"). Currently, to get all those bug fixes and new features ... you have to take on the breaking changes immediately and all at once.
Presentation1.png
Going forward, in CanJS 3.0, we'll be able to release packages independently of each other. This means you can keep upgrading to bug fixes and new features (small steps) ... and delay some of the big steps (can-route 4.0.0) until later.
Justin Meyer
@justinbmeyer
Nov 14 2016 21:36
you'll be able to talk those big steps in pieces too. Say can-route 4.0 one month and can-component 4.0 another month
as can-route and can-component 4.0 are now independent of each other
and may depend on can-compute 3.X
Justin Meyer
@justinbmeyer
Nov 14 2016 21:52
whoops
did I put this in stealjs!
Julian
@pYr0x
Nov 14 2016 23:02
;)