A place for developers to talk about building on Farcaster.

/dev

gm folks, i wrote an article describing why i never use ssr and you shouldn't either

criticism will be ignored but you will comment anyway won't you

gm folks, i wrote an article describing why i never use ssr and you shouldn't either

criticism will be ignored but you will comment anyway won't you

https://blog.borodutch.com/i-never-use-ssr-and-you-shouldnt-either/

cto @ bwl.gg (lunchbreak.com), 80M+ users (bdut.ch) 🙏 built @remindme, @mintit, @gpt, @healthbot, farcantasy.xyz

wrong; everything old is new again - only SSR, never CSR, back to where we started: php 😂

The main problem with SSR was the complexity of writing isomorphic code and reasoning about state. With only server side that problem is solved.

Turns out sending 300kB bundles of your (code split) JS on first request is slow

Building Larry, FOSS via @frames, @framesfun /open-frames to help decentralized social win. a16z CSX23. farcasterchannels.com farcaster.id

companies that care about perf (ones that make money) will move to server only again, and all the tooling and ecosystem OSS funding will shift that way so hobbyists will have an incentive to move that way too

writing php style is faster and simpler than most modern JS dev with CSR.

here's one counterexample to "ssr initial load is always slower by magnitudes" where not only is it not a magnitude slower, but it's faster. 

https://medium.com/walmartglobaltech/the-benefits-of-server-side-rendering-over-client-side-rendering-5d07ff2cefe8

ser, ssr initial load is always slower by magnitudes