I think semver could use a marker for "breaking change to a clearly marked private API that we nonetheless believe people use"
We call it an "intimate API" in Ember. We guarantee an LTS intermediate before dropping.
-
-
Yeah makes sense, but at the same time, don't make it public if it's private. Pointing out that language/tooling is not helpful in this case
-
But reality is messy sometimes. Can you keep it around for one LTS cycle? And have an alternate implementation with a different name?
-
Ahh,that's good context for the previous tweet too,thanks. Makes sense.
-
Is there something holding Ember back from making future things, that require it, actually private?Like in a closure, instead of a _ prefix?
-
One of the goals of the new module API changes in 2.16 (see https://www.emberjs.com/blog/2017/10/11/ember-2-16-released.html …) is to make this easier.pic.twitter.com/JkkD4sswke
-
Performance-critical code isn't always capable of using closures in the way you describe.
-
Oh, that's awesome! And yes, that's the always present caveat, closures are slow, prototype is not
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.