PWV Portfolio Feed

I like the two levels. 

Per-commit review within a branch means they are all merged together. Stacking branches means the bottom should be merged first, but stacks above it depend on those but don’t need to be merged at the same time.

Its a useful mental difference when working on them.

The web ecosystem has had this capability for years. Even browsers can run code natively compiled with a Wasm compiler. Meanwhile, in the mobile space, all we can do is write a pipeline and ask a mobile CI provider to run it.

And the reason why I'm so excited about this commoditization, which is one of the beauties of software, is that it makes running macOS builds cheaper and more accessible, so builders can build new solutions that were too costly to build before.

I believe we're on the brink of a major revolution. With open-source projects like Coolify, you can input your Scaleway or AWS key to orchestrate environment provisioning without leaving your Git forge's CI. This change is imminent.

Mobile CI providers know this, and they are expanding their offerings with solutions that could be just CLIs, playing a game of making their customers believe that it'd be costly to leave their setup, but it's not. It's getting cheaper and cheaper.

Lastly, Dagger offers a wake-up call, helping you realize that you can create automation that's not tied to a specific CI provider's proprietary steps or YAML pipelines. You can loosely depend on them, making your automation portable.

Virtualization is becoming commoditized with solutions like Tart, Lume, and Curie, many of which have permissive licenses. This is attracting a stream of contributors aiming to create a top-notch virtualization tool comparable to Docker, within the limitations of the OS.

Simultaneously, more cloud providers, such as MacStadium, AWS, and Scaleway, are offering macOS environments as a service. Some are more productized than others, yet all provide an API to request a Mac Mini with specific specifications. This option did not exist before.

Git forges like GitHub, GitLab, and Forgejo offer seamless integration for code collaboration while allowing you to bring your own hosts. Companies such as Cirrus Labs, Cirun, and Depot can supply these hosts if you prefer not to manage them yourself.

The mobile #CI space is plateauing, and we might be on the verge of a DevX innovation in mobile tooling. Let me explain why.

Really? That seems like an unlikely reason. The signature just verifies the commit data minus the signature, it shouldn't matter what is in there for a verification. Can you point me at a use case?

In fact, if this were true, Gitea would break with any new future official git headers.

fun challenge! shortest I could golf it is
const findLongestStreak = (v, n) => Math.max(...v.map(x => ++x).join("").split(1).map(v => v.length >= n ? v.length : 0))

We have released patches for a moderate security vulnerability for the vite dev server. Please update to the patched versions: 6.2.3, 6.1.2, 6.0.12, 5.4.15, 4.5.10

Great vibes!

I'm glad to hear that Alberto :)

Vibe coding: Expectation vs Reality