Too bad there’s no single „this is what this project is” anywhere in the repo description, readme or docs. There’s „X is next generation of Y”, and even the whitepaper goes straight into weeds instead of explaining what the thing is. I tried hard but I still don’t fully understand.
„Built on Windows”. That’s like anti-ad these days. Maybe, maybe worth looking at if you can run other OS than Windows on it, but that will probably take some time.
Similar story here. Before vim I used Kate, Gedit, Eclipse, JEdit and NetBeans IDE. Got into vim in 2009 and since then it's the editor I always come back to.
Neovim really gave it a new life - LSPs, Treesitter, scripting with Lua (which I suck at) and many more. Over last 15 years I had shorter and longer periods where I tried/used something else (VS Code, Emacs/Spacemacs, helix) but it's always been vim/neovim. I don't really enjoy vim config maintenance though, but it doesn't happen too often to look elsewhere.
Giving evil-helix a try is on my editors-to-try-when-i-have-mental-capacity-for-switch list :)
I've been in such situations so many times and it never crossed my mind to actually prepare something generic that could fit many of those situations. This is neat idea. I don't think I'd just copy-paste-send though, I'd likely do small tweaks to adapt it to the current case, which would turn it from 3 sec to more like 60 sec, which could still be a win. Will try!
As the author of asciinema I'm flattered that Rodrigo considers asciinema as a potentially useful tool for this problem.
This solution would likely apply to a small subset of contributors, unless most Dillo hackers are terminal editor users, and would probably help only partially (which he acknowledges in the post). I guess partially is still better than not at all. Setting aside the technical aspect, I wonder how practical it would be to review long asciinema sessions when reviewing a patch.
If you're reading this Rodrigo: is your recording verification idea to just quickly eyeball / skim through a recording to catch human behavior in those sessions? Or maybe something more elaborate?
Btw, I'm not taking sides here, just happy to see asciinema in the wild :)
This is a good news. I moved my domains from DNSimple to Infomaniak last year, as part of my rely-less-on-US-infra-and-services strategy. I chose them for their dedication to privacy, ethics and transparency. This change reassures me this was a good choice.
For those who are/were considering Infomaniak and are wondering about the quality of service: I use it for DNS only. Their UI is less than ideal but not bad once you get used to it. The service is solid, never had any issues.
Is it just me or this article has been written or at least heavily processed with LLM? My AI slop radar triggered immediately (overly verbose, fluff, bland). Don’t get me wrong, it has valuable information but that style smells LLM from a distance.
Same here. More than 5 years with fish and it’s been like 5 times when not-POSIX was an “issue”, which I’ve been solving by temporarily entering bash and rerunning the command there.
How do you know “it has no memory leaks, crashes, ANRs, no performance problems, no network latency bugs or anything” if you built it just yesterday? Isn’t it a bit too early for claims like this? I get it’s easy to bring ideas to life but aren’t we overly optimistic?
Here's a copy of my Mastodon post [1] from Oct 2025:
---
I had a job interview yesterday, which happened via Google Meet.
Even though I use my desktop Linux workstation and Firefox 99% of the time for everything, my first instinct was to do this interview on a MacBook and Chrome, to avoid surprises and not look unprofessional if something doesn't work, which has happened in the past. Last year, when I was asked to share the screen during a daily, I had to say "um, I'm sorry, Zoom and desktop sharing don't work on my system."
But I thought I'd first do a test on my workstation, just to see if maybe I shouldn't be concerned anymore. I was sceptical.
The ideal scenario was that on my standard GNOME 48 / Wayland / PipeWire desktop I'd be able to use Firefox for this call, and AirPods, a Logitech webcam, and desktop sharing (5K ultrawide scaled at 125%) would just work with no tweaks whatsoever.
And it did!
I've been using Linux on the desktop for over 20 years (on and off, but mostly on) and I know how to hold my Linux systems, but the situation with Bluetooth audio and desktop sharing in previous years has been... spotty. I was less worried about AirPods — I switched to PipeWire ~3 years ago and so I know Linux audio has been rock-solid and pretty much solved already. But desktop sharing used to be hit-or-miss, highly dependent on whether you used X11 or Wayland, further complicated by the use of Flatpaks.
Since my test went well, I did the interview on the desktop machine. It went smoothly, with no surprises.
Therefore, I announce 2025 as the Year of the Linux desktop :)