🚀 happy to announce the release of @featurevisor v2.0!. ✨ this release packs a punch with several performance optimizations, improved reactivity supporting realtime updates, covering both frontend and backend use cases. 👇

working with Ruby language is making me realize how much it helped influence the node.js ecosystem in early days.

you just cannot one-shot porting SDKs to other languages using AI. not yet, anyways.

Amsterdam is sunny today ☀️

The real AI effect.

kudos to @RedwoodJS team. getting attention from developers is not easy.

.@golang is. opinionated.

over time, I feel both are true regarding writing documentation. it’s:. - a thankless job.- rewarding to get the chance to introduce users to what you build, like a storyteller.

various ways to understand seniority, if you can code:. - for yourself .- for others.- with others . code itself can be less relevant here.

thank you 🫡

creativity of the Flash era of web is arguably still unmatched.

also feel free to add your apps here in showcase page 🙌 .

If you are one of the few people using @featurevisor, would love to know your use cases 👋

same set of SDK APIs across JavaScript, Java, PHP, and now @golang if you have feature flags management needs in your Go apps, give it a try 🙌.

✨Go SDK is here for @featurevisor for serving your feature flags management needs in backend. 👇

full API docs available here @colinhacks.

I like this new API from Zod v4

Wishfully thinking context pricing would go down over time like storage disks did.

Still prefer the idea of having an IDE to be able to review diffs across multiple files with ease.

The challenge is real.

context usage goes up very fast in @cursor_ai if you ask it to work with JSON Schema spec. not a very easy spec in its defence.