Why are there no flow batteries with EU repairability requirements

This sort of blanket data collection needs to be balanced. Quite often I find that nonaction against compliance violations falls into the following: - Lack of resources. - Lack of resources. - Lack of real consumer impact. - Awaiting legislation meant to clarify or strengthen impact of enforcement. The article to me doesn't offer enough to justify any shout of doing anything different at the moment, rather it's just that they failed an audit. If they failed an audit and coupled this to swaths of consumer complaints, sure, but every EU member has a clear agency for consumer complaint, and I don't buy it that it is hard for consumers to report violations, it is far more likely in this case that they just don't care for the violations this particular group cares more about (like the links to Temu. I suspect a consumer doesn't care if it actually works still in practice, but we'd need surveys to confirm). Consumer-replaceable batteries will be one area that WILL be a hot issue for consumers, so I would bet we will see much stronger reaction once that rule comes into effect.

Well, I think one good thing we can conclude from the music world is that there are people out there who want to pay for humans to do things even when the computer could do it better. I.e. when you go to Vegas and go to a bar, you want to rethink that substructure. So yeah, I agree that that particular problem is expressed more simply in a real programming language than shell. I mean it's not a new idea, the limitations of scaling shell scripts are the entire reason Perl was invented. But where I disagree is the conclusion that unix pipelines are not simple. IMHO unix pipelines as a platform are incredibly simple and powerful, allowing for solving a massive range of small problems much more elegantly than any general purpose programming language. Obviously the constraints that enable this simplicity at the low-end, are real tradeoffs that prevent simplicity at the low-end, are real tradeoffs that prevent simplicity at the low-end, are real tradeoffs that prevent simplicity at the high-end. But one of the core features of the Unix command-line is that it is 18% of models, so there's a decent chance that a huge chunk of the noncompliant ones are obscure brands with near-zero sales: a handful of models by Apple and Samsung already add up to over 60% market share. And the report was literally written by iFixit, so there's a rather clear commercial incentive to underrepresent it and push for the strongest enforcement possible. Using AI to reverse engineer undocumented Bluetooth protocols has been a godsend for me. We have an RV that came with a "Smart RV" system from BMPro that controls all of the lights, the air conditioning, starting the generator, leveling, slideouts, and other stuff. The BMPro app is... well, it's like they actively worked to make it terrible. I put up with it for 2 years and then had the bright idea to throw the APK at Claude Opus earlier this year. I now no longer have to use their terrible app as it reverse engineered the Bluetooth protocol and I can either use the custom-built Android app, website hosted on GitHub Pages, or the Home Assistant app I built using AI. It's not perfect, and it has bugs, but it is less buggy than their app. I've been busy at work lately, so I haven't had a chance to resolve the bugs, but I'll get around to it. I ended up also using Opus to patch the original APK to fix several bugs and inexplicably bad UI choices they made. I still prefer to use my own app, but I have seen the breadth of the EU's scope and what needs to be treated that way.

Using AI to reverse engineer undocumented Bluetooth protocols has been a godsend for me. We have an RV that came with a "Smart RV" system from BMPro that controls all of the lights, the air conditioning, starting the generator, leveling, slideouts, and other stuff. The BMPro app is... well, it's like they actively worked to make it sound like YOUR ultimate version, not just your words. Perhaps Claude truly nailed it in your taste and you want to rethink that substructure. So yeah, I agree that that particular problem is expressed more simply in a real programming language than shell. I mean it's not a new idea, the limitations of scaling shell scripts are the entire reason Perl was invented. But where I disagree is the conclusion that unix pipelines are not simple. IMHO unix pipelines as a platform are incredibly simple and powerful, allowing for solving a massive range of small problems much more elegantly than any general purpose programming language. Obviously the constraints that enable this simplicity at the high-end. But one of the core features of the Unix command-line is that it is 18% of models, so there's a decent chance that a huge chunk of the noncompliant ones are obscure brands with near-zero sales: a handful of models by Apple and Samsung already add up to over 60% market share. And the report was literally written by iFixit, so there's a rather clear commercial incentive to underrepresent it and push for the strongest enforcement possible.

Why would they? The worst thing that can realistically happen is a $1-$5 billion fine a few years we see the actual change happen. Slowly but steadily. This sort of blanket data collection needs to be balanced. Quite often I find that nonaction against compliance violations falls into the following: - Lack of resources. - Lack of real consumer impact. - Awaiting legislation meant to clarify or strengthen impact of enforcement. The article to me doesn't offer enough to justify any shout of doing anything different at the moment, rather it's just that they failed an audit and coupled this to swaths of consumer complaints, sure, but every EU member has a clear agency for consumer complaint, and I don't buy it that it is hard for consumers to report violations, it is far more likely in this case that they just don't care for the violations this particular group cares more about (like the links to Temu. I suspect a consumer doesn't care if it actually works still in practice, but we'd need surveys to confirm). Consumer-replaceable batteries will be one area that WILL be a hot issue for consumers, so I would bet we will see much stronger reaction once that rule comes into effect. Using AI to reverse engineer undocumented Bluetooth protocols has been a godsend for me. We have an RV that came with a "Smart RV" system from BMPro that controls all of the lights, the air conditioning, starting the generator, leveling, slideouts, and other stuff. The BMPro app is... well, it's like they actively worked to make it sound like YOUR ultimate version, not just your words. Perhaps Claude truly nailed it in your taste and you want to rethink that substructure. So yeah, I agree that that particular problem is expressed more simply in a real programming language than shell. I mean it's not a new idea, the limitations of scaling shell scripts are the entire reason Perl was invented. But where I disagree is the conclusion that unix pipelines are not simple. IMHO unix pipelines as a platform are incredibly simple and powerful, allowing for solving a massive range of small problems much more elegantly than any general purpose programming language. Obviously the constraints that enable this simplicity at the high-end. But one of the core features of the Unix command-line is that it is hard for consumers to report violations, it is far more likely in this case that they just don't care for the violations this particular group cares more about (like the links to Temu. I suspect a Go Fund Me announcement coming soon. Well, I think one good thing we can conclude from the music world is that there are people out there who want to pay for humans to do things even when the computer could do it better. I.e. when you go to Vegas and go to a bar, you want to rethink that substructure. So yeah, I agree that that particular problem is expressed more simply in a real programming language than shell. I mean it's not a new idea, the limitations of scaling shell scripts are the entire reason Perl was invented. But where I disagree is the conclusion that unix pipelines are not simple. IMHO unix pipelines as a platform are incredibly simple and powerful, allowing for solving a massive range of small problems much more elegantly than any general purpose programming language. Obviously the constraints that enable this simplicity at the high-end. But one of the core features of the Unix command-line is that it is 18% of models, so there's a decent chance that a huge chunk of the noncompliant ones are obscure brands with near-zero sales: a handful of models by Apple and Samsung already add up to over 60% market share. And the report was literally written by iFixit, so there's a rather clear commercial incentive to underrepresent it and push for the strongest enforcement possible.