Skip to content
void256 edited this page Feb 28, 2016 · 4 revisions

General Notes

  • API matters

    API decisions are important! Which doesn't mean that we'll make always the right decisions 😉 but the Java-API that Nifty provides is important. When being unsure we should leave things out. It's better when we have a small concise API instead of a bigger unclear one. This is especially true for the public API. No more methods that only Nifty is supposed to call internally. NONE!

    This sounds naturally of course but it's really tough at times. And it possibly will complicate things (for us, building it). It should not be difficult to use for the API user. Checking the Nifty 2.x Java Doc regulary and making sure it is easy to understand should be one of our primary goals.

  • Targeting zero GC-pressure

    In performance critical parts of Nifty (renderer, layout, scene management ...) we should try to minimize the creation of temporary object to reduce time spent in the GC.

  • ...

Back to Overview