mpd

> ai use is completely and thoroughly normalized

I think this is a certainty. Future generations will be born into a world where education, technology, and jobs have corrected for AI's existence. They will never know a world without it or have the experience of the current growing pains.

We've seen this plenty of times with new tech in the past, and as disruptive as AI is, I can't imagine the cat going back in the bag.

Heya - I'm the author. Glass is a cross-platform MCP server that gives an agent a way to see and interact with GUI apps. I don't like building UI. Agents can code it, but can't verify or debug it. Glass exists to close that loop.

Glass is purpose-built for software development, and aims to enable headless, parallelized agent work while the user continues to use the machine unhindered[0]. It minimizes token usage, increases consistency, and just goes faster by preferring to interact with an app's accessibility tree, before taking the screenshot route (which glass also fully supports).

Glass is cross-platform and the code is Apache-2.0 licensed. We release builds for Linux, Windows, and macOS hosts. Glass supports development targeting the three above host platforms, Android (all hosts) and iOS[1] (macOS hosts). The internal API is backend-agnostic, and new platforms can be added in the future pretty easily.

Feedback is very welcome, either here or at github. If it breaks on your app, I am especially interested in knowing about that. I hope you build great things.

[0] Due to the license enforcement on Windows and macOS, isolated headless development targeting those platforms requires a VM. It will otherwise interact directly with the desktop. Android and iOS development on those platforms can still be done headlessly via the emulators.

[1] The iOS backend does not currently support multi-touch gestures.

When something can be treated as a score to compare with others, it will be. Everything else just follows.

collect $1,329,063

Did that include bugs due to encountering unexpected nulls?

Oh, it looks like the release command would fit the `build` step I mention.

As far as the after-deployment tasks go, we automate those just like migrations - they're (occasionally very slow) one-offs that we don't want to hold up a restart for. Really, an analogue to the release command that can run after restart is all that I'm talking about here.

My big want here is containerized deployments with build + release steps to allow me to e.g. run migrations and after-deploy tasks (we use both). This prevented a move to Render for us previously.

That explains the JVM, but why Java, specifically? JRuby offers everything you mention.