Is your suggestion that people should? Isn’t Rust the more realistic, effective solution because it forces people to do better? Evidently, “correct memory safety in C/C++” didn’t work out.

Valve is generously providing backing for two critical projects that will have a huge impact on our distribution: a build service infrastructure and a secure signing enclave.

What is Tails?

and Tails, a portable operating system that uses Tor

Now that you say so, I feel like I’ve read about this before. In comments about Diatraxis/one of them years ago. :)

I’m using the website / native website interface. It’s at least possible there to edit the post and url. May be different for “Lemmy clients”.

I like that even here on Lemmy, with inline code format, colors.ini is not being colored but color.ini is. Great symbolism for your issue.

If you only care about contributing improvements, no, it doesn’t matter.

If you want to at least be recognized as an author, and be able to say “I made this”, the license opposes that.

Waiver of Rights: You waive any rights to claim authorship of the contributions […]

I don’t know how they intend to accept contributions though. I guess code blocks in tickets or patch files? Forking is not allowed, so the typical fork + branch + create a pull request does not work.

I’ve been using TortoiseGit since the beginning, and it covers everything I need. Including advanced use cases. I can access almost all functionality from the log view, which is very nice.

I’ve tried a few other GUIs, but they were never able to reach parity to that for me. As you say, most offer only a subset of functionalities. Most of the time I even found the main advantage of GUIs in general, a visual log, inferior to TortoiseGit.

GitButler looks interesting for its new set of functionalities, new approaches. Unfortunately, it doesn’t integrate well on Windows yet. Asking for my key password on every fetch and push is not an acceptable workflow to me.

That’s less than I expected. If there’s 141 commands that on average comes down to 10 per.

git has 17 million options

proof needed /s

I wonder how many it actually is.

Looking at the Web Archive; Diatraxis has been around since 2021. That divio docs since May of this year.

I doubt they didn’t “get inspiration” from Diatraxis.

It’s certainly something that looks better, but contrary to green washing, I see real, practical value.

I would rather be able to see and inspect source code than not. And I would rather have the right to take and fork a two year old version than not. Or be able to wait two years to fork the current version.

Those are real good value. Those bring certainty in infrastructure robustness and freedoms.

You posted the article link in the post content instead of linking it in the post. Was that deliberate?

You can still edit the post and set the link. (Then people can open it from the post title.)

The conversion is part of the license. It does not require the company to take any action.

The source is available with a restricted license, and e.g. two years later it relicenses itself to a FOSS license, automatically, as defined by the original license.

You are going to get lots of downvotes, and this comment will too.

👀

Hahahahahahahahahahaha

(Pause for breath)

Hahahahahahahahahahaha

Was that tone really necessary? I would have liked your comment more without this part.

I’ve not seen those kinds of issues. Apart from some dedicated pseudo-/farm-projects.

But still, it has entirely lost its appeal or even viability to me.

I participated many years, until - I presume - it got too big. I was not able to find good projects, the contributions I made most of the time were not reviewed nor labeled hacktoberfest-accepted. An an extrinsic motivator, it became more frustrating than motivating.

Using early returns and ternary conditional operator changes

private boolean meetsRiderPreferences(Rider rider, Driver driver) {
    if (driver.rating >= 4.5) {
        if (rider.preferences.includes('Premium Driver')) {
              return driver.isPremiumDriver;
        } else {
              return true;
        }
    } else if (driver.rating >= 4.0) {
        return true;
    } else {
        return false;
    }
}

to

private boolean meetsRiderPreferences(Rider rider, Driver driver) {
    if (driver.rating < 4.0) return false;
    if (driver.rating < 4.5) return true;

    return rider.preferences.includes('Premium Driver') ? driver.isPremiumDriver : true;
}

dunno if java has them, but in C# switch expressions could put more of a case focus on the cases

private boolean meetsRiderPreferences(Rider rider, Driver driver) {
    return driver.rating switch {
        < 4.0 => false,
        < 4.5 => true,
        _      => rider.preferences.includes('Premium Driver') ? driver.isPremiumDriver : true,
    };
}

or with a body expression

private boolean meetsRiderPreferences(Rider rider, Driver driver) => driver.rating switch {
    < 4.0 => false,
    < 4.5 => true,
    _      => rider.preferences.includes('Premium Driver') ? driver.isPremiumDriver : true,
};

The conditional has a true result so it can be converted to a simple bool condition as well.

private boolean meetsRiderPreferences(Rider rider, Driver driver) => driver.rating switch {
    < 4.0 => false,
    < 4.5 => true,
    _      => !rider.preferences.includes('Premium Driver') || driver.isPremiumDriver,
};

Be bold and make changes. Document what you find out, what is outdated, what is missing.

Take ownership. If there’s nobody that oversees overall structure, be the one to do so - at least where you’re touching it or are being bothered by it.

Diatraxis gives some great insight and considerations input into writing and structuring documentation. Namely how different target audiences and doc use cases require different forms and detail levels of guidance.

My company’s internal doc/guidance also links to https://www.writethedocs.org/guide/ which seems like a good source.

Blazor is incredibly versatile in terms of where and how you run it. The UI is in HTML and CSS, the generated runtime bindings in JavaScript, but you can code the backend as well as frontend logic in C# / .NET / Razor template files.

It can render on the server or client, even work offline with WebAssembly and Service Worker, and dynamically switch between or combine them.

You can also integrate it into Windows Forms, WPF, or multi-platform .NET MAUI with Webview2, which will render “as a website” while still binding and integrating into other platform UI and code.

Your goals of “neat little GUI” and “as portable as possible” may very well be opposing each other.

Main questions are what do you have (technologies); what are you constraints, and what do you need. Different tech has different UI tech. Overall, most GUI programming is a hassle or mess.

If you want to dip your toes, use the tech you like, and look for simple GUI techs first. Don’t try to do everything/all platforms at once first.