Discourse VS ruby

> Tell me another platform that is free, has realtime chat, voice and video, has stable service, allows sharing images and other media, with good ownership management... and is open source.

Mattermost: https://mattermost.com/

Rocket.Chat: https://www.rocket.chat/

Nextcloud Talk: https://nextcloud.com/talk/

Self hosting and some assembly required. I've run all of them on cheap VPSes to explore a Slack/Discord replacement, neither was mindblowing but all of them seemed okay (Nextcloud's offering was rather barebones, though).

Audio and video support varies because getting those right is challenging, at best you'd just integrate with something like Jitsi, that one's actually pretty good for meetings and such: https://jitsi.org/ and has a cloud version too: https://meet.jit.si/ (yet people still go for Zoom and it's odd UI/UX choices)

I actually rather liked forums back in the day, but I guess nobody will be setting up that many phpBB instances in the current year, though projects like Discourse also seem promising: https://www.discourse.org/

I don't think many people at all will be leaving Discord, due to how entrenched the platform is (network effect): if you want people to help you with what you're working on, you go where they are, not vice versa.

Discourse is also open source https://github.com/discourse/discourse

I disagree. Lots of communities, e.g. Julia or Stan, use https://www.discourse.org. Discourse is GPL2 and emulates old Internet forums.

Why isn't Discourse being listed here for forum software? It's open source and designed for modern communities. https://www.discourse.org/

Discourse is open source: https://github.com/discourse/discourse

You could hook it up to a mail provider and can host it yourself for less if you wanted.

I was reading mastodon.social's privacy policy, and noticed that the link at the bottom to Discourse's privacy policy links to Discourse's Github. I'm surprised because I thought it would be the privacy policy on discourse.org.

Yep. Any platform run by someone else can kick you off for any reason, and time.

You should consider looking into running discourse, which is a modernized forum software: https://github.com/discourse/discourse

Nice examples of what it looks like:

https://discourse.nixos.org/

https://forum.level1techs.com/

As a bonus, the content and community will be accessible to search engines, so it’s easy to find answers to problems that gave been already been addressed.

In general, consider combining the two, where discourse is the anchor of the community that can’t be yanked out from under you, while discord is the one that sells the data from your players in exchange for free voice and text chat.

It’s also possible to enable logging in with discord credentials https://meta.discourse.org/t/configure-discord-login-for-dis...

As well as pushing content from discord to discourse so it’s not hidden and losable: https://blog.discourse.org/2021/05/discord-and-discourse-bet...

So, I'm asking myself if you would be interested in joining a good old-fashioned forum (probably using discourse as software) in order to communicate with other gifted people around the globe. And please add any ideas you might have for a platform like this.

To create a new Rails app, you should have Ruby and Rails installed on your machine. You can find how to install Ruby on your local machine using the Ruby docs. You can install Rails by running the following command:

Ruby testing with RSpec

Not parent poster and do not have production YJIT experience. =)

My guess is that you would monitor `RubyVM::YJIT.runtime_stats[:code_region_size]` and/or `RubyVM::YJIT.runtime_stats[:code_gc_count]` so that you can get a feel for a reasonable value for your application, as well as know whether or not the "code GC" is running frequently.

https://github.com/ruby/ruby/blob/master/doc/yjit/yjit.md#pe...

Link to the commit

Part of the major userbase pull in GitHub revolves around hosting a considerable number of popular projects including Angular, React, Kubernetes, cpython, Ruby, tensorflow, and well even the software that powers this site Forem.

Hold option and click on the “collapse file” button in the Files view of a commit or pull request, and it will collapse all the files.

Select text in a comment, issue, or pull request description and press r—the selected text (including markdown formatting) will get pre-populated as a markdown block quote reply in the next comment box.

Add .patch or .diff to any pull request URL if you want to see a plain-text diff of the pull request (e.g. maybe you want to quickly `curl ... | git apply -` an unmerged pull request into a local copy of the repo without trying to add and fetch the git remote that the pull request is from).

There are lots of keyboard shortcuts. For example, / to jump to the file finder.

Not so much a secret but more like a hiding in plain sight: when looking at a commit GitHub will show you the earliest and latest tag (i.e. release) that includes the commit. For example, this commit[1] first appeared in v3_2_0_preview3.

[1]: https://github.com/ruby/ruby/commit/892f350a7db4d2cc99c5061d...

The title is misleading, just like other commenters mentioned. Just check how much indirection "rb_iv_get()" has to make (at the end, it will call [1], which isn't "a light" call). Now, check generated JIT code (in a blog post) for the same action where JIT knows how to shave off unnecessary indirection.

We are comparing apples and oranges here.

[1] https://github.com/ruby/ruby/blob/b635a66e957e4dd3fed83ef1d7...

I'm not sure why, but all the source values are listed here: https://github.com/ruby/ruby/blob/1cc700907d3ad3368272488a6f...

Maybe someone knowledgeable in the underpinnings of Ruby will explain why "class variable" was not hyphenated.