151–154 of 154 posts
I think it's time for me to move on from Raycast. It's decent, but I genuinely hate this direction. Shove AI in to every orifice, doesn't matter if anyone wants it. I guess they're trying to make more money and Raycast is a bit of a dead-end there.
Not to be a curmudgeon, but why are they spending time on this? As an enthusiastic Raycast user, I would prefer to see them focus on making Raycast better, not finding new ways to jump on the AI bandwagon.
Earlier quoted context omitted.
I've vibe coded all sorts of apps for my macbook. A better replacement to iStat Menus. A local-only voice to text whisper.cpp transcriber I can globally use while holding ctrl-semicolon. A menubar app that manages blocky and can easily turn it off or change dns. A tool like hammerspoon but I configure it via nix-darwin and it has no cruft. All of these are apps that use 30MB memory and are better than the apps they r…
Neat! What does the stack look like?
For less trivial apps, use Elm architecture for a pure, testable core.
Earlier quoted context omitted.
Founder of Raycast here so obviously biased but you’ll be surprised. You get a working app one-shotted pretty much all the time. Sure if it is something more complex you might need a few more prompts. Just to give you some examples on what we’ve seen: - Our support team runs on Glaze apps to review Raycast extensions. It connects to GitHub, checks out code locally, gets realtime updates and so on. - The sound agency…
Does it generate native apps, or just Electron?