• 19 Posts
  • 1.25K Comments
Joined 6 years ago
cake
Cake day: May 31st, 2020

help-circle
  • I find it annoying, because the hype means that if you’re not building a solution that involves AI in some way, you practically can’t get funding. Many vital projects are being cancelled due to a lack of funding and tons of bullshit projects get spun up, where they just slap AI onto a problem for which the current generation of AI is entirely ill-suited.

    Basically, if you don’t care for building useful stuff, if you’re an opportunistic scammer, then the hype is fucking excellent. If you do care, then prepare for pain.







  • Lots of “modern” languages don’t interop terribly well with other languages, because they need a runtime environment to be executed.
    So, if you want to call a Python function from Java, you need to start a Python runtime and somehow pass the arguments and the result back and forth (e.g. via CLI or network communication).

    C, C++, Rust and a few other languages don’t need a runtime environment, because they get compiled down to machine code directly.
    As such, you can call functions written in them directly, from virtually any programming language. You just need to agree how the data is laid out in memory. Well, and the general agreement for that memory layout is the C ABI. Basically, C has stayed the same for long enough that everyone just uses its native memory layout for interoperability.

    And yeah, the Rust designers weren’t dumb, so they made sure that Rust can also use this C ABI pretty seamlessly. As such, you can call Rust-functions from C and C-functions from Rust, with just a bit of boilerplate in between.
    This has also been battle-tested quite well already, as Mozilla used this to rewrite larger chunks of Firefox, where you have C++ using its C capabilities to talk to Rust and vice versa.





  • Ephera@lemmy.mltoComic Strips@lemmy.worldHealthy Snacks
    link
    fedilink
    English
    arrow-up
    21
    ·
    edit-2
    7 days ago

    A few years ago, I learned that the stomach rumble when you’re hungry, is part of a process that’s actually kind of important health-wise: https://en.wikipedia.org/wiki/Migrating_motor_complex

    So, it’s good when your stomach and small intestine empty out on a regular basis. It’s good when you’re hungry on a regular basis.
    Just yet another luxury problem of modern times, that we have food available at all times and need to stop ourselves from snacking.

    Side-note: It’s also good to go hungry, because then when you do eat, the food tastes so much better. This also means you can go for healthier food and still have it hit the spot.


  • Ephera@lemmy.mltolinuxmemes@lemmy.worldArch be Like
    link
    fedilink
    English
    arrow-up
    1
    ·
    7 days ago

    Hmm, good question. I know of one such implementation, which is Delta RPM, which works the way I described it.
    But I’m not sure, if they just designed it to fit into the current architecture, where all their mirrors and such were set up to deal with package files.

    I could imagine that doing it rsync-style would be really terrible for server load, since you can’t really cache things at that point…



  • Ephera@lemmy.mltolinuxmemes@lemmy.worldArch be Like
    link
    fedilink
    English
    arrow-up
    5
    ·
    8 days ago

    This doesn’t work too well for rolling releases, because users will quickly get several version jumps behind.

    For example, let’s say libbanana is currently at version 1.2.1, but then releases 1.2.2, which you ship as a distro right away, but then a few days later, they’ve already released 1.2.3, which you ship, too.
    Now Agnes comes home at the weekend and runs package updates on her system, which is still on libbanana v1.2.1. At that point, she would need the diffs 1.2.1→1.2.2 and then 1.2.2→1.2.3 separately, which may have overlaps in which files changed.

    In principle, you could additionally provide the diff 1.2.1→1.2.3, but if Greg updates only every other weekend, and libbanana celebrates the 1.3.0 release by then, then you will also need the diffs 1.2.1→1.3.0, 1.2.2→1.3.0 and 1.2.3→1.3.0. So, this strategy quickly explodes with the number of different diffs you might need.

    At that point, just not bothering with diffs and making users always download the new package version in full is generally preferred.





  • On KDE, it’s just one of the suggestions, I believe, that you could search this term on the web. If you trigger that suggestion, it then opens the web browser to do the search.

    As such, searching “terminal” wouldn’t yield a suggestion from a web result that matches, but I’m pretty sure applications are prioritized above other results either way.