It's barely gaining adoption though. The lack of buzz is a chicken and egg issue for Mojo. I fiddled shortly with it (mainly to get it working some of my pythong scripts), and it was suprisingly easy. It'll shoot up one day for sure if Latner doesn't give up early on it.
Isn't the compiler still closed source? I and many other ML devs have no interest in a closed-source compiler. We have enough proprietary things from NVIDIA.
Yes, but Latner said multiple time it's closed until it matures (he apparently did this with llvm and swift too). So not unusal. His open source target is end of 2026. In all fairness, I have 0 doubts that he would deliver.
Use-cases like this are why Mojo isn't used in production, ever. What does Nvidia gain from switching to a proprietary frontend for a compiler backend they're already using? It's a legal headache.
Second-rate libraries like OpenCL had industry buy-in because they were open. They went through standards committees and cooperated with the rest of the industry (even Nvidia) to hear-out everyone's needs. Lattner gave up on appealing to that crowd the moment he told Khronos to pound sand. Nobody should be wondering why Apple or Nvidia won't touch Mojo with a thirty-nine and a half foot pole.
Kernels now written in Mojo were all in hand written in MLIR like in this repo. They made a full language because that's not scalable, a sane language is totally worth it. Nvidia will probably end up buying them in a few years.
CUDA Tile was exactly designed to give parity to Python in writing CUDA kernels, acknowledging the relevance of Python, while offering a path researchers don't need to mess with C++.
I really want Mojo to take off. Maybe in a few years. The lack of an stdlib holds it back more than they think, and since their focus is narrow atm it's not useful for the vast majority of work.
A browser automation Chrome extension and MCP. It consumes less context than playwright MCP and is more capable: it uses the playwright API directly, the Chrome extension is a CDP protocol proxy via WebSockets.
I use it for automating workflows in development but also filing taxes and other boring tasks
This Chrome extension allows you to control your own browser via MCP.
It bridges the CDP protocol from the MCP to the browser, meaning you can do everything Playwright can.
The MCP works using a single tool: execute. It will run Playwright code to control the browser, meaning context usage is small compared to Playwright MCP and the capabilities are more extensive
The advantage of space is that you have infinite scale. Maybe data centers in space do not work at low scale but you have to think of them at much larger scale.
Elon Musk considered data centers in space simply for the fact that more solar power is available in space than Earth
This project is similar to Playwright MCP, but with some important differences and benefits.
---
1. Key differences from Playwright MCP
1. Uses your existing Chrome tabs via an installable Chrome extension instead of launching a new browser window.
2. Exposes only one MCP tool: `execute`, which runs arbitrary Playwright code in a sandbox.
3. The extension communicates with the MCP via Chrome DevTools Protocol (CDP) over WebSocket.
2. Benefits
1. Less context bloat: the LLM only needs to reason about a single tool instead of many.
2. More capable: the agent can write any Playwright code to control the browser.
3. Fewer resources: reuses your existing Chrome browser instead of spawning a new instance per MCP project.
4. Human–machine collaboration: you can temporarily disable the extension to:
* Solve CAPTCHAs
* Unstick the LLM
* Intervene manually when needed
3. Using it in your own scripts
1. You can connect to the extension from your own Playwright scripts.
2. This lets you automate tasks in your existing Chrome tabs, instead of running a separate browser instance.
4. Non-disruptive browser control
1. The extension does not force-focus Chrome windows during interactions.
2. You can run automation in non-headless mode without Chrome constantly stealing focus and interrupting your work.
5. Security model
1. The extension connects to a localhost WebSocket server started by the MCP.
2. This server proxies MCP commands to the extension.
3. Only tabs where the extension is enabled are accessible to the MCP.
4. Other tabs remain isolated and inaccessible to random agents.
6. Safety considerations
1. The MCP can still cause damage if run unsupervised.
2. You should:
* Run it with permissions enabled, and/or
* Keep it under active human supervision.
reply