If it's mentioned up front and fixed then it's fine. One way or another the restaurant needs to cover it's costs and it's either done via inflating the price of the food or a fixed service fee.
What I hate is a discretionary tip suggestion because suddenly I'm made to be responsible for how much the staff get.
On the potentially bright side maybe this will make people think harder about which model to use for which task. You don't need to feed your entire code base into Opus when a Gemini Flash sub-agent can do a perfectly fine job running grep and compiling a summary for the main agent.
Even Debian has popcon as an opt in. I can see why collecting data about hardware and package choices is useful to Ubuntu. I didn't think they collected any personally identifying information.
I also have a diverter which heats up my hot water tank which saves on gas, especially in the summer.
It will be fun watching those users who first make the jump to the new project.
Export to the grid, for every kWh I export during the day I can afford two kWh overnight.
If it's finding valid vulnerabilities then it's just another tool like static analysis, fuzzers and sanitizers. There definitely seems to be a difference in quality compared to earlier generations that were behind the sloppy avalanch of reports.
Funny 😂
They don't have to be. They know what they asked the LLM to do. They know how much they adapted the output. You usually have to work to get the models to spit out significant chunks of memorised text.
No, that's why the author asserts that with their signed-of-by. It's what I do if I use any LLM content as the basis of my patches.
If the 2-10% is just boilerplate syscall number defines or trivial MIN/MAX macros then it's just the common way to do things.
I'm going to take a swing at the moon reflects a relatively uniform spectrum of light from the sun but our varied atmospheric conditions can alter the refraction of that light.