pjproject VS pixie

Hello, I'm in the process of developing a multiplayer FPS game and recently delved into ICE connectivity (STUN/TURN). Currently, my setup involves a custom matchmaking server in C++, with UDP port handling on the client side through UPnP or a fallback custom relay server. While the current approach works well, I'm exploring options to simplify the project by incorporating existing technologies. I've come across Libjuice and Libpjsip for NAT traversal. Libjuice offers a nice and simple API, but it supports only one person. Hence, I'm considering Libpjsip. I came across their ICE demo script at https://github.com/pjsip/pjproject/blob/master/pjsip-apps/src/samples/icedemo.c and I'm curious about its performance, particularly the pj_ice_strans_sendto2 function. I'm keen to understand how it compares to my current implementation with Berkeley Sockets and whether Libpjsip is a suitable choice for multiplayer P2P games. Any insights or assistance would be highly appreciated. Thanks!

Things improved a lot thanks to the adoption of the pjsip stack.

When I look at stuff like pjsip, I get the impression, it would be huge amount of work. Am I mistaken?

The first issue I'm facing is I can't find lib folder which is mentioned in Using pjproject libraries for your own application heading in the above-mentioned link. I download the source code from this link.

For client and server, I'm only really familiar with https://www.pjsip.org/. It also comes with a bunch of code for doing phone calls, which really most SIP Stacks were built around. But those parts can just not be used.

PJSIP (https://github.com/pjsip/pjproject) is used as SIP framework

We have written pixie: https://github.com/treeform/pixie . Pixie is a 2D graphics library similar to Cairo and Skia written entirely in Nim. Which I think is a big accomplishment. It even has python bindings: https://pypi.org/project/pixie-python/

I made it because I really like pixie/boxy/windy combo, but there is no gamepad support built-in.

With Nim, you can continuously optimize and improve the hot spots in your code. For example, in the Pixie graphics library, path filling started with floating point code, switched to floating point SIMD, then to 16-bit integer SIMD. Finally, this SIMD was written for both x86 and ARM.

The author Fidget actually has a number of other great libraries that are part of the rendering stack. Notably, Pixie for text and shape rendering in 2D, Boxy for rendering textures to the GPU via opengl, and then Windy for an OS window context and user events, and a number of other libraries related to 3D rendering.

Perhaps not the "best" source code I've ever read, but libVF.io had some beautiful code for what's generally gnarly system-glue code. The iommu setup code is a good example and inspires me to think that system-glue code doesn't need to be gross or impenetrable: https://github.com/Arc-Compute/LibVF.IO/blob/master/src/libv...

Another one I've appreciated reading (and learned more about 2d graphics from) is Pixie, a 2d graphics library written in Nim. Here's the implementation of a fair subset of SVG paths: https://github.com/treeform/pixie/blob/master/src/pixie/path...

And one last one for basic algorithms: https://github.com/nim-lang/Nim/blob/version-1-6/lib/pure/al...

Of course Knuth's original code is still some of the best classic code. K&R's original C book is a classic.

I recently helped work on a new open source JPEG decoder in Nim. (Over here on GitHub: https://github.com/treeform/pixie/blob/master/src/pixie/file...)

This video was extremely helpful to understand the "why" of all the things the spec was trying to explain. It made a huge difference in us being able to get things working.

We talk a bit about JPEG and actually writing our decoder in Nim here: https://www.youtube.com/watch?v=vYwD7OynFcg

Overall, our concluding opinion is that JPEG has some extremely cool and really smart ideas for how to compress images but the binary file format itself has some very painful things in it (progressive and restart markers as a couple examples).

I am working on OpenStreetMap renderer in Nim - see https://github.com/severak/lunarender3/ (but work somewhat stalled)

I needed some language which is:

- compiled to binaries

- and really fast

- has needed libraries (HTTP server, protocol buffers, sqlite and image generation)

- it's easy to set up

It was nice experience and Nim simply worked for my needs. People on Nim forum were nice and helped me when I ran into problems. It has nice and usable built-in library and I was really impressed by graphic library pixie - https://github.com/treeform/pixie

I would use Nim again when I when I will see this application is suited for it (e.g. some command line apps).

> but not so small that there are no useful libraries written...

Says the person responsible for a ton of really useful, well-done Nim libraries, such as this amazing Cairo/Skia-like library: https://github.com/treeform/pixie#readme

Thank you for all the things you've made for Nim!

A 2d graphics library like Nim’s pixie