a perfect example of the thinking behind most frameworks. I don’t think most people are looking for minimal. For those that are, this might be right up their alley.

Minimalism is an interesting ideology. it’s about choosing to do more with less, and there’s a great deal of ingenuity in saying, i only have this one knife and a rope, how do i cross this chasm. so to speak.

no offense intended to the batteries included crowd. this is just something i have developed a taste for.

Modularism is my favourite. I am enjoying using ExpressJS of all things, because it comes bare bones but you are a few mix/match middlewares from having it set up as you like. And the process of setting them up is not a chore, it is valuable, you now know how your thing works. Whereas frameworks give you the kitchen sink behind a facade that makes most happy paths easy. But eventually you have to deal with that complexity one way or another, and usually it is by hacking together stack overflow and github issue answers :-)

Your kind of playing a little fast and loose with the term 'database'. You've implemented a naive persistent cache. (Don't get me wrong, I have too at times. they can be quite useful.)

I'll accept the naive mantle. But is this not a database? A database is an organized collection of structured information, or data, typically stored electronically in a computer system.

The 'batteries included' space is definitely a market. For example https://streamlit.io is wildly popular with data teams for quickly making a pre-styled, usable enough web UI to put on top of some model, with controls that are automatically reactive. Those ppl have zero interest in fiddling with modular systems or spending time optimizing and scaling web apps.

All a stock JDK lacks to handle this out of the box is a JDBC driver (which it has innate support for), and a template engine.

It has a built in HTTP server which has recently been improved. It’s also getting, in preview now, a string formatting subsystem which is not quite a template language, but it’s interesting. And, to be fair, out of the box the JDK does have a template system: XML and XSLT 1.0 support.

The HTTP server is usable, but could use some sugar. Same for the logging system, usable but could use some sugar as well.

It has TLS built in as well.

It does not have JSON built in. In todays world, that along with persistence are probably two true must haves. Mind, the JDK used to ship with JavaDB, which was a version of the Apache Derby database.

It is trivial to add the SQLite jar to a project. You wouldn’t even need a connection pool with that.

Anyway, the point being that the JDK is almost there just by itself to be capable of serving a lot of use cases if you’re willing to put in a little bit of work to make your particular work flows a bit easier to use.