same. I even have my first disk of turbo pascal programs, written by my grandad, on github: https://github.com/byronka/turbopascal

> No one holds a press conference and cuts a big ribbon at the end of a bridge inspection or structural retrofit.

maybe they should. maybe we could celebrate repair like we do new construction. there’s a comfort in knowing we’ve been put good again that’s worth signifying.

it’s all a balance. i’m obsessive, yeah, but i’m also trying to have a bit of balance for the bigger picture to each choice. if you look back a few commits you’ll see where i wasn’t even using maven, just GNU Make! But i was convinced over time that taking a more conventional route for that would yield better returns.

yes, certainly you could.

You did not miss anything. It lacks that functionality, making it necessary to template the inner part, and then use that within an outer part.

Fully-featured templating libraries provide this in the form of special syntax. This does not provide that level of capability.

There are locks around those - for example, writeLock

I mean race conditions between the operations, e.g. an update followed by a delete:

1. update x in memory

2. delete x in memory

3. update fn checks for file on disk

4. delete x from disk

5. update x on disk

Is this not possible and you end up with different state in memory and on disk.

great find. i’ve got some adjustments in mind, mainly carefully placed locks. i’d like to give you credit for the call out in the docs/acknowledgment file. is there some better way to reference you than jabradoodle? the code i’m considering is in the branch under_consideration.

Thanks that is kind of you. For the time being I would rather not tie my real life identity to my Internet identity.

hmmm. it does seem possible. Let me look into that, thanks!

Interesting you say that: https://github.com/byronka/r3z

Basically the same thing as Minum, but in Kotlin.

Names. One of the two hard problems in computer science, along with cache invalidation. And off-by-one errors.

Valid point. I was going off documentation like here: https://developer.mozilla.org/en-US/docs/Web/HTTP/Messages#s...

That page uses Method though, and places nouns at equal importance with verbs when describing them?

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.

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.

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.