General Discussion

Suggested Topics

  • 0 Votes
    15 Posts

    @eeeee I totally agree less frameworks , then all stable and better.

  • 0 Votes
    11 Posts

    @oplik0 said in phpBB NodeBB Flarum who is better Forum?:

    @鄭宇佋 A less biased answer would be - they aren't entirely equivalent, and the choice is a combination of specific needs and preferences that IMO can't be generalized to "x is better in general".

    phpBB is the oldest forum, and as such it embodies the older style of forums from before social media made things like tags, real time interactions, feeds etc. popular. However, it is probably the most feature rich of all offerings if you have time and knowledge to set it up.

    Flarum (and I think the Laravel community software too? Never used it :V) is a simpler forum that is tag-based. You can nest tags once in Flarum, but only once and it seems to more encourage a feed approach where your main page is filled with topics sorted in some way and you use tags to go somewhere if you're looking for something specific. This is in contrast to the "classical" structure I mentioned, where you will have subforums/categories that you can infinitely nest and the idea is that the user first goes to the category that will have the topics that will be interesting to them.

    However, NodeBB and Discourse are both somewhere closer to the middle, but on the opposite sides. In both you will find categories and tags, but from what I've seen the emphasis is different - NodeBB is categories that can have tags, Discourse is tags that can have categories 🙂

    Of course, there are a lot of other differences. As mentioned, more modern software is better at doing stuff real-time. Notifications, chats (Discourse and NodeBB have some form of private conversations built in. Flarum and phpBB have extensions that add it), loading new posts without reloads etc.
    AFAIK NodeBB is the only one of these using WebSockets (
    Discourse uses some custom polling based protocol.
    Flarum actually doesn't do much live stuff by default (just kilke phpBB), but it does have notifications that can use officially-supported pusher extension to work.

    One major difference though - phpBB, Flarum and are PHP-based, so you can make them work on generally cheaper shared web hosting, meanwhile Discourse and NodeBB will require a server that can run Ruby or Node respectively - for example a Linux VPS.

    Which one is better depends on what you want then. seems to be most limited in terms of customization, unless there are some undocumented features on that front. So if there are any things you don't like about the way it looks or feels - don't choose it.
    If you like the Flarum tag structure and don't mind it lacking some things (well, it's a beta after all), it seems like the most performant option.
    phpBB? If you are willing to buy/develop some modern theme and spend time to configure it, sure. Otherwise I wouldn't recommend it.
    The decision between NodeBB and Discourse is harder, and while I prefer NodeBB, I'd say it's mostly down to your preferences, specifics of what you want to use the forum for and the preference for technology stack (Node, Express, MongoDB/Redis/Postgres + no major js framework outside of jQuery on front-end for NodeBB vs Ruby on Rails, Postgres + Ember.js on front-end for Discourse).

    Some unfortunately older topics on this (some will have much more recent replies, so might be useful to read them; I tried to include topics from meta-forums of other forum software and user forums based on software in question): (just for context - this forum migrated to NodeBB from Discourse in 2016) monitoring (here there was a migration in the opposite direction in 2018)

    Obviously remember that the answers will be biased essentially everywhere - here, towards NodeBB. On Discourse forums, towards Discourse. On Flarum - towards Flarum. Etc.

    Oh thanks, so much useful information for me as for newbie 🙂

  • 0 Votes
    13 Posts


    Sadly, your solution does not work in my case 😔.
    It's kinda weird indeed - works flawlessly on Chrome, spams errors on Safari.
    I'm really starting to think it's Safari's bug...

  • 0 Votes
    3 Posts

    Thank you for your note, @julian
    I acctually found what I were need.
    Adding an appropriate string to config.json - solved my problem.

    "": { "address": "" }

    Thus websocket will use port 8000 on establishing the connection.
    One of openshift's bottleneck, that held me up.
    Done 🙂

  • io.js

    General Discussion
    0 Votes
    2 Posts

    @Technowix there are performance gains related to the new structures in ES6 (generators, async functions, classes, ect.) There also may be performance gains since they are updating the internal version of V8 to the latest stable version (Node is still on an older version from what I understand).