Distinguished intern at @lovable . accidentally created Rio terminal. prev: @charmcli @spotify @godaddy
Stockholm
- Tweets 13,213
- Following 286
- Followers 6,334
- Likes 14,408
Pinned Tweet
Today I'm announcing Canario, a new terminal for macOS.
It uses Rio under the hood 🐤
Spaces with their own colors (⌘1–9), splits, a ⌘K command bar, live tab previews, session restore, and a floating quick terminal on ⌥⌘T.
macOS only for now, Linux and Windows are coming.
31
27
336
145,352
I might need to remove intern from my profile.
the amount of people that reaches me out for an internship at lovable 😂
it was a good ride with the title though
5
38
1,184
A better visualization of the demo btw
This is a quick superficial demo of OJ store mode.
It makes oj keep compiled output in a shared, per-user, content-addressed store instead of a per-checkout cache: every entry is keyed by worktree-independent identity, so any other git worktree, CI job, or sandbox of the same project can look up the same key and restore the build instead of recompiling.
In this video is exactly what you will see: one worktree compiled once and wrote 1,762 entries, and the other 19 booted off that 132MB store with zero recompiles and zero store writes.
More info on the matter soon.
5
892
This is a quick superficial demo of OJ store mode.
It makes oj keep compiled output in a shared, per-user, content-addressed store instead of a per-checkout cache: every entry is keyed by worktree-independent identity, so any other git worktree, CI job, or sandbox of the same project can look up the same key and restore the build instead of recompiling.
In this video is exactly what you will see: one worktree compiled once and wrote 1,762 entries, and the other 19 booted off that 132MB store with zero recompiles and zero store writes.
More info on the matter soon.
3
5
34
2,024
Very cool, thanks @BetterStackHQ for the video!
I am removing fbm out of OJ, it will be a different/new architecture. More about it soon.
The tanstack bug should be gone btw.
So cool! @BetterStackHQ did an awesome explainer video about OJ by @raphamorims
OJ is a Rust rewrite of the Vite dev server that we're using at Lovable to massively improve performance and memory usage.
1
15
683
I saw yesterday the issue @sapphi_red has posted in OJ repository, asking to update the benchmark since it was misleading. In fact I did a mistake in the bench and I acknowledge it.
I updated the bench to the new OJ version towards to Vite 8.2.1.
@evanyou @sapphi_red please lemme know anything, if I did a mistake again I am super OK in acknowledge and fix it.
Re-run with the corrections applied (M-series Mac, vite 8.2.1, whole process trees, all sizes measured in one session, OJ at the 0.2.8 candidate).
So the honest gap is roughly 3x at 1k growing to 6x at 10k: smaller than the README claimed, and the README now says so.
18
718
People are asking me about OJ bundled mode.
OJ today has similar performance in the unbundled mode to Vite bundled. So today OJ isn’t necessarily faster, it just consumes less memory.
I don’t want to follow bundled mode architecture for different reasons, so started to sketch something different that is designed for agentic era.
I will share more about when time is due.
1
2
11
545
Raphael Amorim retweeted
At @Lovable, @raphamorims rewrote Vite in Rust and I am seeing the performance numbers at scale as it's rolled out. What a beast, can't wait to share more!
lovable.dev/blog/faster-prev…
1
1
19
987
I deleted most of my social media last year, and have been back to back on deleting Twitter (delete, activate, delete, activate, loop).
@caarlos0 and some folks advocated to me why just exist on Twitter is a good thing.
Since then, I decided to stay and Rio multiplied by 11x times number of users, big companies started to use rio-vt or/and librio, etc.
A lot of times you can build great stuff, but no one knows about it. You need to make sure that other people know about it (unfortunately it's the type of work I am the least interested but I am learning).
7
2
52
2,011
Raphael Amorim retweeted
Acabei de migrar o DCC de Vite para OJ + Tauri 🚀
Benchmark local:
Vite: 1,29s na primeira subida
OJ: 0,77s na primeira subida
Com cache aquecido, ambos ficaram praticamente empatados.
O mais importante: o OJ já está funcionando no fluxo de desenvolvimento e build, com desktop, mobile e testes validados.
✅ 895 testes passando
✅ Vite removido do fluxo de build/dev
✅ Tauri funcionando normalmente
Não é uma promessa de “10x mais rápido”; é uma migração de pipeline com desempenho equivalente e uma base mais alinhada ao OJ. 🚀
OJ 0.2.0 is out! 🍊
JavaScript workloads now run in-process on @deno_land isolates, no more JS sidecars (yey)
On one internal app:
• 6 to 2 processes
• 4.1 to 1.5 GB
• memory stays flat across HMR edits.
less machinery and lower overhead
1
1
3
587
No, the sandbox isn't dead, we just migrated from Vite to OJ 🦀
This was an internal sandbox broadly and heavy used in @Lovable.
Fun fact: 09/15 was my first attempt to migrate it to OJ 😂
More details about OJ migration soon.
OJ 0.2.0 is out! 🍊
JavaScript workloads now run in-process on @deno_land isolates, no more JS sidecars (yey)
On one internal app:
• 6 to 2 processes
• 4.1 to 1.5 GB
• memory stays flat across HMR edits.
less machinery and lower overhead
3
1
56
5,915
OJ 0.2.0 is out! 🍊
JavaScript workloads now run in-process on @deno_land isolates, no more JS sidecars (yey)
On one internal app:
• 6 to 2 processes
• 4.1 to 1.5 GB
• memory stays flat across HMR edits.
less machinery and lower overhead
8
3
63
8,890
