• 2 Posts
  • 69 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.








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


  • yeah, its hard to predict what will happen to it, especially after gabe steps down or dies, but depending on how much of the company is broadly owned by employees vs individuals, it can help to shield it from bad decisions. Unfortunately, we don’t know the exact numbers. If gabe + mike own 51+% then it could potentially lead to overriding employee will in a bad decision for money (either through their actions or through inheritance like you say). Or the employees could just collectively make a bad decision too.





  • Employee Number 427’s job was simple: he sat at his desk in room 427, and he pushed buttons on a keyboard. Orders came to him through a monitor on his desk, telling him what buttons to push, how long to push them, and in what order. This is what Employee 427 did every day of every month and every year, and although others might have considered it soul-rending, Stanley relished every moment that the orders came in, as though he had been made exactly for this job.