discord-irc VS zig

How does this compare to https://github.com/reactiflux/discord-irc ?

You can link your irc channels to Discord so no one gets left behind or if some old regular who has been idle for 15 years becomes active again.

Maybe discord-irc

But you can migrate. Have a bot running bridging both apps and then phase the old one slowly out. Like

https://github.com/reactiflux/discord-irc

https://t2bot.io/discord/

That way you are not stuck in an ecosystem. Sure some ppl will always be unhappy and looking up content in the old system is subpar but thats the nature of the game.

Yup, definitely seems possible from a quick google search. LiberaChat seems to just be IRC. Looking for a Discord to IRC bridge, I found this which appears to operate in both directions.

if you want to use your discord client, you can probably set up a bridge. Check out: https://github.com/reactiflux/discord-irc

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