Live data from Hacker News

Pocketbase – open-source realtime back end in 1 file

pocketbase.io

91–100 of 211 posts

Re: Pocketbase – open-source realtime back end in 1 file

#91
post #74

I would love something similar but for frontend. I like developing backends, but writing JavaScript is to tiring.

In the last years a market for "no code" software has sprawled, just etch the interface on a tables SPA, plug Okta, plug your backend or Firebase to their apis and you should be set.

You can also find dozens of drag n drop builders and block editors working for modern frontend dev, there are a lot for React for example, just vibe code the components.

Re: Pocketbase – open-source realtime back end in 1 file

#93

I've been trying out Pocketbase on a side project idea. I'm super impressed! Having worked for many years on Django projects, Pocketbase seems like a perfect fit for those small to medium sized projects for which you don't want to create and maintain a traditional backend for. Happy to answer any questions.

I’ve been using on a personal side project - but found that LLMs seem to be permanently confused over how to interact with pocketbase - to the point where I’ve even tried creating a Claude Skill to try and reduce the confusion. Wondering if anyone else has had a similar experience?

From the top of https://pocketbase.io/faq/

> If you don't have the time to at least skim through the documentation and you plan to solely rely on some AI tool, then please do NOT use PocketBase!

It's a niche little product that's alpha-level quality and changes frequently, I don't know why you would expect LLMs to be good at it.

Re: Pocketbase – open-source realtime back end in 1 file

#95
post #84
post #79

Earlier quoted context omitted.

What is Lagrange? I couldn’t find any project in the context of LLM or knowledge graph.

They said they hacked a Gemini server, Lagrange is a Geminispace browser. https://github.com/skyjake/lagrange

I also somehow thought a Google Gemini MCP server.

Re: Pocketbase – open-source realtime back end in 1 file

#96

I've been trying out Pocketbase on a side project idea. I'm super impressed! Having worked for many years on Django projects, Pocketbase seems like a perfect fit for those small to medium sized projects for which you don't want to create and maintain a traditional backend for. Happy to answer any questions.

I’ve been using on a personal side project - but found that LLMs seem to be permanently confused over how to interact with pocketbase - to the point where I’ve even tried creating a Claude Skill to try and reduce the confusion. Wondering if anyone else has had a similar experience?

I tried to use LLMs to help me with server-side pb coding, but it was mostly a flop. LLMs don't have an up-to-date state of pb's API. 2 out of 3 times the LLM would give at least a hint how to go about something and the rest is me manually editing the code, reading the docs or looking at pb's source code. All in all, I consider it a nice "pair-programming" type of experience but one can't rely on LLMs to do the pb work for you.

Re: Pocketbase – open-source realtime back end in 1 file

#97
post #35
post #19

Is this really realtime? From looking at the description it sounds more like subscriptions to events of data changes that are dispatched close to the data operation How would realtime even work for a networked system going over tcp? https://en.wikipedia.org/wiki/Real-time_computing

I believe there is no contradiction with the definition from the linked article? > A system is said to be real-time if the total correctness of an operation depends not only upon its logical correctness, but also upon the time in which it is performed. Real-time systems, as well as their deadlines, are classified by the consequence of missing a deadline: > Hard – missing a deadline is a total system failure. > Firm –…

Really? I couldn't really see anything wrt degraded performance from my casual glance.

To me, It looks like there are just best effort events with literally no constraints or handling for delays etc

And again, I didn't see how you'd even implement such without being on both sides of the networked connection

I guess I just have to accept that the term has lost it's meaning at this point and can be used for whatever whoever wants to use it for

Re: Pocketbase – open-source realtime back end in 1 file

#98
post #57

Trailbase is the same concept, but written in Rust instead of Go.

Looks pretty nice! Do I understand correctly you can have it run any JS in an endpoint too? Seems you could host your whole app with this https://trailbase.io/getting-started/first-ui-app/#custom-en...

Hi! Depends on what you mean by "any JS". Many JS ecosystems depend on an environment. For example, there are browser environments where you get a common baseline with some vendor differences, there's the server where you get common baseline across nodejs, deno, bun with some differences and also proprietary APIs. Long story short, any vanilla JS (ES5,ES6, probably even common) should be able to run. There's some standard WASI APIs to do I/O through the WASM runtime and a few TB specific APIs.

Re: Pocketbase – open-source realtime back end in 1 file

#99

I see Pocketbase, I upvote. Using it in a few production apps and it's been a very solid experience. Some breaking changes from time to time, but generally very solid. Also has a lot of extensibility built in. Sometimes you might hit a scenario where it doesn't provide what you need, which is when things can get a bit hairy, but nothing a skilled dev can't work around.

This was my exact comment, thanks.

It is a very good piece of work, and extensible with JS (I just tried that). I have a fear about the future because the dev is alone, and responds alone in the discussions. He is also quite, how to say, "rough" in the interactions, which I can completely understand, being the one pulled around by everyone.

This is a very, very good piece of work when you need to decorrelate the back from the front

Re: Pocketbase – open-source realtime back end in 1 file

#100

Earlier quoted context omitted.

TrailBase has a comparison page https://trailbase.io/comparison/pocketbase/

I appreciate their honesty. After a quick look I’d give another point to Pocketbase for it’s admin UI. The TrailBase one is pretty sloppy (on mobile at least), and looks like it’s using bootstrap. Pocketbase has a sense of quality/care around it that seems missing.

You won't get any argument here. PocketBase's is very polished and friendly. I fell back onto a popular pre-existing UI component system called shadcn (which does look a bit like bootstrap), not only because you gotta start somewhere but also because I'm not the caliber of UX designer Gani is :bow:. If you have the time, I would appreciate any feedback on how to improve.

I'm a bit surprised on the mobile comment, since last I checked PB's UI wasn't responsive, i.e. you had to scroll a lot horizontally on mobile. Despite it's missing polish, I tried to make TB's at least work well on mobile. Could you elaborate? - thanks

Post reply on HN