3 ms·
pocketbase on rust. The demo gives a good impression, if I have time I'll play with your project
by lavren1974 2y ago
pocketbase on rust. The demo gives a good impression, if I have time I'll play with your project
- desireco42 2y agoI came here to understand what is the use-case of this, thank you!
- ripley12 2y agoI also found it kind of hard to understand what it's for from the docs. Logging into the demo UI (linked on the GitHub README) helped a lot.
- fastball 2y agoAnd uses V8 as the JS runtime so you can use modern JS language features (goja in pocketbase is ES5 only).
- d1sxeyes 2y agoWell yes but how often do you have to write a JS extension for PocketBase that needs to be super performant and use modern JS features?
- fastball 2y agoAll JS I write in 2024 is ES6+ (usually more like ES2022+)
- d1sxeyes 2y agoI think probably if you worked through line-by-line you’d find a lot of it is valid ES5 as well (and GoJa does actually support a lot of ES6, see https://github.com/dop251/goja/milestone/1?closed=1 https://github.com/dop251/goja/milestone/1?closed=1). Also, what features do you need to code in JavaScript to extend PocketBase functionality?
- fastball 2y agoAnything you want to write in JS. After all we are comparing Trailbase to Pocketbase, both of which allow you to write application logic in JS.
- d1sxeyes 2y agoThey do. My point is that for the vanishingly small number of use cases where you need to write application logic in PocketBase, and you need to write it in JavaScript, and you need to use unsupported super modern ES6 features, you might prefer Trailbase, but otherwise PocketBase is more polished at this point.
- trailbase 2y agoIMHO, this will greatly depend on your use-cases. If you have a rich client app, e.g. mobile or PWA, most of your logic will go into your client by default. However, there might be some code you want to run on the server in a trusted environment, or use some existing JS library for mobile, or have an otherwise mostly static web app, ... depends