HNHacker News
TopNewBestAskShowJobs

kandros

156 karma · joined February 2, 2015

@kandros5591

https://jagasantagostino.com

submissionscomments
kandros··on Better HTTP server routing in Go 1.22
I agree on paper, but story shown how the combination of "I like it, but I want it just a little bit different" combined with something somehow new is a recipe for new weekend projects
kandros··on Better HTTP server routing in Go 1.22
lol no, will start the proliferation of more different abstractions over it
kandros··on Sonoma's log gets briefer and more secretive
Changing to a yearly release cycle is what made quality and stability a non-priority. MacOS has been buggier and buggier since
kandros··on Architecture diagrams enable better conversations
I’ve used old xstate visualizer (like 4 years ago) as a communication tool to review flows with domain experts before implementing something, made conversation and spotting problems so easy
kandros··on tRPC – Build and consume typesafe APIs without schemas or code generation
Take a look at https://github.com/pacedotdev/oto
kandros··on FiraCode: Free monospaced font with programming ligatures
Started using Comic Mono as a joke but I actually like it now. https://dtinth.github.io/comic-mono-font/
kandros··on Rustle: Svelte compiler rewritten in Rust
I think it means using rusty-v8 directly or it's API via Deno to SSR in deno runtimes or similar?

https://deno.com/blog/roll-your-own-javascript-runtime

kandros··on Hasura raises $9.9M to simplify GraphQL
I gave it a try, to be honest, I feel it too cumbersone, I expected it to use already available mutations not just copying existing types.

What I really want/need is custom logic that run IN the resolvers of already available query/mutations with the request as input and the possibility to either return an error or modify the payload before it hit the database

but I know is still in preview, will check it again when released

kandros··on Hasura raises $9.9M to simplify GraphQL
The sync part is very interesting, I like that it’s happening after the mutation so that Im not forced to reimplement the graphql types myself.

Will give it a try, thanks

kandros··on Hasura raises $9.9M to simplify GraphQL
The situation you are referring to is actually a great plus, If you change the data model in you backend, you client consume it and thus depend on it, so you still have to change the frontend code anyway, knowing exactly what you can ask and how it will come back makes it a very powerful developer experience with a lot of test that don’t need to be write thanks to tooling around a type system and a faster feedback loop.
kandros··on Hasura raises $9.9M to simplify GraphQL
While I like and enjoy many aspects of code generation such as this or Prisma, In real world scenario it just doesn’t feel right.

Imagine a very simple scenario, you want to add some validation based on business requirements, in order to do that you have to have a server with custom endpoints or a custom graphql server (thus copy most of what hasura generates) to implement your own validation

The only situation in which I consider this a really good solution is in a CQRS system where the database attached to hasura is read only via graphql and the data is inserted by other services making it a typesafe single source of truth to read from

kandros··on Hasura raises $9.9M to simplify GraphQL
GraphQL is much easier to pickup and get productive than most people think, most of the times all you have to do is writing resolvers (functions) instead of http handlers (functions)

On the client side is the same, following any getting started guide can explain 90% of what you need to know in a single day

← PreviousPage 3 of 3