You shouldn’t be scared of something that doesn’t exist.

That gave me the idea to toss in a coconut or two into bags this year. I’ll reserve those for the “kids” that are obviously too old for this stuff.

It’s a markup language(ish) but it’s not a programming language. XML would be closer to programming, IMHO, since you could have simple things like recursion. That example is even pushing what I would consider “programming”, but anyone can feel free to disagree.

SQL is in the same category for me. It’s a query language and can get super complex, perform some basic logic, but you can’t exactly write “snake” in it. Sure, you could use cmdshell or something else to do something more complex, but that would no longer be SQL.

My simplistic expectation of an actual programming language would be that you can automate an entire platform at the OS level (or lower) instead of automating functions contained within a service or application. (JVMs and other languages that are “containerized” are weird outliers, by my definition.)

I am not trying to step on anyone’s toes here. I just never have really thought about what I personally consider a programming language to be.

Ok, I admit I don’t understand the humor. My immediate response was, “sounds about right because of how these things happen”.(I can be kinda dumb like that sometimes.)

Security advisories may not be immediately announced until a patch is available. If this is in regards to FreeBSD-SA-24:08.openssh, a patch was available the day before it was announced and then refined for prod over the next few days : https://www.freebsd.org/security/advisories/FreeBSD-SA-24:08.openssh.asc

The timing of this stuff is always wonky and it doesn’t look like it hit a could of news places until today, about a week after: https://cyberpress.org/vulnerability-in-openssh-freebsd/

11. Thou shalt not lay with OPs mother.

All the star trek. This is not negotiable.

Bi men, for men.

That is SOC2. In this context, it’s Security Operations Center.

It’s one of the better EDR (Endpoint Detection and Response) tools on the market. For enterprises, they are able to suck down tons of system activities and provide alerting for security teams.

For detection, when I say “tons of data”, I mean it. Any background logs related to network activity, filesystem activity, command line info, service info, service actions and much more for every endpoint in an organization.

The response component can block execution of apps or completely isolate an endpoint if it is compromised, only allowing access by security staff.

Because Crowdstrike can (kind of) handle that much data and still be able to run rule checks while also providing SOC services makes them a common choice for enterprises.

The problem is that EDR tools need to run at the kernel level (or at a very high permission level) to be able to read that type data and also block it. This increases the risk of catastrophic problems if specific drivers are blocked by another kind of anti-malware service.

When you look at how EDR tools function, there is little difference between them and well written malware.

Crowdstrike became a choice recently for many companies that got fucked over by Broadcom buying VMWare. VMWare owned another tool, Carbon Black, which became subject to the fuckery of Broadcom so more companies scrambled to Crowdstrike recently.

I hope that was enough of a summary.

I don’t get it. The key still gets declared, but it’s value is null. “name” in an empty object would return undefined, not null, correct?

(Yes, this joke whooshed, but I am curious now.)

Yeah, I got several replacement bits from them for no charge. It’s also super easy to get past their level 1 support if you present an issue clearly and with evidence. (… as opposed to being forced to perform every step in a level 1 playbook. (DiD yOu tUrN iT oN aNd oFf agAiN?))

I have been following the power loss recovery issues on GitHub for a while. They finally came out and said, on GitHub, that they can’t implement. It was super shady of them to just quietly delete that feature from their product page.

However: If your first layer is tuned correctly and you lose power long enough for the bed to cool down, the print (depending on the material) will likely pop off the bed anyway so power loss recovery is moot. IMHO, if the print is super important it should be supervised and attached to a beefy UPS.

Random rambling and opinions ahead.

It’s $10k if anyone was wondering but as far as commercial products go, that is still peanuts.

Prusa acquired the companies responsible for this product a couple years ago(?) and I believe it is a good thing that this product was in limbo for a bit. (It likely means a more refined product, but just speculation.)

Unfortunately, Prusa is not beyond beta testing with their customers or making false promises about future product features. (re: Prusa Mini, as a good example.) I only say this because if you were planning to buy this for production immediately, I would personally wait a few months.

That previous paragraph sounds bad, and it is, but their support channels are amazing and that is where most of the product cost is. My personal experience with Prusa support has always been excellent.

(I was a Mini early adopter, so I expected some rough edges. Power loss recovery functionality was quietly buried over the last couple of years as their original board+psu wasn’t up to the task.)

This guy was the real killer. The new RMcD is just the cover story.

Yeah, I would think memory as well due to the screen artifacts in that low res mode. (That depends on how x86 memory is mapped these days, I suppose.)

Your post on Reddit reads like an advertisement™️ and karma requirements have been on subs for years. It’s to limit bots with zero karma that typically post spam advertisments. This is a moderator controlled function, usually.

Don’t misunderstand me. I’ll hate on Reddit any day of the week but my complaints need to be educated.

Sorry, my points were mixed unintentionally.

I agree, I stay away from JVMs because they are a pain in the ass to administer and like you said, are usually coded by the lowest bidder.

In a well maintained environment, I have nothing against JVMs actually.

I was just bitching about the spring framework family. While security updates are frequent, Java apps tend to not age well and commonly suffer from version lock-in. (I am going through a round of that at my current job with spring auth stuffs being the offender.)

Huh. Didn’t know that was in a movie.

That is a small town though. If you like corn, oil and wild hogs you would be a good fit down there.

Pshh. They just steal all of their ideas from the CEO of Bitcoin.

I can agree with that. There isn’t anything wrong with diversity as long as the entire ecosystem benefits from it. There are pros and cons, but not really worth going into that here.

At the end of the day, this is the fediverse. If someone wants to write instance code in COBOL to run on a toaster, you go right ahead! (It doesn’t mean I am going to support that effort, but my own personal opinion is insignificant in the whole scheme of things.)

https://sublinks.org/

My reaction on this is: Whatever.

I have heard strange things about Lemmy development in general, so it makes sense that something else would pop up eventually. Java though? I avoid JVMs like the plague and the security track record for spring* is spotty at best.

Still, if some people prefer it that way, whatever.