gqless VS datasette

Maybe GQLess is for you? It's a client that magically creates a query from they way you use objects in your react components.

Yes! We announced experimental support earlier and here's the new spec we're implementing that will support all databases and remote schemas too.

https://github.com/hasura/graphql-engine/issues/6991

General support for inherited roles is one of the things I'm most excited about because it makes a bunch of hard things around reusing and composition so easy.

This improvement plays really well along with things like "role-based schemas" so that GraphQL clients have access to just the exact GraphQL schema they should be able to access - which is in turn composed by putting multiple scopes together into one role.

Also interesting is how well this could play with other innovations on the GraphQL client ecosystem like gqless[1] and graphql-zeus[2] because now there's a typesafe and secure SDK for really smooth developer experience on the client side.

[1]: https://github.com/gqless/gqless

GQless: A GraphQL client built for rapid iteration\ (6 comments)

Cannot recommend gqless highly enough for making graphql actually fun to use and closer to something like meteor/firebase syntax[0].

And I’ll self-promote, but I’ve been working on what I consider to be a “next generation” style system for React that solves my biggest issue with it currently: being able to performantly write styles in a nice syntax that optimize for both web and native. Called SnackUI, though it’s still in beta[1].

[0] https://gqless.com

[1] https://github.com/snackui/snackui

On the GraphQL side you can use gqless[0] (or the improved fork I helped sponsor, here[1]). It's by far the best DX I've had for any data fetching library: fully typed calls, no strings at all, no duplication of code or weird importing, no compiler, and it resolves the entire tree and creates a single fetch call.

[0] https://github.com/gqless/gqless

[1] https://github.com/PabloSzx/new_gqless

Simon Willison's github would be a great place to get started imo -

https://github.com/simonw/datasette

I'm a fan on simonw's datasette/dogsheep ecosystem https://datasette.io/

I use Anki the exact same way. After a lifetime of learning I have accepted that I will never read over anything I write for myself voluntarily - so my two options are:

1. Write an article so good I can publish it and look it over myself later on. I did this last year with https://andrew-quinn.me/fzf/, for example.

2. Create Anki cards out of the material. Use the builtin Card Browser or even https://datasette.io/ on the underlying SQLite database in a pinch to search for my notes any time I have to.

Were you aware of, or tempted by https://datasette.io/ for creating your solution?

Browsing HN, GitHub and the like we get to see a huge variety of software products and code bases.

I often see products and think - if this product X, got together with Y, it would be pretty cool - kind of like if they had a kid together.

Not too literally, but more on the conceptual level - my level of programming is low.

E.g. Just some....

- pocketable.io & datasette (+with some more charting) [https://pocketbase.io, https://datasette.io]

You might like the Datasette project: https://datasette.io/

I don't think they are desperate for contributions but it's a welcoming environment and a fun project to hack on. You'll learn a lot just from reading the source and the incredibly informative PRs. The creator is a really talented developer with a great blog which shows up on the HN front page often.

Last year I worked through the challenges using VisiData, Datasette, and Pandas. I walked through my thought process and solutions in a series of posts.

> uploads of boring raw excel data and receive a nice UI

https://datasette.io/