Live data from Hacker News

Viewing profile — randomwebdev

randomwebdev

HN member
Joined
Thu, Jul 07, 2022, 12:42 PM UTC
HN karma
453
Public activity
29 items

About randomwebdev

No profile information was provided.

Recent public activity

  1. comment
    Comment #42948526

    > As to 4x, my concurrency levels are significantly lower which could certainly explain it. Yes I noticed that too so that it is very likely the reason. In all cases my initial com…

  2. comment
    Comment #42947930

    > I'm not sure this is expected but it didn't seem to make much of a difference with my setup I expect it to be faster but it is also possible that maybe in your specific collectio…

  3. comment
    Comment #42940021

    (Disclaimer: I'm PocketBase author) It is nice to see more backends utilizing SQLite. The benchmarks and the Comparisions section also seem well done. Just a nitpick - list the ver…

  4. comment
    Comment #39764422

    Hi, PocketBase author here. Keep in mind that PocketBase do a lot more than just executing a raw DB query. We perform data validation, normalization, serialization, enriching, auto…

  5. comment
    Comment #37348253

    I'm sorry but that doesn't make sense to me (especially your last sentence regarding TypeScript). During development vite has HMR and you don't need to run build after every change…

  6. comment
    Comment #37348150

    I don't understand your concern with it and why this is a problem. I haven't personally noticed the vite/esbuild memory consumption, but I also run build only once at the end befor…

  7. comment
    Comment #37347906

    Why? I think most modern bundlers and spa routers supports code splitting out of the box by just using dynamic imports, aka: `const myComponent = await import("/path/to/component")…

  8. comment
    Comment #35501914

    It is really a cool project. We are using it as a default driver in PocketBase and although it is not a "drop-in" replacement of the CGO alternative `mattn/go-sqlite3` (different d…

  9. comment
    Comment #32047691

    Its not schema free (although you can create a json field and put whatever you want in it). You can define schema via migrations or through the admin UI (see https://pocketbase.io/…

  10. comment
    Comment #32044133

    Currently you cannot create indexes through the admin UI, but it's in my todo. As an alternative, you can always create indexes through DB migrations or add the index directly via …

  11. comment
    Comment #32024426

    There is already a JavaScript SDK ( https://github.com/pocketbase/js-sdk ) that works both in the browser and node. Dart SDK (targeting mainly Flutter) is also on the way. Unfortun…

  12. comment
    Comment #32024322

    The existing admin interface could be used as a very rudimentary content management, but it was really intended for quick internal data explorations and edits. Additionally, curren…

  13. comment
    Comment #32024098

    Currently any additional data transformation is left to the developers to extend via event hooks or custom client side handling. I've worked with CRDT in the past (yjs), but it may…

  14. comment
    Comment #32020201

    Yes, you can subscribe to individual records or collections. User defined filters for the subscriptions are not supported, but it's a good idea and I may consider it in the future.…

  15. comment
    Comment #32020018

    I guess there will be differences from use case to use case, but in general migrating from PocketBase to a more common horizontal supported stack is not different from rewriting yo…

  16. comment
    Comment #32017599

    Yes, built-in sounds better. I'll update it.

  17. comment
    Comment #32016435

    The documentation is not auto generated and is part of the static landing site (built with SvelteKit). I didn't bother open source it because it is kinda messy and a little complic…

  18. comment
    Comment #32016102

    Uploaded files and your database are stored outside of the binary.

  19. comment
    Comment #32015852

    You may want to check Supabase or Nhost in that case. PocketBase was specifically designed to be self-contained and running only on a single server.

  20. comment
    Comment #32015819

    "Collections" stores a single records table meta data (eg. name, fields, validators, etc.), so when you create a new collection a new related table will be created (see https://git…

  21. comment
    Comment #32015571

    Hm, there is nothing preventing you to start multiple services from a single binary. I'm not sure that PocketBase would be suitable for your use case, but it is distributed also as…

  22. comment
    Comment #32015265

    By default PocketBase uses the local filesystem, but you could also configure a S3 compatible storage (AWS, DigitalOcean, Vultr, etc.) from "Settings > Files Storage > Use S3 stora…

  23. comment
    Comment #32014894

    It's implemented in the application, it's not a feature of SQLite, but its very simple and robust - when a record is created/updated/deleted I'm broadcasting the change to all subs…

  24. comment
    Comment #32014675

    Go's default `net/http` package will serve HTTP2 when a https configuration is provided (also most web browsers don't support h2c, aka. HTTP2 without tls). The default limit of ~10…

  25. comment
    Comment #32014538

    Other than some json functions, PocketBase doesn't use too much SQLite specific features, but I don't plan adding support for other databases at the moment. Please also note that P…