postgrest-js VS nimble

At one point, I really thought it was used in Supabase. But I guess they only wrote the js wrapper for it. https://github.com/supabase/postgrest-js

Came here to mention Hasura as well (not sure of it's popularity though) https://hasura.io/graphql/database/postgresql

Min/Max looks like it still has to be done via RPC (with sample code here) https://github.com/supabase/postgrest-js/issues/206

There's nothing wrong with this and they're pretty open about it. But the SDK they provide for direct database operations is the weakest of the ones I've used, when it should be the strongest I think. It leverages PostgREST which is a tool for auto generating REST APIs from schemas. From the README: "The goal of this library is to make an "ORM-like" restful interface."

Looks like there's an open github issue that might answer some of your questions: https://github.com/supabase/postgrest-js/issues/303

I think it’s great too. I wish they would shore up some of their existing releases though. Probably most notably, the ability to query aggregates via the officially supported route is missing: https://github.com/supabase/postgrest-js/issues/206

The workarounds suggested are not ergonomic for most use cases and it feels pretty out of place for such basic functionality to be missing in what otherwise feels like a pretty full featured product.

Their Realtime product is another example of something that languishes while new features get launched.

I haven't completely understood what you are looking for but I think Supabase could be potential useful alternative backend for you supabase.io ?

I used postgrest-js to communicate with my PostgREST endpoint. The library is easy to use and does everything for you.

yes you're right. The JS library is a thin wrapper around PostgREST's API (https://github.com/supabase/postgrest-js)

Supabase now offers a few more features which integrate with the Postgres database - File Storage (s3), Authentication, Deno Functions, and Realtime (database change listeners). Each of these services is a standalone server and each has a corresponding JS library.

"supabase-js" wraps up the modular JS libraries into a single library for convenience

* Swift Libraries are now underway thanks to @satishbabariya [2]

We still have a long way to go for mobile support, but the Apple logins is a big one. If you ship an app to the App Store with any third-party logins, you're required to enable Apple logins as well. While this sounds like a bit of over-reach, it's actually quite cool - if you use Apple login they obfuscate your email so that the 3rd party app don't get access to your personal data. Quite nice!

[0] CSV: https://github.com/supabase/postgrest-js/pull/187

I was using Nim for some of last years Advent of Code problems. I was mostly liking the syntax. Was a bit bother by the standard library have a snake case and camel case reference for each function (if I'm remember that correctly).

At the time nimble also required me to have NPM to install the the Nim package manager, Nimble. This was not ideal, but looking at [the nimble project install docs](https://github.com/nim-lang/nimble#installation) it seems like it is now package with the language.

Might try dusting it off for some AoC puzzles this year :)

nimble develop -g doesn't work A possible solution is to add "g" to where "global" is placed.

I meant it's unfortunate that Nimble has no standard system-wide library management. It's one of the mains thing holding Nim back from being more prevalent in the Linux sphere in my opinion.

`nimble` is the package manager for the programming language `nim` [1].

From [2], we can see that `nimble scss` simply generates the CSS files for the frontend.

The benefit of OSS is you can answer these questions yourself with a bit of poking around! IMO this is a fairly standard installation process, maybe the fact that it's using Nim instead of a more mainstream language makes it look more daunting than it is. The only out-of-the-ordinary thing here, IMO, is `nimble build` instead of `make build`.

[1]: https://github.com/nim-lang/nimble

[2]: https://github.com/zedeus/nitter/blob/master/nitter.nimble

Something I'm excited about: v1.6.2 integrates support for (not yet released) Nimble[1] v0.14, which introduces lockfiles. I've had terrible experiences with lockfiles in JS land, but they are sorely needed for Nim projects as (fingers crossed) they'll allow for reproducible builds without having to resort to the nimbus-build-system[2]. The latter isn't completely horrible — a lot of much appreciated hard work has gone into it, and it's been a real workhorse — but some days it feels like a big ball and chain.

[1] https://github.com/nim-lang/nimble#nimble

[2] https://github.com/status-im/nimbus-build-system

So you wouldn't have a problem with a package manager where the configuration is in the same language, such as Nimble?

if you structure your project with nimble (which can be be used for both libraries and applications) you can use nimble build and nimble run. While I do use nimble for managing dependencies for projects I don't use these commands that often while developing, e.g. because I'm working on a single test or something like that.

Having similar syntax to Ruby makes it easier to port Ruby code to Crystal (ex: digest-crc -> digest-crc.cr). The Crystal stdlib is very complete and they have a growing "shards" ecosystem, roughly the same age as Rust's https://crates.io or Nim's nimble. You should look into Crystal again.