3 ms·
Personally I don't use macro/micro to describe the bytecode footprint, but rather the API/conceptual footprint. If Jetty is secure and performant, and Javalin
by peeters 9y ago
Personally I don't use macro/micro to describe the bytecode footprint, but rather the API/conceptual footprint. If Jetty is secure and performant, and Javalin keeps it encapsulated, I think micro is a fair descriptor still.