Electronic-Interchange-Github-Resources VS zig

I have a couple of repos you can take a look that are specific to the 834. Heres one with an example 834: https://github.com/michaelachrisco/sublime-834-syntax

Ive done a ton of 837s. Sadly I dont work in EDI anymore, but the software I used in multiple jobs is documented here: https://github.com/michaelachrisco/Electronic-Interchange-Github-Resources

I compiled a resource a while back: https://github.com/michaelachrisco/Electronic-Interchange-Github-Resources as it was exceptionally hard to find tools at one point. If anyone has any additions, a PR is appreciated.

I maintain a informational repo for edi resources https://github.com/michaelachrisco/Electronic-Interchange-Github-Resources

Take a look: Electronic-Interchange-Github-Resources Theres a whole lot of tools and libraries at your disposal. A decent programmer or third party could help you out if need be.

If your looking for more tools and setups, I maintain: https://michaelachrisco.github.io/Electronic-Interchange-Github-Resources/ a collection of EDI tools that may help out. Repo is here: https://github.com/michaelachrisco/Electronic-Interchange-Github-Resources

Its all good, I've been trying to compile some resources for a while now, just wanting to see what the community uses to add to the ongoing list: https://github.com/michaelachrisco/Electronic-Interchange-Github-Resources

You may want to contact your clearing house/insurance/whoever wants the file what kind of format they require and get the specifications then build accordingly. I'm not sure how technical you and your team are but if you have a software developer, you should be able to make a solution using some of these libraries/services: https://github.com/michaelachrisco/Electronic-Interchange-Github-Resources

For everything else, take a look at these paid services.

It's "Zig" not "Zag". https://ziglang.org/ Zig is under heavy development, but there's a single page https://ziglang.org/documentation/0.12.0/ that is a reasonably comprehensive source of truth about the current state of the language.

There is an issue proposing this approach: https://github.com/ziglang/zig/issues/4284

https://github.com/ziglang/zig/issues/224

e.g.:

> > When debugging/prototyping, it's useful to comment out a line without having to refactor, e.g.

When writing code in a scripting language, sometimes you need that extra bit of performance (or maybe an async feature from Zig).

NodeJS is by no means a slow runtime, it wouldn’t be so popular if it was. But compared to Bun, it’s slow. Bun was built from the ground up with speed in mind, using both JavascriptCore and Zig. The Bun team spent an enormous amount of time and energy trying to make Bun fast, including lots of profiling, benchmarking, and optimizations.

ntdll.dll!RtlUserThreadStart()

There are valid reasons to use APIs from NTDLL. Where I disagree with zig#1840 is the idea that it is always better to use NTDLL versions of API. Every other software ecosystem uses the standard Win32 APIs and diverging from that without a good reason seems like a good way to have unexpected behavior. One concrete example is most users and programmers expect Windows to redirect some file system paths when running on WOW64. But this is implemented in Kernel32, not ntdll.

https://github.com/ziglang/zig/issues/11894