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

help-circle
  • 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.

















  • 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.