Hi HN,

We built PageSpeed because generic performance scores are often too vague to be actionable.

The Hook: Instead of just saying "Optimize images," we detect your stack (React, Next.js, WordPress, etc.) and suggest framework-specific code changes.

Closing the Loop with AI Agents: One thing we added specifically for the modern dev workflow is a "Prompt for AI Agents" feature. Once a bottleneck is identified, the tool generates a structured prompt that you can paste into tools like Cursor or Copilot to actually execute the refactor.

It’s completely free and no signup is required. We’d love to hear if the AI-generated prompts actually work for your specific repo structures!

Indeed, you are right!

Author here. Git 3.0 is the first major version in 11 years.

Key takeaways:

- SHA-256 becoming default (brian m. carlson has done ~100 of 200-400 needed patches)

- Rust becoming mandatory build requirement (controversial but necessary for memory safety)

- Reftable format shows 22x performance improvement in benchmarks

- Timeline depends on getting Git forges (GitHub, GitLab) ready with SHA-256 support

The Rust decision is particularly interesting - Patrick Steinhardt's proposal is a "trial balloon" to gauge ecosystem readiness. Happy to answer questions!

<3

Thanks for sharing it!

We have used the gem: https://github.com/a-chacon/oas_rails, and we didn't need to write the specs, just comment the endpoints

We ended up using this gem to implement OpenAPI: https://github.com/a-chacon/oas_rails, it was quite straightforward

So, we ended up by using https://rubygems.org/gems/oas_rails which does the heavy work and generates almost everything. We only had to document the endpoints.

That's it. ProcessWire+DeployHQ (on a VPS)

DeployHQ+VPS (Hetzner, Vultr, DO, etc)