This is why I got all of our devs to start building with the target of a Docker container in mind.

And for the ones who still won’t or can’t wrap their brains around Docker, I run their shit through a Github Actions workflow that spits out their ugly baby as a Docker container. In the end, I don’t give a shit what it is, your Rube-Goldberg piece of shit is getting stuffed into a Docker container.

“It works on my machine!” Yeah, well, your machine is now everyone’s machine thanks to the magic of containers. Now fix your broken shit so PagerDuty doesn’t call me at 3am again. Fuck.

Never going to happen, same for Excel.

Whatever future iteration of ChatGPT that eventually enslaves the human race will be using Outlook and Excel to keep track of the genocide.

I’ve been doing -fr like forever. Don’t know why

BURN THE HERETIC

Even now, the only thing that Javascript has going for it is that it’s not Groovy…

I hate Node and NPM so much that I have a physical reaction to just seeing the words now.

I already disliked Node & NPM quite a bit, but the hatred and disgust got to the point it is now after having to write a CI/CD pipeline in Groovy/Jenkins for a Node site that that our devs were building. I had to automate the build/deployment of Satan’s favorite framework in Satan’s favorite language. I came pretty close to quitting.

It’s out the door now, but I’m in the middle of reimplementing the pipeline in Github Actions so I don’t drink myself to death when they come knocking to do it again.

I’ve been using Linux professionally for a couple of decades and using it altogether since like 1996. I never knew about the timeout command. I’m gonna have some fun with that.

I wonder if I can set someone’s shell to it…

More like <esc><esc><esc><esc><esc><esc><esc><esc>… Just in case

MY PEOPLE!

VSCode is what made me finally switch away from vim for anything but minor edits. It’s just too good.

I did set up vim keybindings in it, though.

I first settled on vim as a teenager because I was a fan of… performing surprise penetration tests.

It defaults to opening files read-only, so you don’t have to worry about the access/modified time on the file changing if you open one for… science reasons.

Man, this comment made me feel a little embarrassed at myself. I saw the shortcuts and thought about how I have a tradition of going to the top of the file when I’m done editing and about to save/quit. I always hit the shortcut for it and think “gg boys! Good game” and then quit out of vim.

Stop judging me.

Quick editing for me is in vim. Anything else is in Visual Studio Code. Which I have set up with vim keybindings.

Yep. I’m not making a proclamation, just stating an opinion. I don’t have a problem with what they’re doing, and if other people do, that’s fine. Some people like their cucumbers pickled, let them have their pickle.

I actually wouldn’t be surprised to see it go open source in the future, Microsoft has been doing that a lot recently, like VScode and the whole of .NET and friends like PowerShell. Pretty much the only things worthwhile from Microsoft are already open source, except Copilot.

Copilot was trained on copylefted code while itself being closed. What was brought to attention by @ralC@lemmy.fmhy.ml isn’t efficacy, but Microsoft’s lack of ethics and social responsibility when it comes to their bottom line.

I honestly don’t have a problem with that. Everything that it was trained on is publicly-available/open-source code, and I’m not aware of any license that requires you to distribute your modifications if you don’t make modified binaries publicly available, not even GPL. And even then, you’re only required to make available the code that was modified, not related code. And I don’t even think that situation would apply in this case, since nothing was modified, it was just ingested as training data. Copilot read a book, it didn’t steal a book from the library and sell it with its name pasted over the original author’s.

This isn’t really any different of a situation than a closed-source Android app using openssl or libcurl or whatever. Just because those open-source libraries were employed in the making of the app doesn’t mean that the developer must release the source for that app, and it doesn’t make them a bad person for trying to make money from selling that app. Even Stallman is on board with selling software.

And even if you take all that off the table, you’re free to do the exact same thing and make a competitor. Microsoft didn’t make their own language model, they’re using a commercially-available model developed by OpenAI. There’s literally nothing stopping anyone else from doing this as well and making a competing service called “Programming Pal” and making their code open-source. In fact, it’s already been done with FauxPilot and CodeGeex and the like.

So yeah, I really don’t have a problem with it. This ended up a lot longer than I had originally thought it would, sorry for the novel.

Because we have some contracts that stipulate any data related to the project, including secrets/credentials, must remain on-site, and in some cases, on an air-gapped network. Doesn’t make sense to spin up something else to manage those secrets when Bitwarden can do it all and satisfy the requirements of those contracts.

Aside from the callback chains and API shit, my issues with Node rest almost entirely on the lack of a standard library, because that led to the state of NPM today, which is just an absolute garbage-fire shitshow as far as I’m concerned.

I have my own separate issues with NPM, namely its dependency resolution (my God, just take dnf's dependency resolution algorithm and use it), trivial packages that other packages list as a dependency (is this an int? Is this running on Windows? Better take this one line and make it a package!), and the relative inability to remove a package from a registry (did a secret slip in there while testing? Tough shit!). The worst of that being the trivial packages, I think, because then you can end up with projects that can have a dependency tree 10s of thousands packages long.

And all that bullshit wouldn’t be even 1/16th of the problem it is today if there were a standard library.

You should take what I’m saying with a grain of salt, though, I’m just a DevOps Sysadmin, and aside from running some software that uses Node, most of my experience with it is unfucking it when our devs come to me to fix the tangled monster they’ve created.

I’ve had something similar happen, except the post that I found which fixed the problem was made by… me. Apparently I’d had the problem before, figured it out, and then posted an update about why it was happening and how to fix it.

That was some Twilight Zone shit.

At that point you may as well go full Vagrant or start using Docker images.

And no matter how quirky or obtuse venv/conda/pip can be, they will never be as bad as Node. Ever. Node will hold that King Shit crown forever, or at least to God I hope it does.

Something worse than Node coming around and getting popular might just make me quit IT altogether.

Github Copilot is worth the money. I’ve had it finish out functions for me after just a few lines. There’s usually an error or two, but the consistency with which it can predict what I’m doing or trying to do is pretty impressive.

I pay for it just because it’s cheap and to support them

I did this too when it first came out, and then the product became robust enough that I recommended we implement it at work because secrets management was non-existent. We have a bunch of licenses on the Enterprise plan now and it just keeps getting better each update.

My only complaint is that migrating the data to a new server is a pain in the ass and never works correctly, even when following the migration instructions to the letter. Always have to open a ticket with them for that. Not enough of a pain to move to another product, though.

I also still pay for my personal plan. It really is a fantastic product.

The worst part of ML is Python package management

Do you have some time to talk about our Lord and Savior, venv?