@FUCORY I have been using a variant of this and it has been working really well
https://t.co/7UhjSdZbsB
Got it integrated into custom commands, my repos are way more tidy now, and it does a better job at keeping track of the work done and to-do
Weโre beyond excited to soon launch our platform on Sonic! ๐
With breakthrough innovations like the Sonic Gateway, Chainlink CCIP, and ecosystem growth plans like Sonic Boom, weโre more than ready to grow and improve the ecosystem together.
As we continue building on our successes, weโre primed to onboard the masses and push Sonic DeFi to new heights
Equal is Sonic.
$EQUAL ๐ค $FTM ๐ $S
@parkerhendo@JustJake@Railway Oh, thanks!
As far as icons go, I would like them to work the same as icons for services, you can give it a URL and it just works.
I get the concept, and it's great, but a good chunk of people, me included, use them with NextJS, which is hard to host outside of Vercel / Amplify, and the experience with those two leads to having to deal with cold starts. If you know of other hosting options where those can be avoided, please share. I'd love to run my projects there.
@vimtor@Railway@helloSQD@ponder_sh Yeah, I keep a channel connection open, and on each batch of blocks I send the formatted events to the RabbitMQ instance.
@DylanZemek@tannerlinsley@tan_stack tRPC has unmatched DX, nonetheless I personally care more about performance and UX, it just so happens it also has that in most cases
@vimtor@Railway Self hosting @helloSQD, I like @ponder_sh's SDK a lot more, but the performance from SQD is a lot better since they're not RPC dependant for historic data
@devagrawal09@tannerlinsley@tan_stack I was parsing urlParams in the server to provide the client components with hydrated state so it wouldn't have to read the URL on the client, just trying to save a few render cycles.
I don't do any server side data fetching, also no SSR, everything is served as static content.
@devagrawal09@tannerlinsley@tan_stack That's what I thought, but if that's the case, why did I see a 5-10s delay when adding a serverside URL parser? the execution itself is under 10ms. The delay is completely gone if there's no serverside shenanigans going on.
@Mahmut_Jomaa@tannerlinsley@tan_stack No, if you run your tRPC API on its own separate server with node, there will be no cold starts because it's not serverless