27

A little headpat for those who have suffered so much in making wrapper code for managed languages for native libraries

Because I know how painful it is to make one

Comments
  • 1
    To this day I admire people’s motivation to work with native codebases for a living.
  • 4
    @Earu it's fun and challenging. Once you do it for 10 years everything else is easy.

    The trick is to build a toolbox that will allow you to quickly build out a framework to extend from.

    Another benefit, you never have to read documentation... Because it doesn't exist!
  • 0
    I guess it can be a challenge or a nightmare depending on your perspective, personally I like to do challenging times things during my free time. At work I’d rather find the solution to a problem and get it done asap lol
  • 2
    I am in great favor of the new painpeko tag.
  • 0
  • 0
    @Earu eh? What's wrong with some C++?
  • 0
    That girl reminds me of Klee from Genshin Impact.
  • 0
    @-ANGRY-STUDENT- it's Lumine from genshin impact...
  • 0
    @iiii I knew I would find you here
  • 0
    Haven't dealt with those, just here foe the headpats. thanks.
  • 1
    @Ranchonyx pain nanora :3
  • 1
    Thanks, I had to make a wrapper for a go cli tool and it it fucking sucked
  • 0
    @Awlex ouch, been down that road before. Making CLI wrappers are painful (language the CLI is written in doesn't matter). So many edge cases. So brittle.
  • 1
    @hjk101 It natters in this case, because I had to compile it myself, because my coworker was still finalizing it.

    And simply put, I'm appalled by go and it's dependency "management"
  • 1
    @Awlex what the fuck. If it's a coworkers thing it should use IPC not CLI to communicate. You should have just gotten the binary. At least it should have been two simple go commands to build it. You don't need extra tooling. Sounds to me like things going on because of a serious lack of knowledge.

    Go has it's own way of doing things but even though it has it's shortcomings would not say it is appalling.
  • 1
    @hjk101 Pretty much. It's an abstraction over starting tasks in local docker containers or aws fargate instances "Without having to care about which backend you choose". I think the very idea that those tasks need to be wrapped/extracted into cli tools is him bring on gnu cool aid.
Add Comment