• 1 Post
  • 447 Comments
Joined 4 years ago
cake
Cake day: May 31st, 2020

help-circle










  • The fun part is that as a dev, you don’t really know that either. It’s just the file name of the executable. Anyone can rename that.
    And even if it’s not renamed, you still don’t know, if your users need to call it with just hx or with ./hx or some other path.

    Obviously, you should mention somewhere that the executable is likely called hx, but because that requires an explanation, there’s certainly a tendency to not mention it very often…





  • Ephera@lemmy.mltoLinux Gaming@lemmy.worldGitHub is down
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 months ago

    They’ve got a migration feature, which should also migrate issues, pull requests and whatnot.

    And then they offer a push mirror, so if you push to a Codeberg repo, you can have it automatically push to GitHub, too. (Alternatively, you could also just add two remotes to your local Git and push to both, if it’s just you developing.)

    They don’t offer a pull mirror, so where it would automatically fetch the newest commits from GitHub, basically because it lead to lots of abandoned repos needlessly eating up resources. But maybe GitHub offers a push mirror itself?
    More info for pull mirrors here: https://codeberg.org/Codeberg/Community/issues/1487#issuecomment-1575165

    As for general advice, from what I hear, the CI/CD stuff on Codeberg isn’t yet as mature as it is on GitHub, so if you need it, maybe look into that before you do the big jump.
    But yeah, I don’t feel like a ton advice is needed beyond that. You mostly interact with things via Git, which stays the same. And personally, I always find the Codeberg webpage easier to navigate than GitHub, despite my dayjob requiring me to use the latter daily.





  • It isn’t, if you’re already familiar with Rust. That’s all I’m saying. Swift usage is largely isolated to Apple’s ecosystem, which doesn’t have a ton of overlap with the open-source ecosystem.

    And I actually disagree that Rust is overhyped, because it can be used for creating libraries which can be called from virtually any other language, like you can with C and C++. Which means you’re not locked into the Rust/Apple/whatever ecosystem, but instead could be coding the next SQLite without needing to be fluent in footgun.

    From what I can tell, this would theoretically be possible in Swift, but hasn’t been implemented: https://forums.swift.org/t/formalizing-cdecl/40677

    But even if Rust was the most overhyped garbage, it would still be garbage that people are familiar with. ¯\_(ツ)_/¯