The motivation is simply to have the runners share a local docker build cache rather than pushing and pulling cache from registry which is a ridiculous best practice.
For any small team wanting to try Copilot, heed my warning that you will waste hours navigating their billing settings using various out-of-date documentation. Long story short, I finally got an email from them saying that "Copilot Business is available for teams purchasing 10 or more licenses". This is undocumented but other people are reporting the same: https://github.com/orgs/community/discussions/199346
We're sticking with Cursor for now, using Kimi as our daily driver (branded as "Composer").
I've been experimenting with aerospace for the last month. Still not sure if I enjoy the tiling aspect. It can get quite janky on occasions when multiple windows open at once. And it lacks some UI affordances (I'd love if you could make the focused app much more prominent). I might try this more limited approach
I wish macos for more serious about window management, it's extremely limited out of the box.
You can literally download a file called LineageOS_on_arm64.utm from the Releases page, drag and drop it into UTM and it Just Works. I've been looking for this holy grail for years.
I went down this rabbit hole before, you have to ignore all the recommended approaches. The real solution is to have a build server with a global Docker install and a script to prune cache when the disk usage goes above a certain percentage. Cache is local and instant. Pushing and pulling cache images is an insane solution.
What you are describing is basically remote buildkitd. That allows all of your docker builds to share a big cache. The cache-to/cache-from approach is of limited usefulness.
Hi Alexei, thanks for your work on HSLuv! I love the simplicity of it, where you can use HSLuv as mostly a drop-in replacement for HSL which most designers are familiar with.
I keep seeing new tutorials on designing accessible palettes that still use HSL, where the WCAG2 contrast breaks and goes all over the place as you vary the hue and saturation. HSLuv makes life so much easier here and lets you focus on exploring colors that you know will pass, using a familiar looking color picker.
> Using native functionality, you have the option of a seizure-inducing sliding animation or an equally time-wasting fade
Amen.
I tried switching to Aerospace, but it would become visibly laggy when connected to an external display and switching a screen that had Zed open for some reason. So I've switched back to Yabai :(
This is the correct answer. Pro-tip: use Django admin as a user facing interface in your prototype, then you won’t even need to write HTML templates, let alone client-side JS.
reply