Feed 📋

Link
See More

@dotproto I learned it the hard way 🫤. Thanks for sharing it Simeon

Link

@mattiem whenever I try it for something larger than “write a test for the function changes” I wonder if I’m using it terribly wrong, or the idea is just full of flaws. It feels brute force programming to me.

Link

TIL that camera films and airport security scans might not be best friends 😬. I can’t wait to see the development of my latest films.

Link

Can there be more cars in Barcelona?

Link

Hola Barcelona 👋

Link

This is yet another example of how our reluctance to invest in open innovation stifles projects that could have laid the groundwork for further advancements. We choose to spend on proprietary versions, where innovation occurs in secrecy, despite having no say in their trajectory.

Link

It's unfortunate that innovation still occurs, yet nowadays open source alternatives rapidly close the gap. The challenge is that these solutions eventually require funding, which is difficult to secure since many equate "open" with "free of charge."

Link

Both open source and proprietary software carry the risk of being abandoned. When a proprietary project faces this fate, it often marks a definitive end, as the corporation retains ownership of the source code. Arc, the browser, illustrates this scenario, though it's worth watching if they'll yield to the demands of the community.

Link

At Tuist, we're enhancing accessibility in dev environments by converting proprietary formats into documented ones and exposing them via web APIs and integrations. Development should not happen in isolation, so we're breaking down silos.

Link

A server opens so many opportunities 😍

Link

If you're not familiar with Dagger and their cloud services, here are some examples of the insights they automatically gather from your Dagger builds.
dagger.io/cloud

Link

Inspired by Dagger, and with Clickhouse integrated into our backend, I believe we can gather and display data in real-time online, allowing anyone to view and take on the task of identifying and highlighting errors, ultimately reducing the debugging time for our teams.

Link

I've observed that in remote settings, whether prettified or not, "xcodebuild" logs are the primary go-to for debugging, especially when something goes awry. However, they're not exactly user-friendly, as the errors don't always conveniently appear at the end of the logs.

Link

Had anyone mentioned how challenging it would be to track the build duration of an Xcode target, I likely would have laughed it off. Now, I can proudly say I've reached Xcode hacker status. 😂

Link

Our efforts to promote Mise and introduce a streamlined "init" workflow are yielding success. Adding new features now requires just a couple of simple commands 🤩

Link

Do we still have time to make requests?

Support third-party logging backends in the swift-build build system. The contract can just be structured blobs through stdio.

Link

I spent days figuring out how to get a piece of data from .xcactivitylog. Why does make everything so hard? 😅