I can only speak of on Linux. If you know the disk is bad, clone it, with ddrescue, and fix the clone. But in future RAID and backup remotely. Also, next gen filesystems like ZFS and Btrfs for check sums and self healing and subvolumes with send/receive deltas between them.

I’m glad that had a happy ending and sorry that happen. Autolock is so dangerous.

You can pay to have less ad, but you’re still also paying with your data. Bet pretty soon it will be pay and have ads, or pay more again. They have a captive market. They can extract and extract.

I feel bad buying things DRM’ed, so I very rarely do, and not for myself. I don’t want to fund that. Feels much better funding DRM free work.

You can of course write drivers for them, but then it’s you own abstraction not the standard Linux abstraction. (You can hack something up with IIO for that stuff, but it’s not pretty). There is CUSE (part of FUSE) you can do some character devices with.

Existing drivers in Python are messy to use if you our not developer in Python.

The nice thing about in kernel is:

• it’s done for you already
• the interface is standard and will work with anything that uses that class of device
• it’s langauge agnostic.

The Linux kernel does hardware abstraction. It’s not a microkernel. There is limited support for proper userspace drivers.

If you doing some application specific app, that will only work with those chips, use do it in userspace. But to make a normal system for normal use, you want things in kernel like normal.

Only a fraction of it is RTCs. What is in the Pi overlays folder is from everything. Not even all the DT I2C RTCs. There is loads of ADCs, DACs, IO extenders, all sorts.

It’s really annoying you can’t do DT on x86 Linux. It’s a bit of a gap in the platform. It would make Linux ARM based developer’s lives easier.

GPIOs are the easy bit. You can get those no issue on x86. It’s I2C and SPI that are the issue with x86. You can get the buses sure, but all the device drivers are Device Tree based. You can’t just throw in Device Tree overlays on x86.

Regulations can work. Latest is EU’s USB-C phone/laptop/tablet standardization. It’s great! No more crazy range of different laptop power supplies.

Some stuff is pretty much as I want already. Henry vacuum cleaners for example. Tough as nails and easy to get parts and help for. Framework laptop and fair phone aim to be good for repair and upgradablity.

France repairablity index can be rolled out further field.

Things used to be more repairable and last longer. We can reverse the trend down. No need to despair.

I think the EU will be first to role it out at and scale. Like USB-C device power standardization.

Seriously, no one is going to mention “Right To Repair”? If this was law, and companies had to divulge how there stuff worked and was assembled, as well as sell parts, things would last longer. If every trade zone had a repairablity index, competition would make things last longer still.

I’m not giving you what I regard as my instances because I think that is combative. I don’t want combat, that’s the whole thing. I’m not really pro or anti this defederation, but I can see the problem and I’m interested in how it plays out. In it becomes a place of combat rather than debate, I’m simply leave. If there is no news or anyone to talk to, I will also leave.

If there is coordinated defederation, maybe it’ll give mods of the troll infested instances pause for thought, and make them clean house. Or not, and Lemmy bumbles along without ever hitting mainstream, until something else comes along. Maybe central instances set the tone of the whole thing, and here this is a mortal wound.

It’s an interesting “natural experiment”.

See that’s not my experience of the problem. They aren’t being polite. They are out right hostile. Staying calm, providing trusted source references, and remaining polite, just seams to enrage they further. They seam to want to have a slagging match, which is of no interest to me as I’m not 12.

So ‘Tankies’ are the ones fighting Nazis? There doesn’t seam much between the two to be honest.

It’s not really communism. It’s all about freedom to compete. The bazaar is a market after all.

Note: Reference to The Cathedral and the Bazaar. Worth at least knowing of in regard to open source history.

I’m watching with interest what happens here. I left Reddit before for Voat for a while. It turned out that without policing (or maybe it was the type of policing) it turned into a toxic cesspit.

Policing of some kind is clearly import to human groups. In the real world, across the world and history, where is no law and order, you end up with war lords and drug lords, who setup their own rules. Take moderation away and online groups get consumed by trolls.

So I’m watching what happens with federated Lemmy with interest.

If Lemmy turns into a toxic cesspit, like Voat did, anyone remotely normal will leave to avoid the toxicity.

You mean a fork? Why not? A copyright assignment and relicensing dispute is what caused a LibreOffice to fork from OpenOffice. Forks is a great feature of FOSS and there are normal.

Best recent example I bumped into was OrcaSlicer it’s a fork of a fork of a fork, merging in some of a fourth fork.

I don’t think there is a way that always works.

It’s not always possible to get a clear spec and do big design up front in R&D. The whole point can be to work out what can be done and how.

Rewrites are great. You have a specification that is so defined it is literally code.

When it’s blue sky, it’s harder. Plans will be wrong. The users don’t understand really what they need or want. It all ends up evolving. Anything with a GUI is worse because users/customers need (want) things moved about, re-themed, with no regard to what’s below. Best to nail them to mock up designs they signed off on. Same with API interfaces. If they signed off on the design, you can then point out “spec change” and get more time/money. It’s more about ass covering than using the outcome or process.

Exactly!

I worked at one Agile place they had all their sprints and milestones in a Gantt Chart waterfall. They also did big design up front and a lot of process. They had do all kind agile and scrum training, but it was the most process heavy place I worked.