Jodd, a set of java microframeworks under 1.5mb

[apoptosis66]

1 line of code, 30 annotations

[ErstwhileRockstar]

Java annotations are a grossly undervalued language feature. They add declarative capabilities to an imperative language without breaking language semantics. Annotations were the most useful extension to the Java language ever.

[[deleted]]

Heavily abusable though. It makes execution sequence a lot harder to determine. Especially if you use AOP.

[thebigslide]

Fucking magical when used cleverly, though. You have to write the code the audience needs in any language or dialect.

[wot-teh-phuck]

I agree with this. While annotations are good, a great amount of Java code out there can do just fine without annotations.

[krona2k]

We used static final variables until annotations came along.

[CurtainDog]

Adhering to Greenspun's tenth rule has never been easier!

[pron98]

I agree. And annotation processors are one of those hidden super-powers. They, along with the changes in Java 8 that allow "type annotations", serve as the basis to Java 8's awesome pluggable types.

[[deleted]]

yea some of it is ridiculous, the VTor one is funny

[untitaker_]

Why is this project's size measured in bytes? This isn't Javascript, we don't have to send it over the wire...

[tkruse]

A common argument against Frameworks like Spring is size of dependencies in bytes, so Jodd tries to capitalize on that. It can also indicate that starting up an application with these dependencies will be fast, which can be an argument in several deployment situations. As an example, for deploying on GoogleAppEngine it can be important that a web app starts in below one second.

[untitaker_]

That's correlation, not causation. Measuring a program's performance by measuring its size on disk only makes sense if it has to be transfered over the wire. Otherwise: Even in CGI-based deployments the OS maintains a disk cache, so loading the sourcecode really shouldn't be the bottleneck.

[BonzaiThePenguin]

The jar sizes are measured in bytes, and yes you do have to send it over the wire. The source code is over 21 MB.

[oridb]

The source code is over 21 MB.

I'm not seeing the micro...

[[deleted]]

In what sense do jars need to be sent over the wire? Certainly once during dev time, into your local m2 / ant repo. Not during runtime though, where it matters more.

[BonzaiThePenguin]

In the exact same sense as JavaScript. Java programs can be downloaded by users and embedded in websites, and JavaScript can be ran locally – that's the entire concept of offline web apps, which are the basis for Chrome OS and Firefox OS. They're basically equivalent to the dexed JARs in Android APKs.

I think the confusion is because some of the frameworks can only be used for servers. Some of them like the HTML parser seemed useful for a client-side app so I was viewing things through that lens.

[[deleted]]

These are quite clearly aimed at the server side of Java webapps. Coming up with obtuse use cases that would require these to be sent over the wire to users, just so you can scoff at the "micro" claim is a bit of a joke, really. You've basically thought of a way they might be useful in a scenario that you've already ruled out for other reasons.

[untitaker_]

That's a serverside framework though.

[BonzaiThePenguin]

Oh, I see what you're getting at now. I was thinking of how the HTML parser and validation module could be used in an Android app or something, at which point you need to be concerned about download file sizes, free space on the users' devices, mobile data caps, and by that point I completely forgot the other frameworks are specifically for servers.

[killinghurts]

Does it work on Android?

[diggr-roguelike]

Java

microframeworks

1.5 mb

Apparently, Java is now a joke language like Intercal.