Installed using the curl-to-bash on Sequoia and I’m getting “error: ReadOnlyFileSystem” on ‘boo new’. Can’t see any open issues on gh and nothing in the readme.
Definitely interested in something like this - love ghostty and I’ve been finding Zellij a bit crashy recently (plus I don’t really need tabs).
That was great, thanks for the write-up. It’s rare to get a peek into Palantir’s ontology-forward approach. I’ve certainly been curious.
> But it would make no sense to have an LLM regurgitate an existing form document token-by-token rather than call a piece of 1994 software like Hotdocs to populate some placeholders.
This is a real “oof”, isn’t it. Very difficult to understand what they were going for here. Perhaps they just assumed no one in the intended audience would pick it up. But it certainly is enough of a red flag that it made me go back to the top of your write-up for a re-read, thinking about their whole pipeline in much more sceptical terms.
Could you say more about signals? Is it are all analogous to, say, game engine signals paradigms (eg Godot) - components at any depth emit signals and any other component can subscribe? Or something totally different?
Those who have moved to Resolve from FCP: would you share a few words about your experience?
I’ve used FCP for a long time but have never loved it. I also have some experience with non-destructive workflows like Blender geonodes and have heard that Resolve adopts a similar paradigm. Definitely curious!
Just get Resolve. It is similar to what FCP
was before Apple turned it into glorified iMovie. Only it is far more powerful than FCP 7 was back then.
Industry-standard NLE's like Premiere or Avid are probably the closest to Resolve. But even those are legacy programs that rest on their moats, whereas Resolve takes far more chances and does far less dumb shit than Adobe and Avid.
The seamless integration with industry-standard grading software is also... um mindblowing. Premiere has Lumetri and FCP has it'd colour correction tab, both of which are like MS Paint compared to Resolve's colour capabilities.
It's also free. The paid version unlocks mostly things to do with grading.
I use both in my workflows. Though with all of the features of Resolve, I still use FCP for most of my content. FCP is just faster to edit and has a smoother end-to-end workflow. Resolve is still best for colorgrading and fine details, but if you just want to get a project released on time, nothing beats FCP.
I felt that FCP was underpowered for compositing and grading so I switched from paid FPC to unpaid Resolve. But I don't really edit that much. Resolve is good enough for me for now.
Interesting. I used to daily drive <https://github.com/asmvik/yabai> for almost a year until a major macOS update broke it and I just didn't have it in me to diagnose the issue. I'll bookmark this for future adventures, thanks!
I’m not an FE engineer but have found myself working very closely with the whole stack recently, which includes an SPA. We use html, JavaScript, Alpine for reactivity and Supabase realtime subscriptions.
It seems … okay? I feel like I can reason about it. But I worry I’m missing something that’s going to come back and bite us later because we haven’t adopted a framework.
Would be silly to rate your stack without knowing more about what it is and its constraint.
If I had to judge it based on this alone post alone:
Great, seems like a straight forward stack. Would happily work on it.
Only criticism, to get all the ergonomics out of alpine, you sometimes have to lax some CSP or use the CSP build. Not necessarily a deal breaker, it is what it is.
reply