Skip to main content

Show HN: Soliciting post placement on Hacker News https://ift.tt/jsnubQd

Show HN: Soliciting post placement on Hacker News Hey, HN -- I just received the following email and I'm not sure what to do about it. Obviously I want to discourage requested-posting like this; is there some structured way that we can do that? One of the things I love about HN is how high the signal-to-noise ratio is relative to...pretty much the rest of the internet. I wouldn't ordinarily call someone out like this, but I want to innoculate HN against this sort of thing. ---- Hey doches, Not sure if it's conventional, but thought I'd ask anyway. Would you be open to posting about my product on Hacker News? I understand that similar to Product Hunt, HN gives higher priority to users with higher karma. I usually keep up with recent discussions via RSS feed on Feedly, but almost neve post. So I thought I'd reach out to someone that has authority. My product is called Popupular and it helps embed just about anything into a popup via a Google Chrome extension. [rest of email truncated] June 15, 2022 at 11:17PM

Comments

Popular posts from this blog

Show HN: TypeScript query builder with full type inference https://ift.tt/xZp9HOm

Show HN: TypeScript query builder with full type inference Hey HN! Colin here - a TypeScripter, open sourcer, and engineer at EdgeDB. As the creator of Zod and tRPC, I'm interested in designing tools/APIs that use type inference and generics to make life easier for devs. This query builder represents another step in that direction. We set out to build an EdgeQL query builder that can express queries of arbitrary complexity (EdgeQL has feature parity with SQL, roughly) and infer the static type of the query result. We introspect the database and generate a schema-aware client that represent any query, including ones that use built-in functions, operators, string/array/tuple indexing, aggregations, conditionals, type casting, subqueries, computed properties, etc—things most ORMs can’t represent. This post mostly discusses the API design, which I think will be interesting regardless of familiarity with EdgeQL. I’d love to see some of these ideas bleed into future generations of TypeSc...