Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The API in question here is the C++ embedder API. It's altogether a different issue to Google changing some Go library APIs.


So are you saying there's nothing that the V8 devs could have done to ease the transition?


To 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.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: