nakama VS Tailwind CSS

nakama: https://github.com/heroiclabs/nakama

To add more detail on the recent work on the ZHeap storage engine. We (Heroic Labs) sponsored work for the Cybertec team to bring it up to date with latest improvements and changes with Postgres' pluggable storage engine:

you can do that, but for what platform? html5? windows? android?, the most easiest way is use firestore a service from firebase (offer a free tier), it is the easiest way not the better, other way is use a service like nakama that is more professional and something in the middle can be mmm pocketbase or supabase.

I recommend the backend solution called Nakama since you’re using Godot: https://heroiclabs.com/

You could create all this yourself, or you can use existing solutions which handle all this (and much more I didn't mention). One that I'm aware of that works with Godot is Nakama. They have a paid hosting option, or you can host the application yourself.

I read using nakama server for this is convinient. https://heroiclabs.com/

Does anyone have recommendations on what to use? I've done a bit of research and found https://heroiclabs.com/. It's a bit unclear to me if it actually supports server side state because it talks about 'hosts' a bit, but I think it does...and it seems like you can host it yourself to avoid the $600 a MONTH! pricetag. But any other recommendations? Has anyone used heroic before?

You might be interested in Nakama server from https://heroiclabs.com/

Depending on how much effort you want to put in to this, you might consider something like Nakama: https://github.com/heroiclabs/nakama

There have been mentions of Normcore, Fish-Net, and Nakama as well.

Lastly, Tailwind CSS is a utility-first CSS framework packed with classes like flex, pt-4, text-center, and rotate-90 that can be composed to build any design, directly in your markup.

Tailwind CSS

Sidekiq is already configured along with assets, tailwindsCSS.

Finally, for our front end, we’re going to be pairing Next.js with the great combination of TailwindCSS and shadcn/ui so we can focus on building the functionality of the app and let them handle making it look awesome!

You can use any frontend framework you want — react-based tooling, however, has a natural advantage as it models everything as a function of state, which can map 1:1 with the concept in Burr. In the demo app we use react, react-query, and tailwind, but we’ll be skipping over this largely (it is not central to the purpose of the post).

Tailwind CSS: A utility-first CSS framework for rapidly building custom designs.

First, you need to make sure that you have a working Tailwind CSS project…

Tailwind CSS

With better CSS approaches like TailwindCSS and Vanilla Extract (which we're heavily using) it's much easier to maintain the UI and make sure it doesn't change unexpectedly. No more conflicting CSS classes, much less CSS specificity issues and much less CSS code in general.