I think the issue the user above tried to point out but couldn't is that how to decide which checks should be done everytime for every car. Considering DQs due to plank wear are ridiculously rare(I don't think there was a single DQ in the turbo hybrid era due to greater than allowed plank wear before this one. Feel free to correct me I am wrong), it's reasonable for the FIA to not have that as critical element which is required to inspected for every car. Maybe they could select tracks where this could be an issue (like cota, spa, Baku) and only on those weekends either check all the cars or atleast the lead car from each team for plank wear transgressions.
Edit : Regarding your idea for a plank with different colours at different thicknesses, it may be technically feasible but such a manufactured plank will be far more expensive than the current wooden plank(considering 23 races and 20 cars then it's 460 planks a year so costs will add up real fast). I don't think the FIA will spend money on a policing an issue that occurs so rarely. Maybe the new increased driver fines can be used for this purpose
There is also an availability problem. Only select few AMD GPUs support ROCm. There are ways to get it for unsupported GPUs but I don't use ROCm so I don't have much idea of how that works. You will have to ask somebody else about that. My point is if your need for CUDA is sure and solid, but an nvidia GPU. Also do check out if solidworks can be made to run on linux because it may not work using wine and there is no native version.
What I don't like about the immutable approach is that it turns my PC into a dumb terminal locked by the distro Devs and updated at their will.
I think you are misunderstanding how immutable distros work. They can be just as configurable as regular distros and in the case of nixOS it is more configurable than popular distros. The point of immutability is to ensure that the system can't be broken during when it is running by a bad update or install or by user making configuration errors as these are applied during reboot. If the system is broken then a earlier snapshot is booted so you always have a working system. You can setup a regular distro with this atomicity and snapshots but it is not as easy as using immutable distros. Yes tinkering and using native packages is harder in most immutable distros but immutables never were a catch all solution. Use what suits you. I was just a little upset that you claimed that immutables are not in the spirit of FOSS. You can even make your own images(base OS) in distros like fedora silverblue and update your system with those images instead of using what the maintainers provide. It is what uBlue uses
I am guessing FIA mandates that no work be done on the car if it had been selected for random tests. How will you ensure it is the same plank if it is delievered well after the car has been disassembled
I am assuming you currently use linux. Do you currently use CUDA with freecad and solidworks(which I am assuming you use through WINE or a VM). AMD generally has better raw performance at same price but has nothing equivalent to CUDA at this point. There is ROCm and plans for CUDA through ROCm but GPU support for ROCm is hit or miss. You also have openCL but performance is nowhere near as good as using CUDA even if the GPU using CUDA is weaker. AMD. will provide a much better gaming and day to day usage experience though
Yes you can do all this with regular distros but not as conveniently. Especially cleanly switching from gnome to kde and vice versa is a nightmare. And by switching I mean removing one completely(including dependencies) and installing the other.
Tinkering on silverblue is similar to tinkering on fedora (at least in my experience) just more restrictive in that the read only parts can't be changed(obviously) and tinkering with packages requires reboots and layering. The good thing is you can rollback to easily undo shit.
Yeah man I don't know. I used to think I like tinkering(used endeavour for a few months) but I am enjoying the no maintaince life with uBlue very much. Most of the time the system updates on its own and I am not even aware that the system updated. Same with flatpaks which also auto update so they are always on the latest version provided by flathub when I use them. But I also like gnome so maybe I am not the tinker lover I thought I was
Plenty of things in F1 are random checks. Weighing the cars during quali is random. The randomness is enough of a deterrent that teams do not run cars below the minimum weight. But things like plank wear should be checked for all because the teams cannot accurately know how much the plank is worn especially on sprint weekends.
This. Ferrari and merc were far closer to RB and McLaren this week and could be because both RB and McLaren compramised setup to raise the car a wee bit
The disqualification itself is not a problem. Both Ferrari and merc were hitting the floor pretty hard on the back straight and this was always an issue.
The problem is only few cars being checked. All of them should be checked especially if it is found that there are some breaches. Atleast one car from each team should be tested
Why say something that could be false. He is not trying to say checo will be in the seat in 2024 no matter what. He is just saying this(championship finishing postition) will not be the deciding factor for checo's future
Check if you can upload images using other clients or the official instance website. Maybe your instance temporarily blocked photo uploads to counter spam
Some of them wouldn't. I can't see Alonso refusing this. Guy loves racing and thinks he is the best. No reason he would refuse