ryanrasti

8 ms·

31.
by ryanrasti 1y ago
The fundamental SaaS lock-in comes from bundling two things: 1. A declarative, stable interface 2. An expert support/ops team I think the path forward is to unbundle them. We're already solving #1. Nix has the best potential to be
32.
by ryanrasti 1y ago
Agree with the other comments that it's not fundamentally innovative and no one with a sense of privacy wants to ship all browsing data to one of the mega-AIs. BUT -- that's missing the strategic point here: - Everyone realizes th
33.
by ryanrasti 1y ago
+100 to you both. This is the classic tradeoff: powerful, centralized DB logic vs. clean but often anemic app code. I'm building Typegres to give you both. It lets you (a) write complex business logic in TypeScript using a type-safe ma
34.
by ryanrasti 1y ago
Ah yeah great callout, that's very plausible. We used Absinthe heavily to power our GraphQL API.
35.
by ryanrasti 1y ago
I share the OP's enthusiasm for Elixir, but as the CTO of a startup that ran it for three years in production, our experience was a mixed bag as the codebase grew. The core promises of the BEAM (concurrency, fault tolerance) absolutely
36.
by ryanrasti 1y ago
Author here. Thanks to `kqr` for sharing this! I wrote this post to distill the tough lessons from using Nix in production for three years with a small team building a full-stack Elixir/React app. My core take is that Nix has already s
37.
by ryanrasti 1y ago
Thanks, glad you think so!
38.
by ryanrasti 1y ago
Thanks! That's a great question. First off, I'm a huge fan of Kysely and it's a massive source of inspiration for Typegres. You've nailed the two big differences: * Architected for Business Logic : The primary innovatio
39.
by ryanrasti 1y ago
Thanks for the great points and link to SafeQL! I'm a big fan of its approach to bringing type safety to raw SQL strings. For static queries, it's a fantastic solution. My take is that while "Just use SQL" is healthy pus
40.
by ryanrasti 1y ago
I'm working on Typegres, a new data layer for the modern stack (TypeScript + PostgreSQL). My take is that for years, ORMs have hidden the power of PostgreSQL behind generic, database-agnostic abstractions. This made sense in 2010, but
41.
by ryanrasti 1y ago
> but I don't we've solved the map problem. Agreed! If we use `map` directly, Cap'n Web is still constrained by the ORM. The solution would be what you're getting at -- something that directly composes the query build
42.
by ryanrasti 1y ago
Really nice summary of the core challenges with this DSL/code-as-data pattern. I've spent a lot of time thinking about this in the database context: > No printf debugging Yeah, spot on. The solutions here would be something lik
43.
by ryanrasti 1y ago
Thanks, Kenton! Really encouraging to hear you find the idea interesting. Right now I'm focused on Postgres (biggest market-share for full-stack apps). A sqlite version is definitely possible conceptually. You're right about the b
44.
by ryanrasti 1y ago
Agree -- I think that's a powerful generalization you're making. > We're often nowadays working in dynamic languages, so they become essentially the frontend to new DSLs, and instead of defining new syntax, we embed the AS
45.
by ryanrasti 1y ago
Agree, and to add, from what I see, the main issue is that server-side data frameworks (e.g., ORMs) aren't generally built for the combination of security & composability that make them naturally synergize with Cap'n Web. Anot
46.
by ryanrasti 1y ago
> I find the choice of TypeScript to be disappointing. Genuinely curious, is the disappointment because it's limited to the JS/TS ecosystem? My take is that by going all-in on TypeScript, they get a huge advantage: they can ski
47.
by ryanrasti 1y ago
> Not sure why this doesn't seem to be a common practice TBH, might be missing something. Yeah... I've been deep in this problem space myself. The two big points of friction are: 1. Requiring a build-step to generate runtime co
48.
by ryanrasti 1y ago
Hi HN, I'm Ryan, the creator of Typegres. For years, I've felt stuck between two unsatisfying options for talking to my database: use a traditional ORM that forces you to learn its quirks instead of Postgres itself, or write raw S
49.
Show HN: Typegres – I made every Postgres function type-safe in TypeScript(typegres.com)
1 points by ryanrasti 1y ago|1 comments
50.
by ryanrasti 1y ago
Haha! That gave me a good laugh.
51.
by ryanrasti 1y ago
Agreed the privacy that keeping AI "in a corner" appeals to me too. The fundamental catch here is that 80%+ of the future benefit will likely come from the very thing that erodes privacy: deep integration and context. Imagine if a
52.
by ryanrasti 1y ago
> With Gemini Apps Activity turned off, their Gemini chats are not being reviewed or used to improve our AI models. Indeed bizarre as the statement doesn't say much about data collection or retention. More generally, I'm confli
53.
by ryanrasti 1y ago
Yeah good point re: functional programming and reasoning. When there's no global mutable state you only need generally need a smaller context to figure out what's going on. I imagine it's the same for LLMs.
54.
by ryanrasti 1y ago
Awesome, go crush it!
55.
by ryanrasti 1y ago
> Q: Can I monitor a phone without them knowing? > A: Yes, you can monitor a phone without them knowing with mobile phone monitoring software. The app is invisible and undetectable on the phone. It works in a hidden and stealth mo
56.
by ryanrasti 1y ago
Wow -- tried it out and looks quite impressive. The granularity of data for these companies is amazing! My last startup was selling to SMBs. It looks like Sumble is most likely targeted at mid-market and enterprise companies. Any plans to e
57.
by ryanrasti 1y ago
> With the carriage / car situation, individual transportation is their core business, and most companies are not in the field of Artificial Intelligence. Agreed. The analogy breaks down because the car disrupted a single vertical b
58.
by ryanrasti 1y ago
Congrats on the launch! I was wondering -- how does the point-based rating system work?
59.
by ryanrasti 1y ago
> I'm curious about the areas you've struggled with, particularly number 3. At the beginning things were very quick like your experiences. It's when we built up a larger code-base (we're currently at ~100K Elixir LoC
60.
by ryanrasti 1y ago
Thanks for compiling this. As a CTO running Elixir for 3 years (1 year of MVP deployed in production), my take is that while the BEAM's fundamentals are incredible, the ecosystem and DX have major trade-offs depending on the applicatio

More ›