Publishing to Maven Central is now available via Central Portal (actually, it has been here for a long time). No more registering using Jira ticket, now it looks more mature with sane Web UI, new API, webhooks, ability to confirm your namespace and more. Web UI and API allow you to upload your bundles manually if your build system doesn’t support it yet. Not so many tools support this at the moment, but the number is growing. For example, Gradle, Maven, sbt, mill are already among these.

Right now one of my working stations is an average laptop which is not performant so much to run some heavy graphical applications (i.e. some competitive games where fps/latency matters). I have a dual boot with Linux and Windows and while Linux works smoothly, Windows is not. In case if you have good hardware, Windows runs pretty good out-of-box without any tweaking, but if you don’t, it is good thing to tune it manually by disabling redundant services, uninstalling bloatware, drivers, tuning network and so on. Actually, it is nice to do even with top-hardware to achieve maximum performance.

I don’t know why I haven’t used it yet but it is possible to make vim’s yy (and similar commands) works with system clipboard and across different vim instances:

" enable copying from vim to the system-clipboard
set clipboard=unnamedplus

My common workflow with tmux is using several per-project windows and navigating between them. Each “project” is usually a git-repo and I do all the things just inside this repo. Until recently I had to manually name each window to not fall into the mess of unnamed windows.

Sometimes you need to quit editor with error code. It happens not so often and the most notable situation is when you need to somehow abort git-committing at “write your message” stage. Here you can manually kill your editor’s instance or, in case of using vim, enter :cq (link). Finally I don’t have to kill my vim instance manually.