Skip to content

Appwrite vs Pocketbase#2896

Open
aishwaripahwa12 wants to merge 1 commit intomainfrom
newcomparisonblog
Open

Appwrite vs Pocketbase#2896
aishwaripahwa12 wants to merge 1 commit intomainfrom
newcomparisonblog

Conversation

@aishwaripahwa12
Copy link
Copy Markdown
Contributor

New comparison blog

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Apr 17, 2026

Greptile Summary

This PR adds a new "Appwrite vs PocketBase" comparison blog post with cover image and cache entry. The content is well-structured and covers deployment, database, auth, functions, realtime, messaging, and SDK differences accurately — with one author attribution issue and one factual inaccuracy to resolve before publishing.

  • Author mismatch: author: aditya-oberai appears to have been copied from another post; the PR submitter (aishwaripahwa12) has a registered author slug aishwari that should be used instead.
  • PocketBase JS runtime: Described as "ES5 JSVM" but PocketBase's official docs state goja supports most of ES6 — this will mislead readers about what syntax is usable in hooks.

Confidence Score: 3/5

Not safe to merge until the author attribution is confirmed correct and the ES5 runtime claim is updated.

The author field almost certainly contains a copy-paste error (aditya-oberai instead of aishwari), which would publish the article under the wrong name. The ES5 JSVM description is a factual inaccuracy that could mislead developers evaluating PocketBase. Both are pre-merge fixes.

+page.markdoc — author field and PocketBase runtime description need attention.

Important Files Changed

Filename Overview
src/routes/blog/post/appwrite-vs-pocketbase-which-open-source-backend-fits-your-project/+page.markdoc New comparison blog post; author field appears to be copied from another post (set to aditya-oberai instead of PR author aishwari), and the PocketBase JS runtime is described as "ES5 JSVM" when current PocketBase docs say goja supports most of ES6.
.optimize-cache.json Image optimization cache updated to include the new cover image hash; no issues.
static/images/blog/appwrite-vs-pocketbase-which-open-source-backend-fits-your-project/cover.png Cover image added at the path referenced in the frontmatter; no issues.

Reviews (1): Last reviewed commit: "new comparison blog" | Re-trigger Greptile

date: 2026-04-20
cover: /images/blog/appwrite-vs-pocketbase-which-open-source-backend-fits-your-project/cover.png
timeToRead: 5
author: aditya-oberai
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Author field doesn't match PR submitter

The author is set to aditya-oberai, but this PR was submitted by aishwaripahwa12, whose registered author slug is aishwari. Every other comparison post authored by the same submitter uses their own slug. If this is intentional ghostwriting, no change is needed — but if it was copied from a template and not updated, the author attribution will be incorrect on the published post.

Suggested change
author: aditya-oberai
author: aishwari


This is where the two platforms diverge most clearly.

PocketBase extends through **JavaScript hooks** running in an embedded ES5 JSVM or by using PocketBase as a Go package and compiling your own binary. JavaScript hooks handle scheduled jobs, custom routes, and record lifecycle events. They are limited to CommonJS modules with no npm packages and no arbitrary runtimes.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 PocketBase JSVM is ES6, not ES5

The post describes PocketBase's runtime as "an embedded ES5 JSVM." According to the official PocketBase docs, the embedded goja engine "has most of ES6 functionality already implemented." Calling it ES5 may mislead readers about what JavaScript features are usable in hooks (arrow functions, template literals, destructuring, etc. all work).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant