mpd

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.

I really enjoyed the recent Hackerbox[0] featuring an FPGA. I'd never worked with one prior to that.

https://hackerboxes.com/collections/past-hackerboxes/product...

collect $1,329,063

Having good error messages is one of the important priorities for me in my compiler, so I made the commitment early and am using codespan_reporting[0] to report the errors, which is going well so far.

0: https://github.com/brendanzab/codespan

Did that include bugs due to encountering unexpected nulls?

https://www.reddit.com/report to skip the subreddit mods and send it right to the admins.

I have an old phone set up here, running Octo4a. It's working great.

https://github.com/feelfreelinux/octo4a

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.

My question is whether or not rubocop can autocorrect it to whatever. If so, I really dgaf about this.

If your only special move is "You're wrong!", it's going to be hard to talk to you. What do you think is debatable?

Only if said "reasonable person" were around in the 90's, and knew the shit that MS was trying to pull. I happen to be one of those people, but that's not the catch of the day here.

No reasonable person could understand the phrase, "Don't Be Evil," to mean, "Don't do things that I personally consider evil."

TBH, I think almost everyone treats the former statement, as meaning the latter. Did you mistype here?

Maybe there's even something different about using "evil" here, specifically. Would another word have a different outcome?

Yeah, tbh I think this project is trying to polish a turd.

MongoDB is a life-changing technology for many Developers

Are there any legitimate citations for this claim? "Life-changing"? Please.

oh man, it looks like this could level up by using the indeterminate state of a checkbox

To me, it feels like the same effect as Ruby ~15-10 years ago. Lots of chaos as good (subsequently winnowed down to preferred), patterns were discovered, and then things stabilized. It isn't sexy anymore, but to this day I've yet to discover a better tool, that lets me blast out features and make changes at rapid pace, than Ruby (and Rails on the web side).

I stopped reading about two seconds in, when it popped up some dumb thing trying to get me to log in / sign up.

I'm currently using https://postimages.org/ for the odd occasion I want to upload something.

I think it's the likely reality of far more projects than just terraform, and I don't fault the project completely for reaching this state - attrition is a brutal thing.

It's distressing personally though, that it's an issue unknown to me before I read this post, and affects a product I use and champion.

The brainfuck compiler is at https://github.com/xxx/cbfc, but I haven't opened up the other one to the public yet. It'll be open sourced once I'm further along with it.

I'm not your parent commentor, but imo, it's because there's is an enormous amount of existing info out there about these two steps. For these kinds of projects, they are necessary whether you're translating to another language (i.e. generating code) or not. And everyone starts with lexing and parsing. And just repeats the same old shit.

in my case, I learned by writing a brainfuck compiler last year. Now I'm working on a compiler / vm for a 30 year old esoteric mud language.

I see it as a new hack (against the human body), really, like in the original MIT sense.

I ran into https://www.youtube.com/watch?v=ZUvGfuLlZus (Elevator Hacking: From the Pit to the Penthouse) awhile back, and it was so interesting to me that I ended up watching the entire 2 hours in one sitting.

Oh yeah, for Apple, just throw it up on Twitter.

and tbh, it's probably the same answer for most providers these days.

It's working for 24-bit color as well.

Android is an open source OS, but not a "phone". It's the core, but you need more than that to boot it on a particular device.