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.
My feelings on the subject is that they don't live nearly long enough to not give them a simple pleasure like sleeping with their people.
Even when he wakes me up at 4am because his paws must be licked for 20 minutes.
Or when he wakes me up at 5am whining to get under the covers.
Or when he sleeps like this, which is all the time:
My feelings on the subject is that they don't live nearly long enough to not give them a simple pleasure like sleeping with their people.
Even when he wakes me up at 4am because his paws must be licked for 20 minutes.
Or when he wakes me up at 5am whining to get under the covers.
Or when he sleeps like this, which is all the time:
Future incidents probably will still happen
It's not a question of if, but when. The only secure computer is one that's a mile underground, encased in concrete, and with no network connection.
And even then, it's still not a 100% safe bet.
So I'm not the only one who fried a monitor trying to get X11 working...
and how hard it was to get x11 working
Oh good God. If you really want to test someone's resolve, sit them down at an old computer with a CRT and no Internet and have them configure X11 from scratch. Seeing that default X11 crosshatch background for the first time was practically orgasmic after the bullshit I went through to make it work.
That's one of those traumatizing experiences I'd completely blocked from my memory until I read your comment.
Traumatizing experience #2 that just came back to me was getting a winmodem working and connected to my ISP via minicom.
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.
Just added it to the massive Google graveyard next to Stadia, wave, hangouts, plus, music, etc etc
I am shocked and appalled that Google Reader didn't get called out in this list and is relegated to the "etc" category.
It deserves more than "etc."
Gotcha. I'm actually in the process of moving away from Namecheap because of an experience I just had with them. I tried to register a domain about a month ago (the domain my Lemmy instance is on) and it stopped the registration process immediately after I hit the Pay/Checkout/whatever button and told me to contact their support team to register it.
The error message said it was because the domain name was too similar to something that already existed, and that the support team would have to decide whether I'd be allowed to register it or not. So I went to another registrar and registered it with no issue. I really didn't like that, and it's enough to make them lose me as a decade+ long customer. I already use Route53 for DNS for all my domains, so it's not like I was using them for anything else other than a registrar, so untangling that shouldn't be too much of a pain.
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 don't think it became easier at all until it was forked off into Xorg and they started making dramatic improvements.
It certainly was until I discovered the monitor I hadn't fried had the modelines printed on a sticker on the back...