https://github.com/bash-lsp/bash-language-server

• pretty much all editors support LSP these days

WhoBird

AntennaPod for podcast travels

When does systemd stop? Linux without it is increasingly looking unlikely in the future. Are we not worried about it being a single point of failure and attack vector?

This isn’t a moan about the unix philosophy btw, but a genuine curiosity about how we split responsibilities in todays linux environment.

Me. Outlook on my windows work box is hard to beat imo. Personal? All android’s default and web-ui

Got tickets for them next month!

It’ll be a cold day in hell before I give up my ~/.vimrc

why do you recommend other tools over things which are tested and will last way longer than whatever the current fad is? The best part of Jenkins is it’s ubiquitousness - writing code that will run forever is not to be sniffed at

You know what’s a hard pill to swallow for Jenkins haters? It’s likely older than your career, and is going to outlive you too. Like bash, and C, and gnu-utils.

Want to appear godlike in any org? Learn a tiny amount of groovy and read the pipelines pages - https://www.jenkins.io/doc/book/pipeline/

Jenkins is battle tested, Jenkins is likely already in your org, and replacing it for anything else is almost not worth the time from a strategic perspective. But it isn’t perfect, testing it in particular - a pain in the ass

So here’s the best tip: skinny Jenkinsfiles. When you use a sh: have it run a Makefile command, or your build tool command. Keep them short single line things. Don’t rely on massive ENVs. Dockerfiles for most stuff. Dynamic container agents in the cloud are actually good. Learn to use archiveArtifact, integrate with test report plugins. Learn about parallel pipelines.

Can you license a comment in lemmy?

I wouldn’t touch ES with a barge pole. They wrote their own gravestone imo. Check out the quality of the docs today between the two, and the SQL support. commits != quality or features

ElasticSearch tried this and lost hard already. OpenSearch has already out paced it in features and performance and ES is effectively dead. Such a braindead exercise to see Redis follow suit

The boring answer: the boring shit pays the bills. If you want to apply your programming chops to science then academia is your home

UBI often touted as an answer to this kind of thing though, breaking capitalism through removing cheap labour will have untold societal shifts, including an uptick in creative thought and independent research. Beware though: most research today costs way more than you think to generate meaningful breakthroughs

Seems fine with anarchy to me

So Konsole rocks. Yakuake a great addition. But I’m a big KDE fanboy

Alacritty is also pretty fun, combined with openbox / LXDE

But for the $dayjob it’s Windows Terminal which is easily the best thing Microsoft has released in decades when combined with WSL

It’s more advice than a complaint. I run on one setup. Linux terminals. And neovim has to beat that for me to switch

For me vim is one of those things that just works. It’s ever present, reliable, and dependable. The simplicity of it mirrors the unix way and my usage of it is so closely wrapped in screen, /tmux, bash, gnu-coreutils, and a few terminals over the years that any change is going to have me asking ‘why?’ essentially. So a command line flag allows familiarity of existing tooling to really sing, and I suspect offers far more compatibility than the suggested fix too given the length of the windows addendum to the guide

And totally agreed about out in, I use Arch btw. And I’m not in a hurry to switch to nvim either, I tried and switched back pretty quickly. Pathogen is still an amazing plugin system, leveraging my git and bash knowledge to boot

Excellent, TIL. It should be bash scripts though. Setting strange write modes and obfusticating paths, combined with a set and a let (now having to go learn the difference) isn’t something I would recommend to anyone.

Add alias vim=nvim --vimrc-compatibility to your ~/.bashrc would be my prefered migration path

It broke vim compatibility with this one change. That is super easy to support for painless migration. A real no brainer imo. The docs don’t explain your easy fix either. The key to making change faster: make it easier for people

It fucks about with locations too much for my liking

Nope. Still on regular myself. Pry my .vimrc and .vim/plugins folder from my cold dead fingers