websocket VS gomodest-template

What I can say is that if you will use Gorilla Websocket (https://github.com/gorilla/websocket) (it's archived now unfortunately, but still super robust) - then you can go to sth like 15-20kb per connection - see https://github.com/FZambia/go_websocket_memory - to achieve this you need to reduce read buffer size, reuse write buffers, use goroutine after hijacking connection (following chat example in Gorilla WebSocket repo).

No Bugs? https://github.com/gorilla/websocket/issues Even if that were true at the time of stoping development, "No bugs" is something that can never be said for any software. I really wish this community stopped recomending to use abandoned libraries if only for the potential Security issues. A not maintained Library is a very lucrative target for vulnerability hunting.

The Gorilla WebSocket License says:

We'll be using WebSocket library: "github.com/gorilla/websocket" ❣️

package github.com/gorilla/websocket is not a main package

As for Websockets, (https://github.com/gorilla/websocket) it uses ws.NextReader() to handle heavy loads of connections.

I'm looking to build a game server that uses web sockets to communicate with clients, I've looked into some of the libraries and the main ones seem to be gorilla websockets and melody.

If this is what your import looks like "github.com/gorilla/websocket" that's wrong it should be just "github.com/gorilla/websocket"

Its too early for a roadmap. I have tried different approaches and rejected them: https://github.com/adnaan/gomodest-template, https://github.com/goliveview/examples. I want the library to be have a great UX, good for moderately complex apps while building tech which is maintainable(no new rendering layer engine). I could use some help brainstorming the approaches though.

Oh wow someone finally went ahead with the server rendered js in Go ! Looks great. I have been experimenting various ways to build web apps in Go: https://github.com/adnaan/gomodest-template. I have landed on pursuing one approach more deeply: server rendered html templates over websockets. Don’t have a lot of code right now but here are some examples: https://github.com/goliveview/examples.

Since early this year, I started working on https://gomodest-template.fly.dev/samples, https://github.com/adnaan/gomodest-template to experiment with various ways to build user interfaces in Go, html and a bit of javascript. Now, I have taken all the learnings from gomodest-template and started working on https://github.com/goliveview/ . Its super early work.

So I have been exploring server side rendered Go web apps using only sprinkles & spots of javascript: source: gomodest-template , live demo .

I have built an app template which uses Go html/template package to render html on the server. The app is enhanced using sprinkles of javascript(stimulusjs, svelte single file components) on the client, wherever needed.

1. template: https://github.com/adnaan/gomodest-template

gomodest-template