12,203 karma · joined July 29, 2008
jason@...
https://vyrotek.com
https://x.com/vyrotek
https://vyrotek.itch.io
https://store.steampowered.com/app/210870/Cloudberry_Kingdom...
It's the dream dev experience I've been chasing. I'm trying to get as close as I can using auto-generated gRPC-Web.
I would love something like https://orval.dev for gRPC-web. Have I missed something or is it just early to expect it?
I tried a few libraries but couldn't get them to work or would generate unappealing results. I believe I'm hitting this issue with my local experiments. https://github.com/grpc/grpc-web/issues/535
UPDATE: I was able to get something working with these from a ReactJS app!
Server: https://learn.microsoft.com/en-us/aspnet/core/grpc/grpcweb
Client TS Gen: https://github.com/timostamm/protobuf-ts
Isn't this exactly how Gumroad started too right here on HN?
I'd love to know how folks deal with this. We've used various health co-ops. Still not great. I feel like it's one of the biggest factors holding people back from starting a business.
When you owe the bank several billion, the bank has a problem.
When the unregulated-bank owes billions to millions of people, I guess the people have a problem?
Traditionally, other materialized view implementations have very strict query requirements though. The queries had to be deterministic. No left joins, dates, etc. This is required in order to properly detect when data changes "impact" the view. I wonder how they get around it.
Update: Ah, ok! Here's a write up on how it works a bit. My last startup built a system like this specifically to power a gamification engine. Would have been nice to have this 10 years ago.
https://planetscale.com/blog/how-planetscale-boost-serves-yo...
> The Boost cluster lives alongside your database’s shards and continuously processes the events relayed by the VStream. The result of processing these events is a partially materialized view that can be accessed by the database’s edge tier. This view contains some, but not all, of the rows that could be queried.
Instead, an API and the endpoints are designed for a specific client. (e.g. A Mobile App or SPA) For us, this also meant a more RPC based API where and reusability is managed after the network hop.
My current SaaS company has 8 web projects and 1 core project. Some of the web projects are SPAs using BFF and others are APIs for customers or our mobile app. They aren't tiny sites. We're up to ~500 controllers. All in a single repo and automatically deployed as a monolith. We have a super small but very productive team which we attribute to this simple design.
We suspected it even reached other schools in the district.
Good times.
Apps may allow users to browse NFT collections owned by others, provided that the apps may not include buttons, external links, or other calls to action that direct customers to purchasing mechanisms other than in-app purchase.
This seems like it restricts a lot of the imagined use cases folks had. You can't use them to unlock functionality.