Skip to content

Instantly share code, notes, and snippets.

View sormuras's full-sized avatar
Testing...

Christian Stein sormuras

Testing...
View GitHub Profile
// https://twitter.com/stuartmarks/status/1304654956146745344
import java.lang.reflect.Field;
public class StillAlive {
@SuppressWarnings("deprecation") // oh shut up
static Boolean truе = new Boolean(true);
static void WearMask() { }
static void Stay6ftApart() { }
@nipafx
nipafx / maturity-model.md
Last active August 16, 2019 12:02
JPMS Maturity Model

Maturity Model

Libraries, frameworks, and tools (IDEs, build tools) have widely varying support for the JPMS. I would like to create a model that makes it easy to judge a project for what it can and can't (yet) do - both for users and maintainers.

Conditions can usually be split into those for libraries/frameworks and those for tools, but that's not clear cut. Bytecode analysis tools, for example, may fall into both categories. So always look at both categories, and check which conditions apply to a given project.

This is work in progress - feedback welcome!

Level 0 - Denial: Don't break!