No problem! Thanks for your feedback too. The examples browser is really designed to be a vehicle to learn and experiment with the engine run-time. It should be a great resource for engine-only developers - so hopefully the dvh will find it interesting. We've done a ton of work on the API reference recently too (https://developer.playcanvas.com/en/api/). It's a huge task, but yeah, we're working night and day to make the runtime easier to work with.

It seems like none of that work solves the underlying issue that was raised which was specifically search ambiguity between the library and the editor. Any response should discuss the possibility to changing the library name or creating search friendly alternative name (such the use of "golang" to alow easy searching for content related to the highly ambiguously searchable Go programming language.

I've kicked off a new forum thread on this topic: https://forum.playcanvas.com/t/improving-search-results-for-... Excited to get peoples' thoughts on it.

It's a marketing thing - the engine is free and open source, the editor is not.