Let me guess, UltraAV whitelabels Kaspersky…

It’s like the PHB. You don’t need to read it cover to cover but there’s a couple of chapters you’ll want to read entirely up front and then it’s just a resource with suggestions on how to adjudicate various scenarios.

Which I always find kind of hilarious since it’s basically expressed on the first page of the DMG.

Not entirely. Yes there was blight affecting crops but there was more to it than that.

Huge volumes of unaffected produce were exported to England for profit - the decreased yields only impacting the market for locals. Previous famines has seen the British ban exports to ensure the local population had access to food (which also decreased the prices) but not this time around.

English landlords of Irish property were evicting their tenants who weren’t able to pay (since the blight impacted many people’s ability to work) with zero notice or rights for the tenants. Absentee landlords were extracting huge amounts of capital out of the Irish economy, owning vast swathes of the entire country.

The Irish were widely dependent on the potato as a primary form of sustenance but it was due to the potato being high in calories, cheap and easy to grow, and high density yields from relatively small plots of land (landlords dividing up the land into incredibly small divisions whilst simultaneously extracting the highest rent possible for the land).

The Irish were, in essence, forced to eat potatoes due to the extreme economic exploitation they were subject to.

Yet there was no aid from England; she simply sat by reaping profit and leaving things up to the divine - “the market will provide”. There had been efforts to change tariffs and laws but the contention in the governing party about providing aid caused the Prime Minister to resign and the subsequent government threw out all efforts (except those such as offering relief to those without land which forced many Irish to sell what land they had to gain relief and aid).

A Prime Minister at the time launched a commission to investigate and it was found that the absentee landlord system was abhorrent and principally responsible for the famine.

Sadly 1/4 of the population perished, and another 1/4 simply left the country. In some ways, Ireland never recovered.

Not to excuse the developer but I empathise with why they might have felt compelled to change the license.

One of the biggest pains for any open source project is distributions and packagers who package the software themselves yet make changes or configure in non-standard ways which leads to major overheads for upstream as everyone submits bug reports for bugs introduced down stream and have nothing to do with them.

I feel we, as a community, need to be more vocal about when a project has been modified from the original source for packaging or distribution (where those changes weren’t pushed upstream) to demand the project be renamed in that instance.

I feel for these small developers who do this in their spare time and find the community forcing more work on them and damaging their reputation without any fault of the developer but someone downstream who doesn’t care not want to support what they’ve packaged.

Perhaps there are other solutions? Before other projects decide to use awful licenses and infringe on rights just to try and tackle the problems created by downstream.

Nonsense. If they were perfect, wouldn’t they have used a question mark? Your judgement of character is laughable. What empirical evidence is there that they are perfect?

(How was that?)

Give it to meee

I’m not insisting anything; stating C is not a memory-safe language isn’t a subjective opinion.

Note I’m not even a Rust fan; I still prefer C because it’s what I know. But the kernel isn’t written by a bunch of Lewis Hamiltons; so many patches are from one-time contributors and the kernel continues to get inundated with memory safety bugs that no amount of infrastructure, testing, code review, etc is catching. Linux is written by monkeys with a few Hamiltons doing their best to review everything before merging.

Linus has talked about this repeatedly over the past few years at numerous conferences and there’s a reason he’s integrating Rust drivers and subsystems (and not asking them to fork as you are suggesting) to stop the kernel stagnating and to begin to address the issues like one-off patches that aren’t maintained by their original author and to start squashing the volume of memory corruption bugs that are causing 2/3rds of the kernel’s vulnerabilities.

No idea what you’re being downvoted. Just take a look at all the critical CVSS scored vulnerabilities in the Linux kernel over the past decade. They’re all overwhelmingly due to pitfalls of the C language - they’re rarely architectural issues but instead because some extra fluff wasn’t added to double check the size of an int or a struct etc resulting in memory corruption. Use after frees, out of bounds reads, etc.

These are pretty much wiped out entirely by Rust and caught at compile time (or at runtime with a panic).

The cognitive load of writing safe C, and the volume of extra code it requires, is the problem of C.

You can write safe C, if you know what you’re doing (but as shown by the volume of vulns, even the world’s best C programmers still make slip ups).

Rust forces safe® code without any of the cognitive load of C and without having to go out of your way to learn it and religiously implement it.

And 50ml of neurodivergence or, if you’re out, 50L of involuntary celibacy.

A typical greentext recipe is to dissolve it in 100ml of lies.

This slogan was from the 90s (1993/94 maybe?).

Slack and Teams have emoticons for reactions which serve the same purpose.

Internal forums are older than Slack. What’s so novel about Nintendo’s approach?

Estimates put it around 13 million sales on Steam alone. Say another 5 million from console sales combined to a guesstimate around 18 million.

deleted by creator

Ship a new app then. Sonos already do this for older products.

Whoever the fuck thought a massive regression for every single customer was the perfect thing to deploy with no option for rollback needs to stop working in software.

Conway’s Law applies in this respect; the mess in governance of Nix has produced a product that reflects that mess. Nix started a beautiful movement but like many first movers, they rarely reap long-term rewards.

If you release in early access, perhaps expect players not being ready to jump into a buggy, in-development competitive shooter?

Only early access games I’ll pick up are ones where it’s not PvP and I doubt I’m alone in that.

Bizarre they’re effectively treating the game as “released” and studying telemetry yet when players see “early access”, they see it as “beta” and not actually released.