With all due respect, you're one individual and basic color terms for a language are not determined by a single individual. If you look at usage via proxies like Google ngrams[1] or Google trends[2], cyan barely registers, which suggests it hasn't really shifted to a basic color term.
But its frequency still rose by over 300x since the start of the chart, which might suggest that for some people it is a basic color term.
"English" isn't one monolith. Every English speaker speaks their own version, some closer to each other than others, and new features are constantly being added or removed.
The further you have to narrow down the set of speakers for whom it's a basic color term, the less of a basic color term it is for English as a whole. We don't have to have this argument about e.g. orange.
Your analogy with CI/CD is flawed because while not all were convinced of the merits of CI/CD, it's also not technology built on vast energy use and copyright violation at a scale unseen in all of history, which has upended the hardware market, shaken the idea of job security for developers to its very foundation and done it while offering no really obvious benefits to groups wishing to produce really solid software. Maybe that comes eventually, but not at this level of maturity.
But you're right it's probably unenforceable. They will probably end up accepting PRs which were written with LLM assistance, but if they do it will be because it's well-written code that the contributor can explain in a way that doesn't sound to the maintainers like an LLM is answering their questions. And maybe at that point the community as a whole would have less to worry about - if we're still assuming that we're not setting ourselves up for horrible licence violation problems in the future when it turns out an LLM spat out something verbatim from a GPLed project.
Of course, nobody is claiming that there aren't lots of Firefox crashes which are caused by bugs in Firefox. Quite the opposite, based on these figures. What people find interesting is that the amount they're suspecting are down to hardware faults is way higher than most people would have expected.
Reactive UIs may have been made popular on the web, where they're an absolute nightmare, but native code does them better still.
Best time I ever had in a job was writing WPF applications in C# using ReactiveUI. Once we really understood the underlying model we were plugging stuff together so easily. It is a really good model, but I can't see how React is a good example of it.
Of course I had lots to complain about then, WPF had bugs, C# has a number of big problems, but it was, overall, very nice.
Maybe it's because there's no overall benefit to these things.
There's been a lot of talk about it for the past few years but we're just not seeing impacts. Oh sure, management talk it up a lot, but where's the corresponding increase in feature delivery? Software stability? Gross profit? EBITDA?
Give me something measurable and I'll consider it.
Scaling up PV production to the point where we could convert the entire Earth's electricity generation to solar is incredibly significant.
Yes there's the problem of intermittency, varying sun availability and so forth - which is why solar will never provide 100% of our power and we'll also need grid-scale storage facilities and domestic batteries and all sorts of stuff - but just imagine being able to make that many panels in the first place! Literally solar on every roof, that's transformative.
But sure, let's send it all to space to power questionable "AI" datacentres so we can make more fake nudes.
Absolutely. Labour betrayed their core voters, who are looking for something else, but won't touch Reform UK because they're even more disgusting than the current right-wing Labour-in-name-only government.
reply