retropragma

TypeBox is similar by virtue of its goal of its runtime types matching JSON Schema's data model without need for conversion.

That's because "minimum length" cannot be enforced in TypeScript. Maybe you already know this.

I'm not a Typia user myself, but my RPC framework has the same feature, and the MinLength issue you mentioned doesn't crop up if you only use the type tags at the client-server boundary, which is enough in my experience.

An interesting development with Typia is that it will need to be rewritten in Go to work with TypeScript 7. https://github.com/samchon/typia/issues/1534#issuecomment-27...

This is because it relies on patching the TypeScript implementation. I'm curious if its approach is even feasible with Go?

Highly doubt this story is true or Bob didn't incite the anomalous behavior

Why would I use this over keyspace notifications in redis?

Every office needs nuts and raisins

Likely never, as those platforms are continuously updating at no cost to the siphons training their LLMs on them

Lmao, HN will complain about anything. Leave the guy alone

I really want a tool like this that can extract a function and its dependency graph (to a certain depth maybe, and/or exclude node_modules).

I wrote this library [1] and hope to add the fine-grained "reference resolution" utility to it at some point, which could make implementing such a tool a lot simpler.

[1]: https://github.com/aleclarson/ts-module-graph

It's just shitty prompt design

You sound like someone who might be intrigued about what I'm building.

Raw SQL (or PL/pgSQL which can be quite powerful) with generated, type-safe client "bindings" (TypeScript functions). It also includes "declarative SQL schema" (instantly update the schema of your dev DB on file save). Generated migrations and "seed scripts" are also on the roadmap.

If any of that interests you, check it out (https://github.com/pg-nano/pg-nano). I would also love to discuss it with whoever's reading this on Discord (@aleclarson).

Hey, I'm developing a different approach that may appeal to a Kysely user such as yourself. I'd be glad to get your thoughts on it :)

Raw SQL (or PL/pgSQL which can be quite powerful) with generated, type-safe client "bindings" (TypeScript functions). It also includes "declarative SQL schema" (instantly update the schema of your dev DB on file save). Generated migrations and "seed scripts" are also on the roadmap.

If any of that interests you, check it out (https://github.com/pg-nano/pg-nano). I would also be happy to discuss it with you on Discord (@aleclarson).

Manual type declarations are error prone, tedious, and subject to drift. Meanwhile, query builders are clumsy and sometimes limiting or buggy, so I don't blame you for betting on raw SQL.

I'm building a middle ground of sorts. Raw SQL (or PL/pgSQL which can be quite powerful) with generated, type-safe client "bindings" (TypeScript functions). It also includes "declarative SQL schema" (instantly update the schema of your dev DB on file save). Generated migrations and "seed scripts" are also on the roadmap.

If any of that interests you, check it out (https://github.com/pg-nano/pg-nano). I would also love to discuss it with whoever's reading this on Discord (@aleclarson).

This? https://pomb.us/build-your-own-react/

What is Sinatra and why should I care if it's built with it?

The smallest app built with Tauri is 500 KB.

[1]: https://tauri.app [2]: https://syntax.fm/show/821/is-tauri-the-electron-killer/tran...

Send it to both?

There is no responsibility in open source. It's the wild West. Anyone with expectations of you is simply new to the scene and doesn't get it yet.

Forking is a thing. People don't do it enough. GitHub doesn't make it easy to find active forks.

Please keep the cheeky reductionist takes to yourself

Well, it goes both ways. Yes, the algorithm is simply rewarding content styles that apparently people "want to see more of". Of course, this metric is fuzzy. Twitter et al don't have perfect information here. All they know is certain content gets engaged with more. So it's both the people to blame and the algorithm. You can't really blame either side; capitalism values attention at all costs, while people naturally engage with certain content styles that don't necessarily breed the most nuance or positivity.

I actually have a system designed that would fit your desired attributes exactly. I don't know when I'll get to building it, but I do believe what you want is achievable. But that's all I can say, because when it comes to something like this, inventing the system is half the battle.