I think I will use vim-classic and possibly contribute to it. Not because of AI, but because I actually want to use Vim over say something like Neovim* and I actually like vimscript, which imo didn't need the development of vim9script to improve it.
Regarding why not Neovim, I think it's because a large section of the community want to create more complex TUI elements or replicate GUI interfaces and make it more like VS Code. I use Vim for the "vim way" not because it's in a terminal or it's not bloated like some other editors.
I see this contradiction all the time. Windows is a mess but there are lots of examples of rock solid, performant applications that have been developed and maintained over decades. Everything is one, also one that springs to mind which is much more performant compared to Linux alternatives is WinMerge.
If I install Ubuntu 25.10, I can't get camera effects (blurred background and so on) to work in Meet because hardware compositing (or something, I'm not entirely clear on the details[0][1]) doesn't work properly on the open Nvidia driver on Wayland. Wait I thought this was all supposed to be the future?
Ratpoison was always my favourite tiling window manager. There's also a fork called sdorfehs[0] which seems to still be maintained and has a bunch of minor improvements here and there.
Slightly off-topic, but a little while back someone shared an article with a screenshot of a lot of famous developers desktops including Kernighan, Ritchie, Pike, Rasmus Lerdorf and a load of others (they are just the ones that come to mind). One of things I remember was the use of Windows for some historical Unix person and also one of them liking non-monospaced fonts. Can anyone find this link? Thanks in advance!
Fails to mention my favourite text editor, Sublime Text which has an optional Vim mode built in (Vintage). I personally am using NeoVintageous[0] which allows you to run various ex commands and shell commands, as well as incorporating features from popular plugins such as vim-surround.
I distinctly remember walking around the area where Notre Dame is in Paris and hearing a faint sound I recognised on the breeze. The closer I got the more it gave me chills. The sound of the organ presumably (I'd like to think) being played by Olivier Latry and of course I recognised the sound from his recordings of Messiaen[0]. Not Messiaen that day but those compositions being played by Latry on that organ... that sound.. it just takes me somewhere else.
Probably submitting this too early because it's not really polished, but thought I'd just raise it because it feels like there is some potential in the REPL space for even quicker experiments by integrating AI.
I have a 3770 Ivy Bridge (a refurb'd HP Elite 8300 with SSD upgrade and 32GM RAM). Genuinely for the work I've done with it, C/C++, Rust, JS and Python, which I'd consider that heavy dev work, media consumption on a 2K monitor, with a Nvidia GT1030, some 3D gaming (on low-medium setting) it's competitive with my work MacBook Pro M1 (although that only has 8GB RAM).
This seems pretty outrageous but reading their website they state:
eufy records and stores videos locally when motion is detected by your device. If you subscribe to our cloud storage service, your videos are securely stored in the cloud and can be deleted at any time. Your videos will be permanently deleted from our servers according to the storage period on your plan.
so it sounds like it's working as intended with their privacy guarantees to do with your data stored in the cloud and ensuring it's only accessible by you
Although the part about identifying faces does sound pretty Orwellian
Definitely up there with one of the greatest scenes for sure. As the article states the impact of the scene is only magnified by real world events at the time, but it's also timeless. I've always loved Casablanca and this is without doubt my favourite scene, it gives me goosebumps.
Very nice! I'm a fan of OpenBSD and pledge(). I've had some success on Linux with libseccomp[0] which means you don't have to deal with BPF directly, but pledge() is obviously much much easier.
I was exploring the actual implementation[0] of a capabilities feature in Nodejs and was utilising seccomp (via libseccomp) on Linux at least to achieve a greater degree of security than might otherwise be possible by remaining in userland code. The idea is that you'd write your code, import whatever you like and define your capabilities upfront at initialisation. The problem is there's quite a big disconnect between what you are doing in JavaScript and what's happening with system calls in v8, libuv and the other native parts that it's difficult to predict what you need to block and what's actually going to happen. So I don't think my approach is really viable in a general sense, although capabilities in general I think would improve the situation if the wider community were to adopt the approach.