It would be best if distros kept tap on kernel changes and update as soon as possible when they see a security issue fixed.

Sending emails to some big distros would still result with e.g. Gentoo not getting that info because they are not a big distro.

The problem is that the kernel devs (correctly imo) consider all bugfixes security fixes. So the distros need to decide for themselves which ones are important enough to warrant an update. Apparently this one had a quite unclear commit message, so it importance was missed.

Not ideal, but also: shit happens? It's always a balancing act choosing the lesser of multiple evils and most of the time it seems to work ok-ish, which is probably the best we can hope for ;-P

The kernel maintainers don't flag "security fixes" as special, and they have a well-thought-out reason for that, see many other comments in this thread.

That, and they flag pretty much any random patch with a CVE these days, making it harder for distro maintainers to keep up.

For this specific "bug" they took care to not mention any security angle in the commit message, making it extremely hard for an outsider to even realize this was a critical patch. I assume this was because they wanted to push the fix without breaking embargo.

There are so many distributions that it is not possible to notify each one, unless there is some single distribution list for all.

And if you disclose to just a handful, why ignore the rest?

You can look at the code in editor or IDE even when CLI agent is doing work.

I do that when I want to, but for me using agents in IDE is like looking with one eye covered.

Yeah, people learned.

I created a 4 subagents that polled for new tasks, and restart after ~5h.

It was a great run.

They do for any new plan. Those multipliers are only for people that paid annually. After their subscription ends they'll go into token based pricing like the rest of people.

Those multiplier are only for grandfathered Pro an Pro+ plans that had annual billing, basically a way to scare people of out of those plans. Ant new ones (and bussiness+enterprise plans) will be on token based billing since June 1.

Is that autocomplete better than IntelliJ own plus their local only LLM completion?

I uninstalled copilot plugin because it was eating memory and its completions where about 60% good and the rest was bad.

After switching back to IntelliJ I see just positives.

Local hooks are just a convenience. CI checks are assurances, you have to have them.

If one hates the round-trip he/she will adopt hooks quickly.

LFS hooks are not just a convenience, for example. CI, despite being a useful thing in its own right, is not a replacement.

Fair, I don't use LFS so I don't know how it works.

I was writing more in regards of hooks as "checks" for workflow/lints/etc.

It is still that person creation. Not sure about American law, but AFAIR in my country you can't remove the author from creative work (like source code), you can move the financial beneficiary of that code, but that's it.

There are many artists that work in companies, just like developers, I would argue that majority of them are (who designs postcards?)

I use Haiku frequently, and for my codebase it is working fine.

But I'm not vibecoding, I don't let models do large work or refactorings, this is just for some small boring tasks I don't want to do.