3 ms·
I'm interested to see how Go progresses over time, as they consciously made the design decision to keep the language easily parseable so that API breaking chang
by shmageggy 13y ago
I'm interested to see how Go progresses over time, as they consciously made the design decision to keep the language easily parseable so that API breaking changes can be accounted for programatically rather that requiring manual porting. See gofix -- http://blog.golang.org/introducing-gofix http://blog.golang.org/introducing-gofix
In theory, this should allow them greater flexibilty to iterate and refine the language over time without the negative backlash that we're seeing here.
- lttlrck 13y agoThe API in question here is the C++ embedder API. It's altogether a different issue to Google changing some Go library APIs.
- shmageggy 13y agoSo are you saying there's nothing that the V8 devs could have done to ease the transition?
- sgbeal 13y agoTo their credit, they warned us some months ago (April?) on the list that the InvocationCallback signature and Persistent would change. That was a new step for them - the first time i was warned about breakage before it happened. But without concrete change details and a reference build to work against, one can't even prepare for the change until v8 has released something. A flood and backlog of client breakage was inevitable the moment they decided to make the change.