liwords VS connect-es

Check out https://woogles.io (disclaimer I am a cofounder). AGPLV3 platform with world class bots, puzzles, a free analyzer, clubs/tournaments, and more to come. You can see the source code at https://github.com/woogles-io/liwords. We recently hit 5M games played and have hosted a few major tournaments.

A small team of us work on a project https://github.com/domino14/liwords - this is an online crossword-board-game playing website. We have around 6000 MAU, are fully free and open-source, and need a lot of coding help!

We built woogles.io (a crossword board game playing site with almost 10K MAU) in Go. See https://github.com/domino14/liwords

https://github.com/domino14/liwords - warning it’s not that well-developed but it’s ok

A small team and I made https://woogles.io - we were inspired by lichess to make a site to play crossword board games during the pandemic (like Scrabble, Words with Friends, etc).

We did raise money on Kickstarter - 25K but are purely donations-driven and open source (AGPL3) Most months we just get enough to cover the cost of running the servers. We have around 6000 monthly active users, have hosted several big worldwide championships, have puzzles, and just earlier today released a board editor / broadcast mode for annotating real life games in real time. We also have a top notch bot AI and WASM-based analyzer.

Our stack is Go, Typescript + React, with NATS/PGSQL on the backend.

woogles.io

The people behind those websites and apps have no clue this software exists. The exception is woogles.io because it is associated with the Macondo AI. /u/14domino is the brain behind both of those things

https://woogles.io raised $25K on Kickstarter and built a more beautiful site. Come join us (we’re still taking donations :)

- Playing online: there is woogles.io which I personally would recommend; it's made by players for players and is free to use. Among the features are: play against humans, play against strong bots, tournaments, feedback on your moves after the game, availability of different languages and game variants. Other options are: playscrab.com (also made by players for players); isc.ro (the Internet Scrabble Club); the app Scrabble Go and, if you don't mind playing with slightly altered game rules, Wordfeud, which comes along with a large online league (not technically affiliated with the app itself).

> However, it's important to note that browser support wasn't a primary focus in gRPC's design. This oversight necessitates an additional component, grpc-web, for browser accessibility. Furthermore, external services often have specific needs like caching and load balancing, which are not directly catered to by gRPC. Adopting gRPC for external services might require bespoke solutions to support these features.

The article should mention the Connect protocol for web-based Protobuf messaging:

https://connectrpc.com/

We can solve this with a service! Now there are many ways I could have started, but I decided to test out gRPC along the way. This was a mistake. I hoped for the best, but gRPC ended up not being a good choice for the web client. Why? you ask. The gRPC protocol works with all the bells and whistles of http when used server to server, but web clients are not as great. The Javascript client is dependent on http 2.0, and it requires a proxy like Envoy to work with a browser. What's more, I didn't love the structure of the generated web client. So through the process of working on this 'local first stack' I actually got sucked in to a big rabbit hole in making the rpc system work. I ended up going with Connect which is a tool that can create a service from a protobuf service definition, that also talks a simple http 1.1 protocol. What ultimately sold me on this solution as the best is that it also came with a very nice to use web client generation, and even plugs in to my favorite react http helper useQuery.

Our stack at Escape is written in multiple languages because each team has specific needs. We use TypeScript for its vibrant ecosystem, Python for cybersecurity research and Go for performance-sensitive tasks. To orchestrate cross-language task orchestration, we first developed a simple request-response protocol over HTTP, but it wasn't sustainable as the Escape codebase grew rapidly. We evaluated several technologies to replace our homegrown protocol, and two emerged as the most promising options: Connect and Temporal. The title gives it away, but the reason is far from obvious

protobuf messages we’ll configure (@bufbuild/connect-es)

try https://github.com/bufbuild/connect-web

As for better gRPC-web, you might want to look into connect-web https://github.com/bufbuild/connect-web

They already have! Connect (https://github.com/bufbuild/connect-web) is what you're looking for, as it's grpc-web compatible.

Ye, fwiw there is an example code size comparison here:

https://github.com/bufbuild/connect-web/blob/main/packages/c...

I'm sure someone will chime in on the implementation details, but hopefully others can give it a try with their projects!