JoshMarler

Apologies for reviving this. Is there any movement on this topic or new/current "best-practice" for avoiding GC/mark-and-sweep CPU spikes? I'm working on an application using https://github.com/nick-thompson/blueprint. Blueprint is a framework...

@svaarala sorry for the bump but any chance on a quick confirm as to whether there is new advice for improving mark-and-sweep stalls?

@svaarala , No problem. Thanks for taking the time. We've got a few alternative to try so thanks for clarifying.

Yeah the mouse button down thing is a pain. @androidStern maybe throw your suggested fix we discussed for #2 here as you could potentially try to leverage the `mouseDrag` event...

Turns out we'll need to implement the chrome debug/inspector protocol as is done in ReactNative so this will be a non-trivial integration. See: https://github.com/facebook/hermes/issues/486

@zigen ahh that's awesome! I'll take a look over your branch and try to digest some of this. `react-dev-tools` isn't something I know a huge amount about but I'd love...

@nick-thompson, This is really cool. Hadn't heard of Docsify. Be cool to add the vscode debugger setup stuff to this. Also keen to sort out documentation for the Canvas API...

** The below is a list of topics we need to document under the new Docsify system to close this issue ** - [ ] Update "Getting Started" with CMake/Projucer...

@jrlanglois this looks great. A Herculean effort! One key point, It's a pretty enormous diff! This is quite likely to cause merge conflicts upon rebasing etc as I suspect some...

> Thanks for the feedback folks! I'm glad to see there's interest. As I mentioned in my original post - treat this `T H I C C` PR as merely...