towhans

When using browser-tools-mcp I can point to an element and ask Agent to "change color of this element to red". It would copy the part of the HTML and search the codebase for it.

I can imagine having an in browser, framework level tool would know exactly which controller and which template generated this element and could target it more precisely while using less tool calls and less tokens. I haven't tested it yet but that is my expectation.

The devil is in the details.

1/ How much Coins per commit will somebody get? It's totally subjective and decided ex post. How do you compare a patch with 300 lines of code to a bugfix that touches just one character? Or to a comment that sheds light on an important issue?

2/ How do business owners submit profits? Even if they are totally honest people - we live in a complex world where it might be very difficult to separate profits of one App from another.

All in all it seems to me that this is a great way to exploit young developers that want to learn but don't know their value yet. The Coins system tries very hard to give impression that it is fair. It's not.

The fact that I don't own my contributions is a total show stopper for me.

I like the overall idea - just not this particular iteration of it.

I cannot believe there is not a complete solution for this. I mean user tracking AND lifecycle emails in one single easy to use package.

I am a programmer yet still I don't get what this is. If an app wants to send JSON to another app why not use HTTP for that. DNS will take care of the routing. The only thing that seems novel to me is their use of UDP which is faster then HTTP.

I totally disagree with updating the UI BEFORE the request gets back. It's wrong for so many reasons. They all boil down to the fact that server state is independent from the client state.

The speed argument also doesn't hold. If requests take too long to process then you have either problem with your API (doing something synchronously on server side which should be done asynchronously, granularity problems,...) or your server is freaking slow. At worst a request should take under 100ms of pure server time. Add latency and you have 300ms.