nimforum VS RFCs

> Only huge projects can afford to have multiple Discords, Telegrams, IRCs, Wikis

There's one option available to small projects and actually you already named it yourself:

> relay bots.

Take for example Nim community. It's not huge by any margin, but we have fairly active forum[0], occasionally active Telegram channel and most of activity is on Discord, IRC and Matrix. I've grouped these three because they're almost seamlessly connected with relay bots into one platform. You can join one of several bridged platforms[1] and talk to everyone on Discord, Gitter, Matrix, etc. with quotes, pings and attachments working as you'd expect them to.

It is certainly an extra burden to moderate and manage all of this, but now you can atleast have an IRC archive[2] that's indexable and searchable [3].

On the other hand, having Discord as your *only* place for discussions is plain stupid (read: foolish). Because I know several people, including myself some years ago, that just 'nope out' from using a project when they see that the only place to get support is a Discord channel.

[0] - https://forum.nim-lang.org/

[1] - https://nim-lang.org/community.html

[2] - https://irclogs.nim-lang.org/30-05-2012.html

[3] - https://duckduckgo.com/?t=ffab&q=site%3Airclogs.nim-lang.org...

To be honest, I haven't found the community size to be an issue. The Nim forum[0] has a vibrant community, and is the place I go to for help, and the response is usually quick and on point. The language is also evolving in a careful manner, with Araq at the helm I think it's going to be even better in the long term.

As for the ecosystem, yes, it's not as big as Python or Rust, but surprisingly the standard library has most of what people need. I rarely look for 3rd party packages to do something.

That being said, I acknowledge that Nim is on the lesser known languages of the spectrum, but that doesn't take away from its merits as a very promising language that does what it's supposed to do very well.

[0] https://forum.nim-lang.org

If the video example does not work, you can use the examples projects in the nim SDL repository. When ex101_init.nim works, there is no reason the video example does not work. If you have further issues, do not hesitate to share a minimal working example with your detailed configuration (Nim compiler version, command line you used, file directory, libraries installed) on the forum.nim-lang.org

It might be worth posting this on the official nim forum (https://forum.nim-lang.org/) to cast a wider net.

Obviously forums aren't as popular as they used to be, so this topic might not be of interest to many. For folks that want to run a forum, they'd most certainly go with Discourse (Ruby), Flarum (PHP), Xenforo (PHP), NodeBB (Javascript), Nimforum (Nim) and maybe Casnode (Go)

https://forum.nim-lang.org/ doesn't let me post.

NimForum - https://github.com/nim-lang/nimforum

You sound like you are in just the right demographic to love Nim...The Forum [1] is a good place to get support.

https://forum.nim-lang.org/

"embedded" can mean a few different things so that's a bit confusing for me, but if the intent was "show me places sqlite is used as a database backend for user-facing web software", the Nim forum (https://github.com/nim-lang/nimforum) uses sqlite as its database backend.

I love NimForum, like a simplified discourse and super light on resources. Example

compiler support for object construction shorthand

Well, maybe not writing. Occasionally low-level C libraries - especially those that deal with keyboard input - decide to provide identifiers differing only in case... There's a WIP RFC for providing a way to deal with identifiers that need to be verbatium by surrounding them with backticks, though.

https://github.com/nim-lang/RFCs/issues/477

Following The Roadmap 2023 for community building , you could join us in the matrix space where we discuss how to build a community. We appreciate doable suggestions and helps, such as improving the workflow, implementing the roadmap, suggesting doable tasks, reviewing code from contributors. United we stand. We shall work together to make the community thrive.