BREAKING NEWS: Girl gets home safely after night out. More at 11.

but I do think a sizeable portion of existing C++ devs who don’t want to use rust exist

That may be true. But out of that pool of people it seemed that very very few wanted to work on the fish project. So it was not helping them much at all. The is a vastly larger pool of people that don't want to learn C++ and some of those may be willing to pick up rust. It would not take much for that to out number the number of C++ devs that want to work on fish that also don't want to learn rust. Given there are not a huge amount of contributors that regularly contribute to it according to their announcement blog post.

You don't actually require a separate partition - you just need to not reformat the current one when reinstalling. Most distros I have seen will delete system folders if you don't format but will always leave the home folder intact. Manually deleting the system folders is also an option if the installer does not.

TBH I am not sure a separate partition actually buys you anything but false confidence (which we do sometimes need ;) ). During the partitioning phase you can easily delete or format the wrong one (hell, if you only have one then it is less error prone to skip it all together). And after that step the drives are mounted and there is nothing protecting your files from the installer deleting them. It is just installers don't touch the home folder or anything other then the system ones if it is on one partition or 50 different ones - it just sees the files in the directory it wants to install to. The only way a separate partition would add protection is if it were mounted after the install - which I do not know of any installer that actually does that.

As with anything. ALWAYS backup the data you care about before installing a new OS. The separate partition does NOT protect your data from deletion in any way. Leaving your home folder is simply a convenience option so you don't need to restore all your files after the installation - not a replacement for a backup.

Coloured text does not require a dep. It is just about printing the right colour codes like:

const BLACK: &'static str = "\u{001b}[30m";
const RED: &'static str = "\u{001b}[31m";
const GREEN: &'static str = "\u{001b}[32m";
const YELLOW: &'static str = "\u{001b}[33m";
const BLUE: &'static str = "\u{001b}[34m";
const MAGENTA: &'static str = "\u{001b}[35m";
const CYAN: &'static str = "\u{001b}[36m";
const WHITE: &'static str = "\u{001b}[37m";
const CLEAR: &'static str = "\u{001b}[0m";

fn main() {
    println!("{RED}red! {BLUE}blue!{CLEAR}");
}

The libraries just make it easier so you don't need to remember or know what those codes mean.

Which validates the authors point - it can be hard to find or get a job writing rust. Much more so than other languages. Even if there technically are jobs around, just knowing rust wont help that much in obtaining one.

What standards? The old init systems were a loose collection of shell scripts that were wildly different on every distro. Other tools like sudo also broke the established standards of the time, before it you had to login as root with the root password.

Even gnome and KDE have their own themeing standards as well as other ways of doing things. Even network manager is its own standard not following things that came before it. Then there are flatpack, snaps and app images. Not to mention deb vs rpm vs pacman vs nix package formats. Loads of things in Linux userland have broken or evolved the standards of oldern times.

IMO it is a double edged sword. One the one hand a doctor that uses AI to notify them of something they might not have thought of and the doctor confirms what the AI says before treatment can be a big benefit. But on the flip side people leaning to much on it and not verifying the output at all and taking what it says at face value like it cannot be wrong will lead to some very bad situations.

I can see most people wanting to pull towards the former, but cost cutting, overworking employees and trying to maximise profits will pull things towards the latter. And ATM I don't know which force is stronger - we really need to get the profit motives out of our healthcare systems.

How much human invention has to actually be there?

This is still up for debate, from the case in question:

Undoubtedly, we are approaching new frontiers in copyright as artists put AI in their toolbox to be used in the generation of new visual and other artistic works. The increased attenuation of human creativity from the actual generation of the final work will prompt challenging questions regarding how much human input is necessary to qualify the user of an AI system as an “author” of a generated work, the scope of the protection obtained over the resultant image, how to assess the originality of AI-generated works where the systems may have been trained on unknown pre-existing works, how copyright might best be used to incentivize creative works involving AI, and more.

Or a better idea: don't use goto. In any language. Especially not one that needs line numbers to work and not labels, as soon as someone edits the file utter chaos will ensue. This has all the normal downsides of gotos with labels, but with far more downsides.

https://docs.docker.com/engine/reference/commandline/init/

Looks like a feature that can be used to generate Docker files based on source code in a repo/directory. Looks like they added detection support for rust server applications so it can now generate a Dockerfile that can be used to build rust server applications.

This is a poor article. It makes no sense. It does not describe what white box testing really is.

It is different from the black box testing as the white box testing is not used to find missing functionality of a software

Like what the hell is that even meant to mean?

None of the advantages or disadvantages make any sense or related to whitebox testing at all. It is just words that are related to testing throwing around in hopes they mean something. Do not bother reading, it is not worth the effort to click on that link.

You do not want to use floats for any part of calculating money. The larger the value the larger the error in them - not a trait you want when dealing with money. Fixed point numbers/decimals/big ints are much better for this, if you want greater than cent precision, treat the values as fractions of a cent (aka move the arbitrary decimal over one more place or however many you need for your application). The maths is the same no matter where you place the decimal point in it.