javiercr

I've recently switched from GitHub Copilot Pro to Claude Code Max (20x). While Claude is clearly superior in many aspects, one area where it falls short is remote/cloud agents.

Yesterday, I spent the entire day trying to set up "Claude on the web" for an Elixir project and eventually had to give up. Their network firewall kept killing Hex/rebar3 dependency resolution, even after I selected "full" network access.

The environment setup for "on the web" is just a bash script. And when something goes wrong, you only see the tail of the log. There is currently no way to view the full log for the setup script. It's really a pain to debug.

The Copilot equivalent to "Claude on the web" is "GitHub Copilot Coding Agents," which leverages GitHub Actions infrastructure and conventions (YAML files with defined steps). Despite some of the known flaws of GitHub Actions, it felt significantly more robust.

"Schedule task on the web" is based on the same infrastructure and conventions as "Claude on the web", so I'm afraid I'm gonna have the same troubles if I want to use this.

Meanwhile Gemini 2.5 Pro support for VSCode Copilot is still broken :/

https://github.com/microsoft/vscode-copilot-release/issues/8...

Burning Man morning vibes, walking to a neighborhood camp for good coffee and meeting some new friends. Love it.

Awesome! How long did it take to run locally on your Mac? Any details you can share about the stack used for processing (other than YOLO for detection)?

On Episode 01 of The Social Radars podcast [1], Paul Buchheit, creator of GMail, explains that the Gmail invite-only beta was actually due to shortage in hardware and difficulties to scale the service, rather than a just a "growth hack". It seems they were running the service for a long time near 100% capacity.

[1] https://open.spotify.com/episode/0oRAHcP9g41jcEzpDtOa4b?si=1...

API routes are not supported yet for /app

JavaScript is basically a Game of Thrones spin off by now.

Exactly the same thing happened in Spain. +1 to everything you said.

I've been suffering this for years with a TL-WPA8630P v2.0 and so far the only solution from TP Link [1] is a firmware update that disables DHCP only until you reboot it (or the power goes out). It's ridiculous.

[1] https://community.tp-link.com/en/home/forum/topic/265692

A good question is why Google is using only one tile to measure LCP for sites that have maps taking 50% of the viewport.

Is it just a coincidence, or did they make it to avoid ruining LCP metrics for large sites using Google Maps extensively (Airbnb, rent.com, etc.)?

React going full stack may be the first early good new from 2021. I hope they solve routing soon as well.

Does anyone know if this bug is present on Google Kubernetes Engine (GKE)?

I think this only works if you're doing a clean yearn install. If you have a yarn.lock file already generated, chances are every package is pointing to registry.yarnpkg.com instead.

Yes, probably related to npm problems https://status.npmjs.org/

Magic Keyboard = scissor mechanism (what the latest MBP 16" uses).