typescript

How to implement type-safe JSON strings and extend `JSON.parse()` and `JSON.stringify()` to automatically infer them. Genius.

How to implement type-safe JSON strings and extend `JSON.parse()` and `JSON.stringify()` to automatically infer them. Genius.

https://youtu.be/z7pDvyVhUnE

/frontend dev・founder/decentralized data wrangler /blockhead・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx, ritual.net・x.com/darryl__yeo

or use https://effect.website/docs/schema/json-schema/

Farcaster Development Boutique @ https://dTech.vision 💜 in love with tech 🤓decentralization, fitness and oldschool rap 😎

farcaster engineering liquidity • prev manifold.xyz, twilio.com

1) I understand, though the benefits outway it for me personally. It's just clean and stable vs wrapping every thing in try {} catch and praying for it not to break with many validation helpers

2) depends on how deep you go into the functional paradigm

1) I understand, though the benefits outway it for me personally. It's just clean and stable vs wrapping every thing in try {} catch and praying for it not to break with many validation helpers

2) depends on how deep you go into the functional paradigm https://effect.website/blog/from-react-to-effect

1. if you use a 3rd party library so close to the native one you're basically forking into a new programming language, a massive dependency, can cut you off from ecosystem, and makes bringing others on hard.

2. Functional programming doesn't scale well. You hit complicated subjects quite quickly and the it very quickly consumes your entire codebase with non native types. All of the sudden before anyone can contribute they have to understand monads, functors, lifting functions, combinators and a lot of advanced subjects.

I experienced this with scalaz in scala world and a bit of guava in java.