They will not get as safe as cars. They are inherently dangerous, it's like taking a car and removing every safety feature. Removing doors, windows and belts. There's a reason that there is a legal requirement in many countries to wear a helmet.
I spent some time in Vietnam back in 2005, after getting a few lifts on the the back of mopeds in both Hanoi and Ho Chi Minh City, I decided to look up some road traffic accident stats for those cities: I never took another lift like that again.
I just had a horrifying flashback to the Creative Labs driver download page... some wizard-style abomination three levels deep, nothing just a simple link.
Still, the archive was complete and you'd end up getting what you went there for, so still infinitely better than the average experience today.
Mechanical code review by something like sonar qube is much cheaper. Use that for low bar quality gate and AI after.
AI code review is startlingly effective. Continually finding things me and my colleagues never would. Well the decent models do. Maybe not so much the cheap ones.
My gut reaction to this is that there is something seriously wrong if special clauses are required. Why should open source get special treatment, to me that just highlights that the law is utterly ridiculous.
Technically opensource stays the same. The special treatment is for closed source OSes that get an additional legal protection for their datamining. We should not be passing laws that legalize the datamining of people.
One of the problems with the original law is that it failed to distinguish between open source projects and closed source products. If anything this amendment should make the law less objectionable, not more.
I've been really struggling to get AI to write good quality c# code, or to be precise, what I see as good quality.
I'm in two minds on if it matters or not.
On one hand I think, I want to be proud of it, I want to be able to explain it, if it breaks I want to be able to figure out why.
On the other hand, AI can do all of that with badly written code, so who cares.
Edit: however, it still feels like an amazing power tool, but it has taken me months to figure out how to use it.
I have the opposite experience of everyone else I follow online, I find it terrible at green field and great at brownfield. Green field it makes horrible choices as it has nothing to follow.
I'm in no way a very good programmer, or very smart, but the code I saw most of my co-workers writing was about the same quality as AI, not very good.
I mean, you don't have to update if you think that's the most likely vector (I don't disagree, at least for managers that have no online components, not even an update check). I'd recommend reading the changelogs though to see if they upgraded encryption parameters or did other fixes that you should want. You could wait a while applying them, and/or spot check if the diff makes sense
Unless you want sync or other online functionality, you're almost certainly better off with an ancient version of some trusted password manager than with a custom implementation. And if you do, I'd still not necessarily recommend it, but then imo it depends on your experience/knowledge level (regardless of whether you use an LLM)
I've never heard of the one you mention so I can't say anything positive or negative about it. The page looks ancient enough that I... not immediately trust it blindly, but it speaks for it. They either care about stability (not jumping on the latest fashion trends) ...or it's abandoned and the last release might or might not be flawless :p
Nothing in particular. In my head all that needs to happen is some form of update (dependency, core project or the Android version on my phone) and sneaks in something that reads the unencrypted file and sends it over the internet somewhere.
I wish android and windows had flat seal, as far as I can remember that can prevent all network access for a given app.
reply