iup-go VS Centrifugo

For years I had Qt experience in Python and C++. But I found it too heavy to introduce in a Go project. After trying a couple different options (I'm not a web dev) I actually really liked IUP. https://github.com/gen2brain/iup-go

You can check the screenshot from Windows 10 here https://github.com/gen2brain/iup-go/blob/main/examples/sampl.... If you are not using the manifest it will not follow the system appearance and will always look like Windows XP Classic.

I've tried a few different Go gui solutions so far. Coming from a C++/Python Qt background, I wanted to use Qt bindings but found them to be a bit too heavy as a dependency in Go. And I'm not a skilled web dev so some of the other options didn't suit me well enough. But I did actually enjoy using this in a recent project: https://github.com/gen2brain/iup-go

For native controls check https://github.com/gen2brain/iup-go.

That depends on your requirements. I'm currently using IUP for a desktop app (Linux and WIndows). Caveats:

For native UI, you can check https://github.com/gen2brain/iup-go. There are 50+ examples to help you, i.e. show images, buttons, file dialogs, etc.

If I may, https://github.com/gen2brain/iup-go: Cross-platform UI library with native controls.

You can check https://github.com/gen2brain/iup-go. The Cocoa backend is still not finished but it works for basic UI. There is GLCanvas for Linux and Windows.

I recently created a Go binding here https://github.com/gen2brain/iup-go and was amazed how simple API is, thanks to their attribute system. Although they have some controls that are custom, everything else is native. Compared to Qt or wxWidgets, IUP is just a UI toolkit, Qt/wxWidgets is much more than just a UI toolkit.

Hello, I am author of https://github.com/centrifugal/centrifugo. Our users can choose from WebSocket, EventSource, WebTransport (experimental stabilize in the future). WebRTC is out of scope as the main purpose is central server based real-time json/binary messaging, and WebRTC makes things much more complex since it shines for peer-to-peer and rich media communications.

What I'd like to add is that Centrifugo also supports HTTP-streaming – not mentioned by the OP – but this is a transport which has advantages over Eventsource - like possibility to send POST body on initial request from web browser (with SSE you can not), it supports binary, and with Readable Streams browser API it's widely supported by modern browsers.

Another thing I'd like to mention about Centrifugo - it supports bidirectional WebSocket fallbacks with EventSource and HTTP-streaming, and does this without sticky sessions requirement. I guess nobody else have this at this point. See https://centrifugal.dev/blog/2022/07/19/centrifugo-v4-releas.... Which solves one more practical concern. Sticky sessions is an optimization in Centrifugo case, not a requirement.

If you are interested in topic, we also have a post about WebSocket scalability - https://centrifugal.dev/blog/2020/11/12/scaling-websocket - it covers some design decisions made in Centrifugo.

Check out https://github.com/centrifugal/centrifugo - it was initially designed to be a standalone language-agnostic real-time messaging server. So it may be used with Django without radical change in the existing application and using ASGI. It can also provide a much better performance if you care about it.

https://github.com/centrifugal/centrifugo

It's a complete solution, including server, admin panel and client library.

We're an European company and use OVH, Hetzner and others.

Hello! Theoretically you can take a look at https://github.com/centrifugal/centrifugo - which is a standalone self-hosted real-time messaging server. It does not have native support for Laravel and not compatible with Pusher protocol, though integrating with any backend system, including Laravel: see the blog post https://centrifugal.dev/blog/2021/12/14/laravel-multi-room-chat-tutorial, also has some helper packages:

Hello, it's also possible to design an app in a way that its core will be built with Python, but WebSocket part delegated to something external and efficient like https://github.com/centrifugal/centrifugo – the benefit of the approach is that application business logic is completely decoupled from the real-time transport layer. This may lead to a scalable design with graceful degradation. I think this is especially useful when you already have backend built with Django and need to handle millions of concurrent connections.

Centrifugo https://centrifugal.dev/ https://github.com/centrifugal/centrifugo