• 2 Posts
  • 32 Comments
Joined 2 years ago
cake
Cake day: June 20th, 2023

help-circle
rss
  • i second the comment that you need to consider why you want to do this. You generally need a pretty good reason to split your codebase into multiple languages.

    As far as actually doing it, you have a ton of different options, some of which have been mentioned here. Some i can think of off the top of my head:

    • create a library (dll or so file or the like)
    • set up a web server and use communication protocols (either web socket or rest API or the like)
    • use a 3rd party communication/messaging framework like MQ or kafka or something
    • create your own method of communication. Something like reading and writing to a file on disk, or a database and acting on the information plopped in

    basically every approach is going to require you to come up with some sort of API that the two work together through, though, an API in the generic sense is basically a shared contract two disconnected pieces of code use to communicate.




  • You’ve obviously gotten the base level answer, but to add some color here - certain types of food, such as dried pasta, rice, beans, grains, high proof alcohol, vinegars, and basically anything frozen to name a few, never spoil in the sense that they’re unsafe to eat.

    Flavor, however, is an entirely different matter. Just ask anyone who has eaten freezer burnt food.

    Pretty much any high proof alcohol will fall into this category. And, if it’s unopened, it should retain most of its flavor for a very long time. Once opened, however, it can deteriorate relatively quickly, depending on how it was stored.


  • It was the official discord until earlier this year, so it’s kinda not just “some unofficial server”. Also, the mod in question was using racial slurs. Granted, the Godot foundation also split ways with them.

    Additionally there was something about an over zealous community manager blocking people over responses that supposedly weren’t all that inflammatory or bad? I’m not super sure there, I’ve only kinda half been paying attention to it











  • However, if you ask me to pick one specific project, I get overwhelmed because I don’t know what’s reasonable.

    I don’t know enough to know if my ideas are achievable, or if I’d just be bashing my head against the wall. I don’t know if they’re laughably simple tasks, multimillion-dollar propositions, or Goldilocks ideas that would be perfect to learn a coding language.

    List out some ideas you’re thinking of. While it may not be obvious to you, someone who is seasoned (me or someone else) might notice at least a general theme or idea to point you in the right direction for where you should go and what you should learn, regardless of if the projects are reasonable.

    Note - Most projects take teams to realize, so if your ideas are too large, they might not generally be feasible alone.






  • Running arr services on a proxmox cluster to download to a device on the same network. I don’t think there would be any problems but wanted to see what changes need to be done.

    I’m essentially doing this with my set up. I have a box running proxmox and a separate networked nas device. There aren’t really any changes, per se, other than pointing the *arr installs at the correct mounts. One thing to make note of, i would make sure that your download, processing, and final locations are all within the same mount point, so that you can take advantage of atomic moves.


  • You’re talking about XMPP, and it was google with google chat that people refer to with it.

    That said, there’s a lot of details that story people throw around about google killing it that lacks some details. Specifically that the premier service that used and developed the standard, jabber, was acquired by cisco like 8 years before google supposedly killed it, which i would argue affected it far harder than google chat did.

    It’s also lacking a lot of modern features that were becoming staple around the time that it was killed; i.e. QoS, assured delivery, read receipts, and a few other things. I still don’t think the protocol supports them.

    Also, the protocol still exists and is used. It’s used by microsoft in skype for business, it’s also the IM protocol for lots of gaming platforms like origin, playstation, the switch (for its push notifications for their online service), League of legends, fortnite, and others. It’s still a reasonably popular standard when it comes to chat programs, though none of them that i’m aware of use the actual federation piece of it to talk to each other.

    While the tactic alluded to does exist (“embrace, extend, extinguish”), i’ve never been necessarily convinced that google “kiled” xmpp, as its been around a long time and continues to be for various reasons. Even with google chat, it was never a ‘front end’ thing many users even thought about, because it’s back end frameworks tech, and it continues to be so in lots of different places today. I’m reasonably sure that the people who get upset about it and proclaim google killed it are basically just upset that it didn’t become the defacto chat standard today, which i would argue almost nothing is the defacto standard anyways, unless you count discord which kinda came out of nowhere like a whirlwind and took over the chat space and has nothing to do with any XMPP drama.

    Ultimately, its up to you (whoever is reading this) to look into the facts of the matter and decide for yourself if that’s what really happened, but keep in mind, the people who usually repeat the anecdote about how google killed it have an agenda to push. I’m personally skeptical, because there’s reasons for google to have dropped it (see mentioned limitations above), and even back then, it wasn’t that outrageously popular. In fact, i would argue its more widely used today than it was back then, but i have no hard numbers on that.