AnimalMuppet

"If you vote this time, you'll never have to vote again", so, maybe?

Don't roll your own numeric libraries. There are libraries with decades of improvements to handle corner cases and increase stability. You won't create a better one, not in one lifetime.

So, yes, in some cases code reuse through libraries really does improve software quality.

It fundamentally comes down to this question: Can I, the user of this library, produce a library that is more robust for my purpose than the existing libraries? Those who say "yes" often underestimate the amount of care needed to create code that actually works - that works solidly, that is robust against failures on certain inputs.

But, you say, you don't actually have any of those inputs, so why do you care? You don't - now. But the day may come when your program is going to have to handle those inputs, and when it does, then it's your problem, because you wrote the library.

Amazon may be better than getting in your car and driving downtown to visit several stores to see if they have what I want. It can still be worse than it was five years ago, though, and that difference can still grate on users, even while the users continue to use it.

Facebook may be the best way of seeing updates on what my grandchildren are up to, and it can be much more of a dark pattern, enslaving mess compared to what it was five years ago. People can still feel the difference and resent it, even while they look at their grandkids' pictures.

Now, I don't know how many of those bugs were privilege escalations, or could be leveraged to be. I'm not sure that people tried to exploit in the same way back then (or, if they did, if they said anything publicly about the results). Still, even if the majority of those bugs were not exploitable, OSes were much smaller then.

So that's my conclusion of how we got here: We've always been here.

I mean, there's no tech angle here. The discussions are mostly "yay, our side won!". That's one step away from turning into a flamewar, if the other side gets out of mourning enough to show up.

Whether it turns into a flamewar or not, there's no fodder for an HN-style discussion here.

Why would they flag such a thing? Election results aren't really very much of an HN-style topic. "Yay, our side won!" is not usually a very thoughtful conversation. Nor is there anything tech-related whatsoever in the topic (aside from some somewhat-off-topic conversations about data centers).

The site guidelines say that most stories about politics are off-topic. This one fits into the "most stories" category.

Off topic: I first wrote "2029" instead of "1929" because habit. Wow, the start of the Great Depression was 97 years ago? I find that surprising.

Applied math wants to solve a practical problem. It wants to do something that will actually matter in the real world somewhere.

Pure math wants to understand. It doesn't care about practical application. But we still want it to do well and thrive, because it makes the tools that applied math has available, and when you have a practical problem, that matters.

Or, if you insist on keeping your claim, then when the SEC is playing "favorites", it's "the favorite set of rules", not favorite companies.

The right answer isn't forever patching freezer software. The answer is either to not have them on the internet, or to have something in front of them, and keep that thing very up-to-date. (Or maybe several layers of "something" in front of them.)

What I've seen (at least at one place I worked) is that the code may be very well engineered for further modification - but only by people who have worked quite a bit on that code. For someone coming from outside, it's almost impossible. It takes forever to find your way around, and figure out where the magic place is that you need to modify in order to work within the existing design.

Well, you say, that's what the design documents are for! But they didn't have enough detail. They described the major objects, but not all the ancillary helper objects. They didn't describe the flow of data through the system in enough detail to know what to modify. The knowledge was there, in peoples' heads, but it was hard to get those peoples' time.

So, yeah. "Well engineered", but not engineered for maintenance by people who are not those already in the group.

Why are gas and diesel prices high? Is it because of lack of refineries? No, it's because crude oil got expensive because Trump attacked Iran and they closed Hormuz.

What's building an new refinery going to do? Reopen Hormuz? Reduce the price of crude? No and no. Is there going to be anything more for the new refinery to do than the old one would have to do? No.

So why would you build a new one? Lack of refineries is not the problem.

If lawyers are going to straight-up lie, then that can cost them the case, or get them sanctions, up to being disbarred from practicing.

For any reasonable definition of "prompt injection", that pretty clearly is one.