Having been in some of these values meetings, I really imagine it went like this: someone wanted speed, and someone else wanted quality. Sorry, I mean Speed and Quality. Many people said there is a tradeoff between those two things, and only one thing can be first.
Some brilliant businessman: "I know, we'll combine them. We want Speed _and_ Quality." Thus, "Speed with Quality." Tada!
Values are a tradeoff: only one thing can be first. Trying to duck that is stupid.
The funny thing is you absolutely can do things which improve both speed and quality at the same time (basic good engineering), but they're like 3 or 4 orders of effect removed from those outcomes and impossible to do when you have someone breathing down your neck asking "does this make us go faster" at every step of the way.
Also "our velocity is 3x higher than it would be in the imaginary invisible universe where we made worse decisions 6 months ago" is impossible to measure, whereas "we cut a bunch of corners and shipped a piece of garbage on an arbitrary deadline" is very measurable.
That is an incredibly long bow to draw from someone that obviously doesn’t know what they’re talking about and is willing to make massive jumps to conclusions. Do you know how ecommerce works? I agree that it is a bit absurd, but not nearly as absurd as your claim of “the only reason”.
If a single non-malicious code change can break a thing like that with nobody noticing that's a catastrophic failure in testing, QA, and operations (nobody noticed 20% of euros transacted just stopped). It's hard to blame that on IC engineer.
I know that, now. But apart from this incident being in the annals of time as it relates to my work, there absolutely was no fallout, which my mind could not comprehend in those days.
> 56 interoperability requests under the Digital Markets Act have produced no concrete solutions by Apple,
The chart, stupidly created as a pie chart and with percentages rather than numbers: 21% of requests are in Phase III, ie implementation by Apple.
When liars make clear their intent is to deceive, the correct reaction is to ignore them entirely. You can fairly quibble about what requests are approved or not, but honest people fairly communicate the state of things.
Maybe you are saying something that makes sense. But your comment doesn’t read that way.
A “concrete solution by Apple” would be a solution that shipped.
Cook got accused of acting illegally by a judge. Which is very unusual. It is pretty clear that Apple is dragging their feet as hard as they can get away with.
Firefox often groups tabs from the same site into one process. With large numbers of the same tabs open in both, check the total memory for all firefox processes and all firefox processes. You will likely find firefox actually uses less memory than chrome.
I disagree. It's great that you can get a Wen track saw with 100 in of track for $200 with tax and a Makita with 100 in for $800. People who just want to cut a sheet of plywood aren't stuck paying $800, or more likely, using an inferior tool because the cost doesn't match value to them.
> have everyone believe that trivial feature requests take time to implement.
This could not be more wrong. Features do, because telling a user they can do X comes with a standing promise that it works, the results are correct, the ui is accessible, the feature cleanly interacts with all other features in the system (both now and in the future), corner cases are worked out, etc. And that burden is where prod+eng spend time.
Sorry, but that's really absurd entitlement and also contravenes the license.
Open source is fundamentally a gift culture from the authors: here's a thing. You can use it for free; it may or may not meet your needs; but I do not owe you anything either way.
Gifts come with some implied responsibility from the giver and a niche hobby project is different from a package manager.
Take it to the extreme. What if I write a library, put an OSS license on it, advertise it, and then bundle malware in the release.
Am I fault for including malicious code, or are the users who downloaded it entitled for expecting the code, that I asked them to use, will not harm them.
I would argue the burden is mostly on the user for smaller niche projects, but mostly on the developer for large, heavily advertised, critical infrastructure projects.
It is not entitlement to expect operating systems, package managers, browsers, etc to be following good practices.
Having been in some of these values meetings, I really imagine it went like this: someone wanted speed, and someone else wanted quality. Sorry, I mean Speed and Quality. Many people said there is a tradeoff between those two things, and only one thing can be first.
Some brilliant businessman: "I know, we'll combine them. We want Speed _and_ Quality." Thus, "Speed with Quality." Tada!
Values are a tradeoff: only one thing can be first. Trying to duck that is stupid.
reply