https://github.com/bash-lsp/bash-language-server
- pretty much all editors support LSP these days
Scottish loon sometimes in Caithness, usually in Edinburgh. Likes rugby, F1, reading, cooking, and irn bru
https://github.com/bash-lsp/bash-language-server
It’s unusual for the author to write a headline fyi - and I do agree, full of great facts
Clickbait headline quality article
It’s 6th ed. But not calling it that. And all your 5e is now under-powered
Nah, it’s far more
Surely the absence of nine indicates our model of gravity is off. Combined with lack of Dark Matter, is Einstein wrong?
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
It’ll be a cold day in hell before I give up my ~/.vimrc
Yup. Combined with phosphene it’s looking more and more likely. But still faaar from proven
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.
Archer returns!
Oh a couple. Were much more common in previous editions.
First one I played, a swarm of bats comes out a cupboard I iust opened in a haunted house module. I’m playing the wizard who could burning hands and save us all in an instant. But we’d been plagued by a few illusions, and so I attempt disbelieve it instead. Two rounds later: we’re all dead and the party blames me.
First one I ran: smaller party of three in Dark Sun. Just a few halflings to try and nick their stuff, this one should be easy right? Halfings use poison on Athas. Paralysed one, critted the other, last one frantically trying to unparalyze the other party member, and so I basically have to as a DM or this isn’t Dark Sun; I swarm him and tie him up. They then proceed to roast him alive, and eat him. Lesson learned: don’t mess with anything on Athas, lost more than a few parties on that planet
So good to have trek back!
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
Pandas. Python’s only killer library imo