If I buy an Android phone, I should be able to maintain/update the operating system.
If I buy a MacBook, I should be able to maintain or change the operating system.
If I buy a TV, smart watch, microwave - I should be able to maintain their software.
The only thing prohibiting this is the fact that drivers are obfuscated and/or hardware schematics sufficient to produce drivers are not provided.
IMO, if the EU wants any technical sovereignty, they'd address this as I don't see European companies producing a competitor to the MacBook - I do however see European companies being capable of creating a competing operating system (or Linux) to install on a MacBook, but only if Apple is compelled to allow them.
The same goes for smartphones, cars, and any digital device
You'd probably also get things like TVs with very basic software at import, with much better software available for people willing to obtain it outside the EU.
The source of this number seems to come from here, on page 73:
https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELE...
Interestingly, the number is over a span of 15 years, and is only the calculated "Growth and investment".
Other numbers are "Savings in production costs" at €15.6 billion, and "Consumer savings" at 25€ per consumer per year for an impressive total of €176.5 billion.
It also lists "Business adjustment costs" at €8.1 billion, "Business administrative costs" at just €69.8 million and "Implementation and enforcement" at €105.5 million.
I wonder why "Growth and investment" was chosed as the number to use. Maybe to keep emphasising their gist of "the EU is the future for sustainable growth"?
Also, here are the announcements by the Commission:
https://commission.europa.eu/news-and-media/news/right-repai...
https://www.consilium.europa.eu/en/policies/right-to-repair-...
What I know off the top of my head, from reading the legislation a while ago. Is that technical reasons, such as waterproof devices, will still be able to retain non user replaceable batteries if it is needed to keep the device waterproof.
Unfortunately regulations often don't go far enough.
I have a ~10 year old iPad Pro in perfect working condition. I can basically do nothing with it, and increasingly it can no longer even browse the internet because Safari is so outdated on it.
So it will be waste.
See similar story about Amazon bricking old Kindles: https://www.techradar.com/tablets/ereaders/amazon-bricking-c...
But, this regulation is still a tiny step in the right direction.
The 10 year old iPad is still a perfectly capable device, but it suffers from the lack of an updated operating system and enough storage to apply a would be update. There are millions of people for whom an iPad is all the computing they'd ever need (many just use their phone as well), but the larger screen makes it a good option of online shopping, banking, emails, government documents, calendar and appointment booking. The price is reasonable, but it doesn't need to replace every three to five years to serve that purpose. Arguably I don't know how Apple would make money on it long term, but the lack of update should count against them in terms of their environmental image.
Apple is far from the worst, their phones updates for a long time, longer than most. Their laptops equally so. The iPad is very disappointing, because even if they issue an OS update, not all the devices can apply it, because of the lack of storage. Still better than my wife's old Samsung phone that was unable to apply any operating system update ever, because the storage was to limited.
Like just a few years ago it became impossible to run 32bit windows which effectively killed all OS software updates for hardware older than ~2005. Most application software followed.
On the Linux they just dropped support for the 486 and older versions of the kernel will likely still get security updates for a while.
The main problem is that people maintaining the OS build for your hardware is the same people making the hardware. If legislation forced to divest both into separate companies the support would last far, far longer.
But I guess there is no money to be made on that software...otherwise we would already see a bunch of non-manufacturer companies offering software for 3rd party devices that are unlocked, wouldn't we?
Or maybe the used hardware is just not documented well enough
<sigh> If only that were true. I have a Samsung S20 with 128gb storage and a adequate battery that is ewaste because of the locked bootloader and now permanently vulnerable kernel.
Not disagreeing with your premise (the same should be done with ISPs — own the connection or the wires, but not both). I'd just take the "hard" install with fewer features over what we have now.
Imagine the cool things people could do with old iPads. Put Android or Ubuntu Touch and give it to people who cannot afford a tablet. Wall display for Home Assistant. Rip out the batteries and have a very low energy ARM server, etc.
If we're talking about a 15-year old device, it definitely feels like requiring (1) a boot loader unlock method & (2) all technical specs required for basic functioning (display, input, compute) aren't overly burdensome on Apple et al.
Essentially mandating a corporate 'methods and specifications' EOL requirement to avoid device obsolescence.
This would also have a side effect of giving the EU a regulatory trade barrier against sketchy fly-by-night Chinese tech (e.g. "DMOAO tablet").
And encouraging tier I tech device manufacturers to offer longer warranties, in their own self-profit-interest.
And they won't let anyone install any other software onto the hardware, so I can't even rely on the free market providing what I want.
Because otherwise you won't buy new device for full price
Eh, what are you proposing? That these new regulations should cover +10 year old devices too?
Similarly I still have an iPhone with a lightning port instead of the legally mandated USB-C port, but at no point was I expecting Apple to somehow change the ports of existing devices.
I'd say that we need regulation requiring user-replacable software. Even though a PC might not be supported by Windows 11, and subsequently major browsers will cease support. You can still install a 3rd-party OS like Linux which will maintain support far beyond the original EoL.
Same goes for Android devices, I used to have an LG G2 (the phone, not the TV), which IIRC shipped with Android 4 or 5, and through LineageOS I updated it all the way to Android 11. Granted it couldn't remain relevant forever, its 32-bit ARM architecture is quite outdated and a lot of apps lost support for it, but for a while it remained quite useful.
So for next decade, older devices might often have more memory!
Might help you get some more use out of it, thanks to the DMA :-)
If limited to the bootloader, such as allowing users to run their own operating system, then that is definitely a possibility, with the exception of firmware running on the device itself. But I doubt that is what most users here are expecting, and in my opinion, it wouldn't provide much value to the vast majority of customers.
Not every business venue needs to be a multi billion multi national and using some devices for a long time is better than burrying them all in a land fill.
> it wouldn't provide much value to the vast majority of customers
I should have phrased it as:
> it wouldn't provide enough value to their customers to create meaningful value for the company.
You can argue that "ha ha, we shall enact regulation to force them to do this!" but the reality is that only a small percentage of customers would actually benefit from such regulation. Because most people are not going to tinker with their devices, especially if there is no easy or straightforward way to do so.
So in the end, you'd have more regulation that makes it harder for new players to enter the market, while doing little to solve actual customer problems and ultimately imposing significant costs on manufacturers.
For people who actually care about long-term device support, they can choose reputable manufacturers that already offer it. If no such manufacturers exist, that may instead represent an opportunity for someone to build a business around providing better long-term support.
It's the large stream of perfectly usable e-waste modern practices emit.
Anything that makes a significant portion of that stream reusable by anyone is a win.
If that's someone buying e-waste, unlocking devices, flashing linux, and then reselling it to whomever then that's still a win.
From my point of view, the proposals suggested here, although difficult to discuss in detail because of how abstract they are, would not solve this issue in any meaningful way. By "meaningful" I mean that the cost-to-benefit or cost-to-regulation ratio would be rather poor.
IMO, the core issue with e-waste isn't necessarily bad practices by manufacturers, but rather consumer behavior. People often throw away 2–3-year-old phones that are still fully supported by the manufacturer. For example, with the exception of the phone I broke, I usually replace my phone every 5–6 years. Within that timeframe, I have the battery replaced by the manufacturer at least once, and the phone continues to work just fine.
This issue extends beyond electronics as well. People often throw away clothes once they "go out of fashion," which these days happens exceptionally quickly. The same applies to furniture, appliances, and other consumer goods that are often replaced simply because newer models are available, rather than because the old ones are no longer functional.
This is ultimately a broader issue of consumer culture and our tendency to replace things rather than repair or continue using them. I don't agree that this is primarily due to a lack of repair options or difficulty accessing repairs. In many cases, the means to repair these products already exist, but consumers simply choose to replace them instead.
This deserves a 'in the first world' caveat. Most waste streams terminate in the not-first world. There's a reason there are so many photos of African and SE Asian markets full of a hodgepodge of mobile device and English-printed t-shirts.
Which is to say, increasing repairability shouldn't just be measured by how likely the first world is to use it, but also to how useful it would be to downstream consumers.
To your list, there is a critical caveat to my caveat though: weight and volume.
Things like appliances (small motor, big bulky box) and furniture (bulky) are exceptions to the above, given their difficulty to efficiency ship en masse.
> I don't agree [consumer tendency to replace over repair] is primarily due to a lack of repair options or difficulty accessing repairs. In many cases, the means to repair these products already exist, but consumers simply choose to replace them instead.
It's a gradient, like all things. Repair has difficulty and cost. Policies (like this one) could be enacted which decrease that difficulty and cost. Are they worth it?
> cost-to-benefit or cost-to-regulation
Which gets to the measuring. My suspicion is that most HN commenters (myself included) are weighing from placing a high value on 'owning your own tools' which may not generalize to the populace.
But even so, I think it's a valid question of whether society would be 'better' if people had more ownership of their devices. Versus the current outsourcing to the mercy of Google / Huawei / Samsung / Vivo / Xioami / Apple.
Cars are a good example of this. Historically, people in Western Europe would sell their used vehicles into what was essentially a second-hand market in Eastern Europe. This worked and continues to work to this day.
While a car is a good example of something whose lifespan can be extended beyond its first user, I don't think the same necessarily applies to mobile phones that are more than seven years old and are no longer supported by the manufacturer. That said, broken phones or phones that are traded in early in their lifespan can definitely find a home in secondary markets.
> Things like appliances (small motor, big bulky box) and furniture (bulky) are exceptions to the above, given their difficulty to efficiency ship en masse.
It's largely a matter of the weight- and volume-to-cost ratio. Otherwise I agree.
> It's a gradient, like all things. Repair has difficulty and cost. Policies (like this one) could be enacted which decrease that difficulty and cost. Are they worth it?
There are already vendors that refurbish phones and resell them today. However, it is not a particularly profitable business, largely due to the high labour costs involved. And I'm not talking about the difficulty of replacing a glued-in battery, but rather the cost and expertise required for component-level repairs on the motherboard, something no regulation is going to magically make disappear.
> But even so, I think it's a valid question of whether society would be 'better' if people had more ownership of their devices. Versus the current outsourcing to the mercy of Google / Huawei / Samsung / Vivo / Xioami / Apple.
It depends on where you draw the line on ownership and what benefits that provides to the end consumer.
There are specific areas where full ownership is explicitly restricted by regulation or other legal requirements, such as radio firmware or secure payment systems like Apple Pay or Google Pay. I don't believe consumers would benefit from increased access to these systems. In fact, I believe the opposite.
There are also cases where manufacturers rely on intellectual property from third-party vendors and simply cannot release or open-source the code without violating a non-disclosure agreement and potentially causing significant financial harm to the vendor. Even if regulation were introduced to allow manufacturers to disregard such agreements, that would not eliminate the underlying problem. It would simply shift the cost onto the third-party vendor, whose intellectual property and business model could be undermined by having its proprietary technology made public.
However, there are also cases where software or hardware becomes unusable for no apparent reason whatsoever. A good example, albeit purely a software one, is what Stop Killing Games is trying to address. I would generally agree with initiatives like that.
They don't have to. Open up the platform for linux and custom OS.
You could make the argument that manufacturers only need to provide the means for the community to support the device, rather than extensive documentation. However, these communities are often so small that this would never be a priority for most companies. Combined with the IP-related issues, I don't think this is really feasible.
Btw, it's difficult to believe the post is a good faith argument.
> it's difficult to believe the post is a good faith argument.
Right back at you, I guess.
I would understand the frustration if manufacturers were not upfront about how long they intend to support their hardware, although that is not always easy to predict. However, demanding that they support hardware indefinitely is unreasonable.
nobody demands that - it's more of the fact the hardware is locked and serialized, e.g. it won't accept a blue tooth module unless it's unlocked with proprietary software.
The hardware manufacturers spend quite the effort, so the devices are not open and require designated tools for minor fixes. I can imagine it not wanting to perform a warranty repair but that's the end of it.
Manufacturers have a regulatory obligation to prevent unauthorized combinations of software and hardware where those combinations could compromise the device's compliance. This is particularly relevant to radio firmware, including Bluetooth, where the manufacturer must ensure that the radio equipment remains compliant with the applicable regulatory requirements.
> The hardware manufacturers spend quite the effort
Because they are required to do so by regulation. Those regulations exist for good reason, for example to prevent unwanted interference in the radio spectrum.
Beyond regulatory requirements, manufacturers also have legitimate reasons for preventing unauthorized tampering with their devices. One concern is theft and device resale, while another is software security.
You may argue that you don't care about these things, which is perfectly fine. Everyone is entitled to their own opinion, and there is nothing inherently wrong with holding it. However, I would argue that this is not what the vast majority of customers expect, and that most would ultimately accept these constraints for the benefits they provide.
It's not. It's something they have to stop doing. Stop adding code that specifically stops third party software from running.
You can just stop to the last reason, they don't want to give up ownership back to you.
They would prefer you to throw the device in the bin and buy a new one, preferably from them again.
No, it's simply that your demand is completely unreasonable. You are essentially asking them to adopt an open-source model. That can mean giving up control over its intellectual property and potentially exposing proprietary technology to competitors, especially when some products are valuable precisely because of the software that runs on them.
Edit:
I don't know why it is not allowing me to reply to you.
> No, I'm asking these devices to work like normal computers
What exactly is a "normal computer," and what specific behavior are you expecting?
Can you freely tinker with your motherboard's firmware? Can you modify the Bluetooth or Wi-Fi firmware on your motherboard? Can you modify and independently update the internals of Windows itself? These are all examples of components that are proprietary and subject to limitations, even on what we would consider a "normal computer."
There may be some exceptions to the above, but the same generally applies to mass-produced, commercially distributed devices. They are often locked down for technical, legal, and security reasons, and "unlocking" them is simply not a reasonable expectation in many cases.
There's a 10 minute timer on HN to avoid discussions becoming too heated (at least AFAIK that's the reason).
> You are essentially asking them to adopt an open-source model. That can mean giving up control over its intellectual property and potentially exposing proprietary technology to competitors, especially when some products are valuable precisely because of the software that runs on them.
...and nothing wrong with that. The right-to-repair is mainly aimed at discontinued products anyway, at that point the "IP" is so old it doesn't require protection (and to be honest, the whole concept of long term "intellectual property" is bullshit anyway, just as long-term "copyright" - about 3 to 5 years is a reasonable time frame for 'exploiting' a novel idea, after that it should be free for all - at that time your competitors will have figured it out anyway).
In the 80s it was entirely normal to get parts lists, schematics and ROM listings when buying a computer for instance (and I guess other electronic devices too), there is absolutely no reason why access to the same information should be restricted today.
What you consider "old" may not be what I, or the manufacturer, consider "old." A lot of embedded development is incremental: you start with an existing codebase and continue building on it to meet new requirements. Occasionally, the entire system is rewritten from scratch, but that is not necessarily the case. Therefore, even software running on a discontinued product may contain code and intellectual property that is still actively used in newer products.
> and to be honest, the whole concept of long term "intellectual property" is bullshit anyway, just as long-term "copyright" - about 3 to 5 years is a reasonable time frame for 'exploiting' a novel idea, after that it should be free for all - at that time your competitors will have figured it out anyway
I believe you are confusing intellectual property and copyright with patents. If that is the case, I would largely agree. I would even go further and argue that many things that are allowed to be patented are ridiculous and not particularly novel at all. Some are so obvious that even a layperson could arrive at the same solution, which arguably should disqualify them from being patented in the first place. This is especially egregious in the standards world, where some companies hold patents on solutions that are intended to be standardized and used globally.
If, however, you are not confusing these terms, then I find your position absolutely ridiculous. It would be akin to asking Microsoft to release the source code for Windows, Office, Teams, Azure (although who wants to see that mess, am I right? lol) simply because "intellectual property" isn't a thing. That would outright destroy countless business models, and I can assure you that no major global or regional regulatory body is going to adopt that position.
> >>there is absolutely no reason why<< access to the same information should be restricted today.
There are plenty of reasons. You simply don't agree with them. That's perfectly fine, but claiming that there is "no reason" for things to work differently from how you want them to is simply ridiculous. Many of them I've mentioned in this post.
Also I doubt that there's anything left on 2015 era hardware that will grant you an edge on current age competitors
To give a reply:
> Can you freely tinker with your motherboard's firmware? Can you modify the Bluetooth or Wi-Fi firmware on your motherboard? Can you modify and independently update the internals of Windows itself? These are all examples of components that are proprietary and subject to limitations, even on what we would consider a "normal computer."
Yes I expect do be able to do all of those things if I want to, it's my computer and I should be free to do whatever I want on it. Including modifying firmware, modifying the OS and modifying anything else you can think of.
Do I want to do all of these? Probably not but the freedom for me to do it should be there if I change my mind. And no, it's a reasonable expectation.
> Yes I expect do be able to do all of those things if I want to
For the components I listed, and based on my understanding of "normal computers" as desktops and laptops, you cannot do all of these things today.
> it's my computer
It's their firmware. They don't magically give up their intellectual property rights when you purchase a piece of hardware from them.
What would be reasonable is providing access to datasheets, schematics, and manuals, where permitted by local laws, so that users can tinker with and develop for the hardware themselves. However, that shouldn't come with the expectation that the hardware's chain of trust remains intact or that all features will continue to function as they do with the OEM software.
And yes, I also support adding laws to force manufacturers to respect my rights.
> However, that shouldn't come with the expectation that the hardware's chain of trust remains intact or that all features will continue to function as they do with the OEM software.
I'm okay with that if the manufacturer doesn't remove features in bad faith (which they almost always do as there's very few legit uses on their side).
Again with the abstract. Provide an example of a manufacturer removing features in "bad faith." It is very likely that what you view as a "bad faith" action actually has a reasonable explanation from the manufacturer's perspective. This is especially true in cases of chain-of-trust and anti-tamper protections.
> I never stated that I own the intellectual property but I'm stating that I own the device and such
Technical specifications, datasheets, and similar materials can also constitute intellectual property of the manufacturer. Without access to these, you may not be able to "do any modification I see fit," especially when phrased so broadly that it could mean almost anything.
The only option I can see being somewhat feasible is for manufacturers to eventually release APIs with closed-source binaries, allowing users to create their own applications or operating systems.
This would, however, require regulation to ensure that manufacturers are allowed to provide these interfaces, as in some cases even the APIs themselves may be considered intellectual property, and manufacturers may not always be legally allowed to disclose them. Although it could be argued that if this is regulated, manufacturers would select vendors that can meet these regulatory demands.
The other issues to resolve here would be anti-tamper and chain-of-trust concerns that could arise from such an approach. However, if there were no expectation that users would continue to have access to the manufacturer's software or services, I think these issues could be resolved.
Sure, any app not running because of artificial software restrictions (and no, I won't buy the claims of """security""" when even the manufacturer doesn't have a real picture of what's running on the phone and cannot assess it's security - or sometimes even includes built-in adware!).
Another example of bad faith could be Apple removing true tone on official screen replacement.
Again, I'm not against the concept of chain of trust, it's just I've never seen any software restriction which I would think justified, so a good use case might exist in theory, I'm just not aware of it.
> The other issues to resolve here would be anti-tamper and chain-of-trust concerns that could arise from such an approach
I have serious doubts that integrity checks and anti-tamper mechanisms are legal in the current environment anyways as there's no real competition in the mobile space and these are further barrier to create competitors (and were even created for this purpose in the first place in some cases, like in Android)
It's definitely against current anti trust laws. These companies are just too large and too wealthy for the laws to be applied at the moment.
By not doing it you are basically outsourcing this cost to the environment.
E.g.: "for example, you may not be allowed to provide access to the radio firmware." Given that everything has a radio these days (everything is wifi- and/or bluetooth- enabled), this is just stupid. Why is firmware for basically essential infra not legally available?
Same goes for many, many, many other things.
Manufacturers need to pass certification for their radio implementations, such as FCC, CE/RED, PTCRB, Bluetooth SIG, etc. Any modification to the radio firmware can potentially change the device's RF characteristics and cause it to fall outside of the conditions under which it was certified.
This is why manufacturers generally cannot simply release the radio firmware and allow users to modify it freely, as doing so could result in devices operating outside their certified RF parameters and expose them to regulatory or legal liability.
Not to mention the intellectual property rights of the manufacturer and their vendors. The firmware may contain proprietary code, algorithms, or other licensed technology that the manufacturer does not have the legal right to redistribute, especially if it was developed by a third-party vendor.
Why would this expose the manufacturer, and not the device owner?
> The firmware may contain proprietary code, algorithms, or other licensed technology that the manufacturer does not have the legal right to redistribute
As per my comment above: "Given that everything has a radio these days (everything is wifi- and/or bluetooth- enabled), this is just stupid. Why is firmware for basically essential infra not legally available?"
E.g. I don't buy the bullshit argument of security and legal something, and of proprietary algorithms, for example, when Philips suddenly starts requiring a log in to control its bulbs via bog standard protocols: https://hueblog.com/2023/09/21/philips-hue-soon-only-usable-...
The same goes for nearly everything else.
This may be the hope or expectation you have with regard to regulation, but I don't think it is ever going to happen because it would conflict with other regulatory requirements, especially in the realm of radio.
You may say "regulation can be changed" but radio regulations exist for real reasons and I doubt anyone could convince the major governing bodies otherwise.
Not to mention that such a requirement could effectively force companies to give up intellectual property that they have invested heavily in developing. What if a manufacturer outsources the firmware development to a vendor that specializes in firmware? If the manufacturer were required to release that firmware as open source, they would effectively be forcing that vendor to open-source its product. That could undermine the vendor's entire business model.
You're saying the chips in iPads etc. are not regulation-compliant and this non-compliance can be trivially unlocked if you know the specs?
The radio modules in iPads are compliant, assuming that the software using those radio modules is compliant as well. This is why manufacturers have to enforce specific combinations of software and hardware, as not all of the functionality and regulatory constraints are implemented in the hardware itself.
If you gain access to the radio module of an iPad, you can definitely make it non-compliant, depending on the level of access the module provides. In my experience, however, radio modules generally provide enough access that a user could potentially cause regulatory issues if the relevant safeguards were removed or you do not adhere to the specification of the radio protocol you are using.
If you don't believe me look at Bluetooth SIG listings and you will note that they specify specific software versions: https://qualification.bluetooth.com/Listings/Search
Allowing users install what they want on it would be the best case scenario.
Instead we have bullshit like "your TV is three years old? No updates for you": https://developer.samsung.com/smarttv/develop/specifications...
> They don't have to support it indefinitely.
How long should support for devices last in that case? And what should be supported?
Indeed. An ancient 3-year-old device isn't receiving any OS updates. Which means it doesn't get features, its core software isn't updated inculding such minor things as the browser (most apps on TVs are browser apps), store etc.
Eventually its certificates will expire and it won't be able to connect to most things
> How long should support for devices last in that case? And what should be supported?
Depends on device. People don't buy TVs every year. So a 10-year support isn't out of the question. That said, 10 years should probably be minimum for almost all hardware.
E.g. Microsoft supports Windows for ~10 years, and for a much wider array of hardware.
After that: open up, and let people do whatever they want with it.
In the "save the planet" times.
Repair cafes are nice hobby projects for pensionados but it is not going to move the needle.
> Manufacturers must also provide [...] access to spare parts at a reasonable price.
This is the important part. Stupid shit like 0.3€ soldering buttons to 200€ motherboards so the repair is expensive has got to go.
Hopefully data collection that supports device-specific repair cost breakdowns and tracking is part of this legislation.
Currently, manufacturers optimize for manufacturing -- it's cheaper to assemble with a $200 all-in-one board than a discrete button.
If it were more expensive to use an all-in-one board (say, because they were on the hook for repairs and/or buyers had a place to easily compare repair costs...) then they'd do otherwise.
Price/cost obfuscation is the root of a lot of inefficiencies.
I won't call soldering anything on a 20-layers pcb "stupid shit".
If you want an economic argument there's no way to sell my free time for anywhere near the market rate on such a short notice.
Nevertheless, the point is not the electronic toothbrush, but rather the "BIG" stuff that costs much and it's creating a lot of garbage.
A 1200 euro TV that breaks after 5 years - are you willing to buy a new one just because?
Once you have that infrastructure in place, eventually also the "smaller" things will be cheaper to replace.
Things that are on the not hard scale to fix - cleaning robots, inkjet printers (with fill-in ink), laptops (incl. board repairs as long as they are not a BGA), desktop pc, mowing robots, mowers (all 2 and 4 stroke variants), most battery tools (drills, sanders, saws, etc.). Overall stuff that can opened reliably, even if that requires specialized tools like bearing pullers or impact wrenches.
Things that are hard - anything that uses glue as the prime assembly fastening choice, e.g. TVs and monitors (or just plastic clips). Cheap plastics (ABS) bodies are annoying as well. Fridges, no way to refill or fix the compressor. Serialized components that need specialized tools/software after being replaced.
In that regard that would be my complaint - ease of disassembly and clearly marked parts, exploded views, schematics. Spare parts. Personally, I'd spend half a night to repair 30-40euro device w/o any documentation, just b/c I can -- but that shall not be the norm.
I've played with entrepreneurship most of my life - I know how "a solution looking for a problem" looks like. Any VC would laugh them out of the room.
Edit: don't get me wrong - there is a part of this that is almost free and only requires a bit of enforcement. That part is good, and it's exactly what governments should deal with. But anything that imposes direct or indirect costs should go through serious cost/benefit analysis.
Washing machine repairmen never ceased to exist.
Helsinki (for one) needs some real repair cafés.
In Finland, the standard line is that they'll take your gizmo and put it in the repair queue - and then just to have someone in the back room so much as breathe on it - it's gonna cost ya 50, 80, a hundred.
reduce, reuse, recycleIt's because that's what we collectively told them to do.
In a forum full of "tech guys" that like "tech solutions" the number of comments that are against being allowed to thinker and repair their own devices is above zero.... we really need to drown out those voices, they represent a very shameful set of individuals that taint what (I would like to think) we like and prefer
This kind of misses the point though.
Don't get me wrong, the above is nice to have as a law, but it does not really understand the underlying problem domain. Louis Rossmann explained it several times already; the problem was not that primarily that upstream companies refuse to repair something, but that they deliberately make it harder for downstream folks to repair something, for many reasons. Planned obsolescence, trade secrets and other shenanigans, unable to purchase replacements parts and so forth. Having a law that forces easy repairs onto the upstream company, DOES NOT FIX THE DOWNSTREAM PROBLEM; and in some cases it will make it worse. If the EU were serious about fighting for consumers, they would require of all companies operating in the EU, WITHOUT EXCEPTION, to not deliberately make it harder for downstream people to repair things. We now live in the age of 3D printing, so really repairing anything should be much much easier (at the least for simple materials; I understand that 3D printing isn't that great yet with regards to tiny electronics parts). To me it seems as if lobbyists always sneak in and worsen the legislation here. Both in the EU and in the USA.
If your hardware start-up was going to tell me to buy a new product if it broke after a year, then I've no problem if it doesn't get going in the EU.
We don't need more cheap tat, we need things that can have a reasonable shelf life. We used to expect that from products as standard. Then when more things became electronic, it started to drift into obsolence after X years.
But there's so many products that don't need to be replaced. I don't need a state-of-the-art pedometer or weighing scales, I just need one that does the job it did when I bought it.
If Apple, Samsung and the Chinese manufacturer isn't compliant, then Fairphone just got handed a market of 500 million people with no real competition. Some US electronics manufacturer who doesn't want to deal with EU regulation, is handing over the entire market to someone who will, and that company can still sell everywhere else.
Down the road, if we make it, we will have access to funds for a few roles that maintain spare parts and a repair (more likely replace/refurb) department, that will coordinate with our manufacturing houses.
None of this blocks innovation or velocity for early stage startups. Unless you have more concrete examples I'm somehow missing?
People act like these are industry shattering requirements, but hard tech is already subject to a plethora of requirements we have to handle every day. We will always have some kind of process for CE certification, battery safety requirements, GDPR, or open source licensing and toolchain access, etc, etc. This is just another (honestly, minor) process to roll in with the rest of them.