←
liolocs1,176 posts
liolocs avatar

liolocs

@diysoftware

Building software to solve my everyday problems

◷ Joined March 2024▧ 185 Photos and videos
liolocs avatar
liolocs@diysoftware·Nov 10

These are the kind of AI benchmarks we need. Max Bittker turned RuneScape into a test for AI models and it's hilarious. Normalise this over "trust me bro" benchmarks

Post attachment
liolocs avatar
liolocs@diysoftware·Nov 4

I do not see myself using Higgsfield after this, and I have since given ComfyUI a try. What do you think, would you still use Higgsfield after this?

liolocs avatar
liolocs@diysoftware·Nov 4

So on Oct 16 ComfyUI tweets: "Higgsfield promised to open-source their entire platform. They didn't. Let's help them." Two weeks, $25,000 in prizes for the best open-source builds on the Comfy Developer Platform.

liolocs avatar
liolocs@diysoftware·Nov 4

Background: Higgsfield CEO Alex Mashrabov said on LinkedIn in Nov 2023, after leaving Snapchat, that the company would "open-source key frameworks" built along the way. That never happened. On the 20VC podcast he said "we open sourced all of it."

liolocs avatar
liolocs@diysoftware·Nov 4

Higgsfield sent a cease and desist order to ComfyUI on Oct 28. ComfyUI is the open source alternative to Higgsfield. This is so ironic: their CEO called open source his "network effect moat", then never actually opened anything.

Last night, @higgsfield sent @ComfyUI a cease and desist (attached) They want the Open Source Higgsfield challenge taken down within 48 hours. Their argument is that our use of the Higgsfield name and that using their CEO's likeness is an infringement violation (man, the irony). Claiming that it makes the event look like Higgsfield is associated with it. This couldn't be farther from the truth, which is that Higgsfield made a promise to open source its product and never did. For the past two weeks, builders have been recreating popular closed apps as open workflows anyone can run. So we asked our community to deliver where Higgsfield failed: apps in the open, built by the community, for the community. We've made it clear that the challenge is organized by ComfyUI and not affiliated with or endorsed by Higgsfield. When we started Comfy, we made the community a promise. Our product stays open, free, and yours. We’ve kept it every day since, and one letter isn’t going to change that. The challenge stays up. Comfy and open source will win!

Post attachmentPost attachmentPost attachment
liolocs avatar
liolocs@diysoftware·Nov 2

Who should skip it: Anyone who wants batteries included and zero setup. That is a real use case, it's just not mine. What's your stack of choice?

liolocs avatar
liolocs@diysoftware·Nov 2

Who should try it: Full stack devs who vibe code whole apps and don't want to get locked into a particular framework.

liolocs avatar
liolocs@diysoftware·Nov 2

1) The ecosystem is young. I had to wire Tailwind and shadcn by hand because the CLI doesn't recognise Primate yet. 2) It's rapidly evolving, apis can change quickly. 3) There's no CMS in the ecosystem yet, you have to code your own.

liolocs avatar
liolocs@diysoftware·Nov 2

6) It is insanely fast and has a crazy small amount of dependencies. Small enough that I stopped thinking about the dependency tree. Now the part that makes me hesitate:

liolocs avatar
liolocs@diysoftware·Nov 2

5) Typed routes you can import straight into a client component. I import the route, pass it to the form, and the types come for free. No hand-written fetch layer, no extra forms library. I don't know another framework that does that.

liolocs avatar
liolocs@diysoftware·Nov 2

4) A store is agnostic to the database. I can map one store to one database and another store to another. You can import stores in any node/bun/deno script and just seed your database.

liolocs avatar
liolocs@diysoftware·Nov 2

3) It works like lego. A TypeScript route next to a Go route. A React view next to a Svelte view. Bun, Node or Deno. Swapping a block is cheap, which is exactly what you want when you're still deciding what the project should be.

liolocs avatar
liolocs@diysoftware·Nov 2

2) I start on a JSON database while the schema is still churning. No migrations while I figure out what the project even is. Once the shape settles, I graduate to Postgres and nothing else changes.

liolocs avatar
liolocs@diysoftware·Nov 2

1) Routes and views live in separate folders, and that stays obvious after an agent has written 40 files. In Next.js the client and server line blurs. Primate's file map does the explaining, so my agent is never confused.

liolocs avatar
liolocs@diysoftware·Nov 2

My framework of choice (primate.run) is great for vibe coding but I still wouldn't recommend it to everyone. Here is the full picture: