I wanted to read about double pump but the linked article looks like a general benchmark, without an explanation of that concept?

So instead of one replacement… we have seven:

haha

https://status.codeberg.org/

Uptime status may not be representative though.

When I open the dashboard right now it loads the HTML but then only shows a loading icon.

Codeberg published a blog post yesterday. They suspect (or know?) that it’s a broadened attack because Codeberg hosts liberal and human projects.

In the past days, several projects advocating tolerance and equal rights on Codeberg have been subject to hate attacks, such as massive spam of abusive messages in their issue trackers. We have been monitoring the situation closely and have tried to clean up the content as quickly as possible.

Often, content remained available only for a few and up to 30 minutes. Due to constrained personal capacities, some rare cases have remained online for longer. We appreciate all your reports to abuse@codeberg.org that help us identify abuse quickly.

On 12 February 2025, an abuser has escalated the attacks to a next level. Instead of targetting individual projects, they have started to create abusive content and mentioned Codeberg users in chunks of 100 each.

(emphasis mine)

Without having looked into it, I find it plausible that it could take several patchsets to come to an assessment of consequences and conclusion. Especially as they happen alongside assessments and discussion. The patchset number may also be largely irrelevant depending on what was changed.

This is the first time I have seen a Wikipedia weblink that sets a display theme via parameter.

Is this a subtle campaign for everyone to use vector? /s :P

I think the issue with that would be increasingly working catch-up on newer developments of replaced functionalities.

If your end-goal is integration then it’s better to integrate early rather than late.

Developing and maintaining an interface and abstraction and having to keep that up to date is one thing. But after replacing some modules and components, any developments on their originals raises the question of how does that apply to our Rust module? If it already were in the Kernel and had replaced that module or component, that effort would not arise.

You say it’s “needless” complexity. But that’s what’s up for debate, and most people, including Linus seem to disagree with you.

It’s not a matter of whether Rust is demonstrably superior and more secure, that it is seems to be the common understanding and agreement.

A new project matching reasonable Kernel feature-parity would be too much effort. It’s unrealistic.

The value is in moving the Kernel itself into a safer space and tool-space.

The idea that a technically superior solution would naturally supplant an earlier one with a huge market penetration and stability is wishful thinking. We see it in many areas. Without significant issues people at large will stay with what they know and what is popular.

I’ve tried it briefly, but didn’t like it/did not find an intuitive or preferred way into it.

A rare case of a topic text opening with providing context on what it is talking about. Thank you! I love it.

I don’t use one. I don’t feel like I have conflicting keybindings, or a need for additional keys. When I do, I customize my bindings through settings.

I mainly work with C#, where I use Visual Studio. I think I mainly changed bindings for expand selection, and go to definition, declaration, implementation (ALT+A/+S/+D). All other bindings work out for me.

Cursor and selection “jumping” with CTRL and SHIFT, and using multiple cursors is a regular occurrence for me. I largely keep using keyboard, but for navigating I do often switch to or combine it with mouse.

When it’s not C#, it’s often VS Code, or otherwise Notepad++ for non-IDE simple editing. For even simpler quick edits I also use Double Commanders integrated text editor.

I use TortoiseGit, and its diff editor. I sometimes make changes there too. I also occasionally use KDiff or Winmerge.

I think whether it’s worth to learn a new one should be determined by 1. what are your pain points/shortcomings, 2. what are the promises or your hopes, and 3. testing it out.

If you explore a promise and quickly find it not useful to you, it may be easy and simple to dismiss a switch without investing more.

"" to '' … There is nothing to highlight for SemanticDiff.

Really? I definitely want to see that. I want to be deliberate about my code. I am not only targeting compiled code. I am also targeting developers through maintainable code.

I’m surprised they did not list an alternative that would be my preference: Highlight the entire string. The f prefix changes the entire text value type. I would like the `f´ to be highlighted strongly, and string it changes the interpretation of weakly, and the placeholder variable more strongly again.

Case insensitive handling protects end-users from doing “bad” things and confusion.

Title: “is finally rolling out to the wild”

Content:

Ahead of Legion Go S shipping, we will be shipping a beta of SteamOS which should improve the experience on other handhelds, and users can download and test this themselves.

So, neither that product is rolling out yet, nor the SteamOS beta is rolling out yet?

(This quote is from Valves announcement, but meaning-equivalent to the linked article sentence regarding it.)

The server sidebar has an uptime stat. Could also have a simple monthly costs covered percent stat.