An additional regulation that will come into effect soon (fully only in 2027) is the Cyber Resilience Act which will require all manufacturers to provide at least security updates for however long a "reasonable user" expects to get security updates.
The recitals say:
"In determining a support period, a manufacturer should take into account in
particular reasonable user expectations, the nature of the product, as well as
relevant Union law determining the lifetime of products with digital elements."
and
"The support period for which the manufacturer ensures the effective handling of
vulnerabilities should be no less than five years, unless the lifetime of the product
with digital elements is less than five years[...]"
So....it's a bit up to us to ask vendors for updates for older devices so that we can maybe slowly move the baseline of what a "reasonable user expectation" is.
I've tried various tools (including Cursor) and my problem is that they often (more than 50%) generates non-working code. Why does it do so? Because the ecosystems change so fast and they have been trained on old versions of various libraries (by definition) but when I use the latest version it's a constant uphill battle. And there are so many different combinations of how to use libraries together....
I can't be the only one facing this issue but I didn't see a lot of discussion around this.
So, as someone said: It's generating at most average code and most of it is outdated and sometimes vulnerable because... Well that's what's out there.
I still use these tools but mostly to know how a solution could look roughly and then start to do my own research and to avoid the black page problem. Sometimes just to learn what to even Google for especially in ecosystems I'm unfamiliar with.
I don't think this is absurd at all, I'm in the exact same boat.
In fact, I suspect most people have far more sophisticated relationships with digital companies these days than ever before. Grievances like cancellation pain are an oversight of antiquated businesses that don't realize it, imo
Just to add a different opinion: I have been using Jira my whole life and I am now using GitHub issues full-time and I like it a lot, I also like these new changes and I'm looking forward to even more to dependencies between issues.
I'm sure you know but just to make sure. You can use Issue Templates to steer people towards Discussions. It's not perfect but it can help a bit at least.
Yes, we've got that and it does help a bit. But we're often forced to be heavy-handed and just close junk issues with a comment asking the poster to open a Discussions thread. I feel bad about doing that though as it's hard not to come across as unfriendly.
The recitals say: "In determining a support period, a manufacturer should take into account in particular reasonable user expectations, the nature of the product, as well as relevant Union law determining the lifetime of products with digital elements."
and
"The support period for which the manufacturer ensures the effective handling of vulnerabilities should be no less than five years, unless the lifetime of the product with digital elements is less than five years[...]"
So....it's a bit up to us to ask vendors for updates for older devices so that we can maybe slowly move the baseline of what a "reasonable user expectation" is.
reply