# Static Global Context

DevFeed: [Static Global Context](<https://devfeed.tech/articles/static-global-context-19532.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/static-global-context/>)

Author: Shai Almog

Published: 2017-05-29T00:00:00Z

Content type: article

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Code](<https://devfeed.tech/topics/code.md>), [Java](<https://devfeed.tech/topics/java.md>), [context](<https://devfeed.tech/topics/context.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [context](<https://devfeed.tech/tags/context.md>), [java](<https://devfeed.tech/tags/java.md>), [performance](<https://devfeed.tech/tags/performance.md>)

## AI overview

The article explains why Codename One is introducing a new static global context class to replace some uses of the broadly named Display class. It argues that static methods can provide shorter syntax and modest performance benefits under current Java and ParparVM implementations, while preserving existing APIs for now.

## Source excerpt

A developer recently asked me why Display is called Display when it has such a broad purpose? The reason is historic with roots in Codename One's origin back in 2007, when we formed the company Chen advocated for a rename of that class and I disagreed. In retrospect I was wrong, the name doesn't work. This isn't something we can easily fix but it's something we can replace and improve...