advice: no one knows what's best for you more than you
don't hesitate
back yourself
trust your gut
go after what you really want
regret hits harder than failure
Moving from Ruby to Elixir is more than a syntax change. It is a new way of thinking about software.
From object oriented patterns to functional design, and from managing concurrency to having it built in, the shift can transform how systems are built and scaled.
Read one developer’s journey:
https://t.co/3DDRWmRKV0
Finally, @Tan_Stack Start now supports React Server Components!
Start's RSCs are a truly fetchable, cacheable and composable primitive that work with your favorite tools instead of dictating your entire architecture.
Oh, and one more thing... "Composite Components" 😉
🔗⬇️🧵
every skeleton screen you've ever hand-coded is a waste of time
you're literally measuring padding and guessing widths to build a worse version of a layout that already exists in your DOM
so I made a package that just reads the real one
@aidenybai here goes nothing..
on the otherside of the world, there are so many people in the world want death to come to them sooner, cause of suffering they endured they have nothing to do with.
how's that fair if this life is the only life there is..
it is but a dream.
Big news: Popcorn 0.2 is out! 🍿
Popcorn lets you run @elixirlang in the browser – and with this release, it finally has a proper npm package.
Read @JakubGonet blogpost and learn how shipping Elixir, JS, and WebAssembly as one npm package turned into quite the journey 🧵
I've built a new JavaScript runtime that runs inside the BEAM.
Every JS runtime is a GenServer with its own OS thread. No JSON anywhere — JS objects map to BEAM terms natively through a lock-free queue.
What makes it different from running Node/Deno/Bun alongside Elixir:
→ JS runtimes live in supervision trees. They crash, restart, recover state — standard OTP
→ fetch() goes through :httpc. WebSocket through :gun. crypto.subtle through :crypto. BroadcastChannel through :pg — works across a cluster
→ The DOM is lexbor (C library). JS renders into it, Elixir reads it directly — no serialization, no re-parsing
→ Workers are BEAM processes. They get preemptive scheduling for free
→ TypeScript toolchain (OXC) and npm client built in — no Node.js on the machine at all
Full control over the JS layer: parse ASTs, bundle imports, transform TypeScript, minify — all from Elixir via OXC NIFs.
Use cases:
— SSR with Preact/React into native DOM, Elixir reads the tree
— Sandboxed user-defined business rules with memory limits, timeouts, and a controlled API surface
— Parallel Workers that compute and broadcast via distributed process groups
— Evaluating or bundling TypeScript without any external toolchain
— Running npm packages inside the BEAM
Still a research project in early beta. Covered with tests including Web Platform Tests ports, but expect rough edges.
https://t.co/OCB2aoombd
We are hiring 5 systems engineers to build the future of JavaScript
Strong background in Zig, C++, C or Rust required. We are in-office 5 days/week in San Francisco
Email [email protected] with some background about yourself and why you want to join Bun
LiveVue v0.6.0 is here! 🎉
This is by far the biggest update since the initial release, months in the making 🫡
🚀 Out-of-the-box JSON Patch diffs reduce WebSocket payloads by 90%+
📚 Complete docs overhaul
🌟 Client-side utilities
A short thread 🧵
#myelixirstatus