AirSkyBoat VS gleam

https://github.com/AirSkyBoat/AirSkyBoat.

https://github.com/AirSkyBoat/AirSkyBoat/issues/2284 https://github.com/AirSkyBoat/AirSkyBoat/issues/2299

An accurate recreation of the mmorpg final fantasy 11 when it first released - emulation software (https://github.com/AirSkyBoat/AirSkyBoat) and the upcoming private server horizonxi.

We would like to welcome you to our new server, Tabula Rasa! Using https://github.com/AirSkyBoat/AirSkyBoat and https://github.com/LandSandBoat/server as a base, we have begun a new 75 cap private server project. Our project is dedicated to reproducing Final Fantasy XI as it was prior to the level cap increases with a few minor additional comforts.

I think we were either not clear enough or this was lost in translation, but all of our current developers are also apart of AirSkyBoat which is an open-source era module repository for the LandSandBoat project. You can find more information here: https://github.com/AirSkyBoat/AirSkyBoat, so our methodology whenever we want to put a new piece of content into HorizonXI we will first make an era module for it on AirSkyBoat. For instance, if we want besieged for HorizonXI we first would would develop an era module for AirSkyBoat then add any adjustments we need to do for HorizonXI on a separate repository. We want to help the era community whilst also just allowing players to experience things like it is a new game again.

I haven't had time to really try to write anything in it, but https://gleam.run/ looks really good too. Like Elm for backend + frontend!

Want a friendly language for building safe systems at scale? Gleam is here for you. It features modern and familiar syntax, that's reliable and scalable. Gleam runs on an Erlang virtual machine, and can run plenty of concurrent tasks. It comes with a compiler, build tool, formatter, editor integrations, and package manager all built in so you can get started right away. Congrats to the team on shipping your first major version 🙌.

While I love Clojure, I have to agree about tooling. I recently started using Gleam* and was impressed at how easy it was to get up and running with the CLI tool. I think this is an important part of getting people to adopt a language.

* https://gleam.run/

If you use languages that compile to WASM (such as Gleam https://gleam.run), and can also run Postgres via WASM, then it opens very interesting offline scenarios with codebases which are similar on both the client and the server, for instance.

Recently, Gleam has gained more popularity, and a lot of developers (including me) are learning it. At the time of this writing, it has exceeded 14k stars on GitHub; it grew really fast for the last month.

Oh, strange that github had a date of 2016 on this one: https://github.com/gleam-lang/gleam/issues/2

I was just going by that, though I do remember checking out gleam 5 years ago or so.

Re: macros, I really do think they’re a big deal and all the other newer languages I’ve used, such as Rust have some kind of macros or powerful meta programming features.

For older languages, a few, like Ruby have enough meta programmability to make nice DSLs, but many others don’t. Given the choice, I’d much rather have Elixir/Clojure style macros than other meta-programming facilities I’ve seen so far.

I had been only following this language with some interest, I guess this was born in gitlab not sure if the creator(s) still work there. This is what I'd have wanted golang to be (albeit with GC when you do not have clear lifetimes).

But how would you differentiate yourself from https://gleam.run which can leverage the OTP, I'd be more interested if we can adapt Gleam to graalvm isolates so we can leverage the JVM ecosystem.