I tossed that number out as my experience, and it varies wildly task to task and language to language.

For C development, I'd imagine it's super accelerating, as there's so much boilerplate micro managing.

For python, less so as it's a bit less boilerplatey.

If wanting to make a variation on a fairly common pattern, really accelerated. If trying to work in a niche context, frequently more annoying than helpful if you try to prompt, but maybe decent at AI augmented code completion.

They already slop up excessive documentation. That's one of the issues is that a issue report or a pull request that might have formerly been to the point is now a big verbose essay. An issue might drone on about the history of string formatting and the various capabilities and the entire rationale of why hexadecimal is so useful in the context of computing and documenting how prevalent it is.

For a pull request that adds an argument to switch some numeric data to hexadecimal. Bonus points, instead of a refactor to shunt numbers over to a common format handler, it might duplicate the logic N number of times, depending on how things rolled that day. Especially CSS, vibe-coded frontend stuff loves to vomit up needless CSS...

The one line explanation suffices, but I see a wall of text and have no idea what they are on about because it's buried in there somewhere among fluff..

But that's my whole point, what you describe is the 20-50% faster scenario.

What is driving most of the annoyance with pull requests are the folks that just tell it to do something and then it spits out a bunch of plausible code, particularly if not testable.

One example:
https://lore.kernel.org/lkml/3...

The proposal was *probably* vibe coded and submitted to the kernel to get some attribution, and the code was fundamentally untestable, and constituted basically LLM guesses about what PCIe7 would look like. Structurally credible, but a volume of negative value crap because it's outright incorrect per people that actually know what it looks like and had to waste their time just in case it was a credible origin for this.

*This* is what responsible open source contributors are up against, not because the slop is viable, but just because the slop drowns out the better. Your AI generated code may be fine because you actually oversee it credibly, but by volume most GenAI output is slop, because of the humans feeding the prompt getting more volume if slop suffices for them.

GenAI rewards those that just don't give a crap and trust the output far more than it rewards people that want to make sure the generated output is actually what you want and done well.

So someone turning on the token hose to an agent that can create and comment on pull requests and all this stuff flood with useless crap. They are going to vomit up probably about 100x more "stuff" to the world than a traditional developer, and further it's a fad where there's probably 5x more people trying.

Someone that uses it to generate and curate the result, who would be able to likely contribute even without the agent, *might* be able to be significantly more productive with credible product. But we are talking about maybe 1.2x to 1.5x in the context of credibly shareable code that would be put into projects (a higher multiplier for throwaway single purpose stuff that won't need maintenance or is something like a basic site).

When 99% is slop, it's hard to imagine the 1% to be worth it.

Yeah, I think the big question is was Eclipse as unhinged as the blog posts suggests throughout, or was this unhinged state brought on by unreasonable treatment by Microsoft...

From some analysis, I think MS team became less competent and more bureaucratic, and probably struggled to understand whatever the hell Eclipse was getting at, and Eclipse was perhaps on top of confusing was also potentially offended that they failed to respond in what he thought was an appropriate amount of time.

So Eclipse obviously had real stuff, but maybe MSRC couldn't understand, and Eclipse took it gravely personally and here we are.

The other option is that MSRC engaged as described and drove Eclipse to be unhinged after trying to engage in a reasonable way.

My life experience is probably that the former is the scenario, that he was smart, but communicated poorly and took offense easily when faced with a boringly incompetent corp team and mistook their nature for malice initially. Things might have gotten heated on Microsoft's side, but I would guess Eclipse went off the rails first, based on his communication style on display in his blog...

Funny thing is that it's literally the opposite, it's the worst at stretching the imagination.

Just saw a claude commercial, and their pitch was "hey, you can use us to make a knock-off dropbox"

Their big stunt a while back was "we made a knock-off C compiler"

Everything is about making knock offs because that's what GenAI can do. It can certainly tailor the knock off in ways that were easier than what it formerly took, but roughly knock-off in their bread and butter

A generic site builder... Yeah that's pretty firmly in the reach of GenAI...

CIA is supposed to deal with external threats. Is this rule rigidly adhered to? Given what we have seen from the Wyden Siren, I seriously doubt that the CIA is holding to this rule.

Google makes money by selling adverts and information. It's not actually in Google's interests to allow random websites to mine their customers' data.

It sounds to me like the input to the algorithm is truly random, but not unbiased, and the algorithm perfectly unbiases output from the particular source they are using. The rest of the article goes into the type of flaw they're addressing, and talks about very slightly unfair dice, which you could correct, but you'd need to know exactly how unfair they are, and you're always going to be very slightly wrong and end up correcting not quite perfectly. The obvious quantum RNG is to generate polarized light and measure it perpendicular to the polarization, but you'd still need to get it perfectly perpendicular. It sounds like they've built something that doesn't rely on precise alignment to give a known distribution, which they can then use to unbias the output perfectly.

Or just get a usb air mouse remote. There's plenty available.

Why build your own? There are plenty of available set top boxes on the market complete with remote controls and a variety of different software, everything from the cheap chinese android boxes running kodi to the apple tv, and all of them are better than the crapware bundled with any tv set.

This was back in the 2012-2015 time frame ... so "buy them bigger drives" wasn't always a reasonable solution. A lot of them were using Macbook Airs that were great for their needs EXCEPT for the SSDs not being as big as one might prefer.

I'm sure I'm just an outlier here. But I bought a cheap big screen LCD smart TV at Best Buy 3-4 years ago. It was a Westinghouse branded set running Roku TV.

At some point, they updated the firmware to consolidate the TV guide in it so it displayed all the streaming content and your over the air TV stations in the same guide. (Used to be, you had to pick a Live TV icon/button to look at your OTA content in its own place.)

Ever since that happened, the TV forgets all my OTA stations regularly so I have to go into setup and re-scan for all of them, to get them to reappear in the guide. REALLY annoying.

It would be awesome if a total UI makeover for it results in fixing this problem.

I knew several people in ruraltania who bought into the 3rd generation of raising Vietnamese potbellied pigs. First and second generations made a fair amount of money selling into a rising novelty market; the second generation also made money selling to third generation hopefuls. Third generation breeders lost their shirts of course. Before that it was small farmers in central Ontario who discovered that ginseng grows very well in that climate and soil and that was large, nay HUGE, demand for that root in the PRC. This is perhaps even more germane to the tech example because it takes the first crop of ginseng 7 years to mature, so many many Lake Erie-area farmers saw their early-in neighbors harvesting the crop and the cash - only to see the market flooded and prices crash the year before they were due to harvest.