Going to second other comments. Even without archinstall. It feels like it will be harder than it is. Umm, just save yourself a bit of time and configure the network and install a console editor (nano/vim whatever) while in the chroot (if going full manual). It was a minor pain to work around that for me.

There are pages discussing how to do everything (helps to have a laptop with browser, or a phone to look them up). At the end, you generally know exactly what you installed (OK no-one watches all the dependencies), and I've found any borks that happen easy to fix because I know what I installed.

I remember those times too. The difference today is that there are so many more libraries and projects use those libraries a lot more often.

So using configure and make means that the user also has the responsibility of ensuring all those libraries are up to date. Which again if we're talking about not using binary install, each also need a regular configure/make process too. It's not that unusual for large packages to have dependencies on 100+ libraries. At which point building and maintaining the build for all of them yourself becomes untenable really. However I think gentoo exists to automate a lot of this while still building from source.

I understand why binaries with references to other binary packages for prerequisites are used. I also understand where the limits of this are and why the AppImage/Flatpak/snaps exist. I just don't particularly like the latter as a concept. But accept there's times you might need them.

The current thing I'm working on (processor for iptv m3u files) isn't public yet, it's still in the very early stages. Some of the "learning to fly" rust projects I've done so far are here though:

https://git.nerfed.net/r00ty/bingo_rust (it's a multi-threaded bingo game simulator, that I made because of the stand-up maths video on the subject).
https://git.nerfed.net/r00ty/spectrum_screen (this is a port of part of a general CPU emulation project I did in C#, it emulates the ZX spectrum screen, you can load in the 6912 byte screens and it will show it in a 2x scaled window).

I think both of these are rather using Arc<RwLock<Thing>> because they both operate in a threaded environment. Bingo is wholly multi-threaded and the spectrum screen is meant to be used by a CPU emulator running in another thread. So not quite the same thing. But you can probably see a lot of jamming the wrong shape in the wrong hole in both of those.

The current project isn't multi-threaded. So it has a lot of the Rc/Rc<RefCell> action instead.

EDIT: Just to give the reason for Rc<RefCell> in the current project. I'm reading in a M3U file and I'm going to be referencing it against an Excel file. So in the structure for the m3u file, I have two BtreeMaps, one for order by channel number and one by name. Each containing references to the same Channel object.

Likewise the same channel objects are stored in the structure for the Excel file that is read in (searched for in the m3u file structure).

BTreeMaps used because in different scenarios the contents will be output in either name order or channel order. So just better to put them in, in that order in the first place.

"I think, the people of this country have had of experts" - Michael Gove, (during UK brexit campaign)

The problem with rust, I always find is that when you're from the previous coding generation like myself. Where I grew up on 8 bit machines with basic and assembly language that you could actually use moving into OO languages.. I find that with rust, I'm always trying to shove a round block in a square hole.

When I look at other projects done originally in rust, I think they're using a different design paradigm.

Not to say, what I make doesn't work and isn't still fast and mostly efficient (mostly...). But one example is, because I'm used to working with references and shoving them in different storage. Everything ends up surrounded by Rc<xxx> or Rc<RefCell<xxx>> and accessed with blah.as_ptr().borrow().x etc.

Nothing wrong with that, but the code (to me at least) feels messy in comparison to say C# which is where I do most of my day job work these days. But since I see often that things are done very different in rust projects I see online, I feel like to really get on with the language I need a design paradigm shift somewhere.

I do still persist with rust because I think it's way more portable than other languages. By that I mean it will make executable files for linux and windows with the same code that really only needs the standard libraries installed on the machine. So when I think of writing a project I want to work on multi platforms, I'm generally looking at rust first these days.

I just realised this is programmerhumor. Sorry, not a very funny comment. Unless you're a rust developer and laughing at my plight of trying to make rust work for me.

I looked at that. Actually I would argue that was even more negligence by the management there. I mean they couldn't even say how long he'd not been working for.

But in reality he was paid for at least 6 years of work (and they suspected more) and only fined for 1 year of pay. So, he's still a winner I think. And yes, public funds likely did help in bringing that case forward.

Most larger private businesses tend to avoid going to a court for such things unless they need to in my experience.

Would have been funnier if you just replied "Groundhog Day (1993)" again.

You can make fun of managers not doing work. You know what's worse than someone at manager/director level that doesn't do any work? One that insists on doing so! Trust me, first hand experience.

I don't know if they have much of a case to sue you, if you fall through the cracks on their own negligence. Fire you, yes. Sue, I am doubtful most larger businesses would even try. They'd rather solve the problem and sweep it under the carpet in my experience. Not USA experience of course, but still the attitude would be similar I expect.

I would worry a bit about whether they're allowed to give negative references though. Because if so, it might not be so easy to get another job after.

Best move would be to line up another job to start like a month before the review, and never reach the review stage. Even if discovered, most people that would "know" wouldn't really be driven to report anything if they're leaving anyway. The "not my problem, and this will make it my problem" attitude in big companies is real.

Yes, but it seems the French language pack is a dependency for pretty much everything else! Who knew?

I've been using thinkpads as a work laptop since they were branded IBM Thinkpad. So, I have nothing further to comment.

I think it goes further than that. There's two things happening with regard to AI and software development.

1: Stack overflow has become less common as a resource to solve problems. This, as you say has a problem of input into LLMs for future problems to solve.
2: Junior developers are being hired less because of AI. I assume the idea is that seniors will use AI in the same way they would usually use juniors. Except, they've done what business always does. Not think one bit about the future. Today's senior developers are yesterdays junior developers.

The combination of AI performance drop due to point 1, and the lack of new developers because of point 2 makes for potentially, a bad future for the profession.