Joined December 2008
213 Photos and videos
Pinned Tweet
Small update to this story: Oliver has paused OmniWM and plans to return with Hiro, a Rust rewrite. I’ll be happy to test it when it lands. Meanwhile, I’ve been working on Nehir — a focused Niri-only fork with several stability fixes already landed. v0.4.0 is the first signed & notarized build, now available via my Homebrew tap: github.com/Guria/nehir/relea… github.com/Guria/nehir/discu… brew tap guria/tap brew install --cask nehir Feedback and bug reports are very welcome.
May 29
Great project with huge potential just got archived. github.com/BarutSRB/OmniWM/i… I was one of its biggest supporters. I sponsored the author, actively tested new builds, and shared a lot of feedback because I genuinely wanted this project to succeed. Unfortunately, supporting countless edge cases and user requests can be exhausting, and it seems the burden eventually became too much. Oliver, if you ever read this, please know that I'm grateful for all the time and effort you invested in this project and for sharing it with the world. Let's see if the OSS community can carry the torch forward. Regardless of what happens next, OmniWM made a lasting impact.
1
65
Jun 13
Just paid @AnthropicAI $120 to see this
11
May 29
Great project with huge potential just got archived. github.com/BarutSRB/OmniWM/i… I was one of its biggest supporters. I sponsored the author, actively tested new builds, and shared a lot of feedback because I genuinely wanted this project to succeed. Unfortunately, supporting countless edge cases and user requests can be exhausting, and it seems the burden eventually became too much. Oliver, if you ever read this, please know that I'm grateful for all the time and effort you invested in this project and for sharing it with the world. Let's see if the OSS community can carry the torch forward. Regardless of what happens next, OmniWM made a lasting impact.

I am in love with #OmniWM. Finally I can organise my work, pet projects, vibe coding, messengers and terminals. Still there is a lot of room for improvements but I found it usable already for my use cases.
1
167
GuriaFS retweeted
May 13
Extremely interesting test collection. I was happy to adopt @ReatomJS for it.
Replying to @johnsoncodehk
Also built reactive-framework-test-suite — 180 test cases for reactive signal semantics across 13 libraries. PRs welcome to add more frameworks or test cases. github.com/johnsoncodehk/rea…
2
3
13
1,547
May 13
Someone please vibecode vim motions Duolingo like app
23
I am in love with #OmniWM. Finally I can organise my work, pet projects, vibe coding, messengers and terminals. Still there is a lot of room for improvements but I found it usable already for my use cases.
110
GuriaFS retweeted
Incredible growth! Huge thanks to all our users!
1
8
233
Mar 12
I've just observed GPT‑5.4 running inside Copilot tried to read the ~/.codex files. That suggests some agentic behavior is baked directly into the model’s knowledge base. I just wonder where that could lead us. What subtle behaviors become uncontrollable by tweaking the harness?
33
me: @github how much of analytics is enough? @github: yes
1
58
Feb 22
Here is what am I talking about. 7 tool calls instead of 1, just because model assumed code is indented with spaces.
Feb 21
Do LLMs actually have trouble with tabs instead of spaces in code, or is that a myth? Any benchmark results?
1
72
Feb 28
I really hope @AnthropicAI will be able to notice and fix the issue that causes extra token burning in tab-indented codebases.
12
Feb 21
Do LLMs actually have trouble with tabs instead of spaces in code, or is that a myth? Any benchmark results?
108
GuriaFS retweeted
built a small CLI tool that moves your AI coding session context between Claude Code, Gemini, Copilot, Codex and OpenCode when you hit rate limits. no more re-explaining what you were doing, or painful copy/paste from terminal that lose tool-call context. just `npx continues`
132
200
2,529
213,428
Feb 18
That rare moment when the AI tells you "The bug isn't in your code, the bundler broke the library's NPM artifact by transpiling async/await into too many .then() chains" ... and you assume it's hallucinating. But then you check the stack trace, and it’s actually 100% right. 🤖🎯
Feb 18
Found a super unpredictable bug in Babel's async/await transform recently 😱 Transform itself comes from 10-year-old archive code (github.com/babel/kneden?tab=…). So, first things first: I STRONGLY RECOMMEND NOT transpiling async/await at all! There is no reason for that now! 1/4
1
1
57