Which is better NodeBB or Discourse?
-
@julian said in Which is better NodeBB or Discourse?:
Thanks for the kind words, we strive to keep NodeBB minimal and fast, and I feel we're keeping up with trends. Of course, what's in style always seems to pass too quickly
With regards to the composer resize, there's no particular reason it has to be limited to the resizer button, I'll look into it
This looks to be implemented. Thank you very much @julian !
I will suggest that the icon/resizer button needs to re-considered along following lines:
- be gone or redesigned.
- and/or move position to centre.
I"m going to provide you with a mock-up or my own version of the icon ok!
Here it is
or
- weight the top line if the composer differently to suggest it's draggable.
For example:
OFF state
ON state
note: I think my colours are mis-match to the persona colour scheme, need to check that out!
-
The reason the resizer is at the left is because it is out of the way. If it were at the center, then it draws too much visual interest, for something that most people don't touch. That's the only UX rationale against it being center...
-
@julian said in Which is better NodeBB or Discourse?:
The reason the resizer is at the left is because it is out of the way. If it were at the center, then it draws too much visual interest, for something that most people don't touch. That's the only UX rationale against it being center...
Now that the entire top perimeter line is actively draggable (thanks once again!) it copperplates such reasoning and positional choices, for now...
-
If I was to be honest, Id say I prefer nodeBB over Discourse. Why? Many many things. Just to name a few::
- well-thought UI/UX, much more intuitive than D,
- simpler to install/manage,
- without stupid requirements (like mail-service),
- nice & supportive community
And many more.
-
@macfan said in Which is better NodeBB or Discourse?:
If I was to be honest, Id say I prefer nodeBB over Discourse. Why? Many many things. Just to name a few::
- well-thought UI/UX, much more intuitive than D,
- simpler to install/manage,
- without stupid requirements (like mail-service),
- nice & supportive community
And many more.
Yeah, so easy to manage, scales so well, support is so good.
-
I started working with Discourse and nodebb about the same time and I have seen a clear difference in how both platforms have matured, and as well as missing out.
Discourse went from Jeff's Forum Software to a real product for others. In making this change, they have built IMO far better setup, worked with cloud providers to have one-click options, forked and brought in-house popular plugins to be maintained, broke out of the 'how i want it' to 'you want it, we will build it'. Speed is acceptable. Styling feels limited. Mobile is positive.
NodeBB still has all the great things that caught my attention in 2014, but it STILL suffers from the same problems I had then. Out of date documentation. Documentation migration. Limited integration with cloud providers. High profile Plugins Abandoned. I love the speed. The mobile implementation is incredible. But I find myself having the same frustrations I had nearly FIVE YEARS ago.
While Discourse isn't perfect, they have built and matured as a platform, in both polish and reliability. When I get the 'New Version' for Discourse, I am never scared to click that button. I can't say the same about NodeBB. Nodebb still feels like most other open source software, exciting and interesting, but not reliable enough to make me jump in.
Another good comparison in maturity would be Ghost. I started using Ghost and NodeBB at the same time. Polish, feature additions and ease of deployment have all been things you can easily see that Ghost has improved over time. I don't see that same platform maturity with Nodebb.
-
There is lot of issue in @Nodebb-org is also not working well on Chrome own like nodebb itself.
-
-
@shinyidol said in Which is better NodeBB or Discourse?:
While Discourse isn't perfect, they have built and matured as a platform, in both polish and reliability. When I get the 'New Version' for Discourse, I am never scared to click that button. I can't say the same about NodeBB. Nodebb still feels like most other open source software, exciting and interesting, but not reliable enough to make me jump in.
Another good comparison in maturity would be Ghost. I started using Ghost and NodeBB at the same time. Polish, feature additions and ease of deployment have all been things you can easily see that Ghost has improved over time. I don't see that same platform maturity with Nodebb.Not using Ghost so will say nothing, but - for Discourse part - its all way round. Discourse matured over time? Must be kidding! If they wanted to be treated like mature product they wouldn't have implemented three mail providers only, but also all the other mail providers like gmail.....
And per support: Discourse had just banned me because, lo and behold, I voiced my concerns. Oh yea, just for doing so.
So no, Discourse is by no means mature. Whereas NodeBB is.
-
for Discourse part - its all way round. Discourse matured over time? Must be kidding! If they wanted to be treated like mature product they wouldn't have implemented three mail providers only, but also all the other mail providers like gmail.....
In terms of features added, taking control of plugins to build a stable environment AND listening to what people want, yes Discourse has matured. Jeff is very opinionated and can be difficult to work with. I got in an argument with him in 2014 over features we would want if we were to deploy Discourse and he said those features aren't important and would never be part of the platform. Two years later, all of those requests are part of mainline because there was a demand from customers to make that part of the software.
Sounds like you feel into the trap of Jeff and got burned. Don't be mad, you aren't alone.
I still stand 100% behind that Discourse has matured. Their setup process is cleaner and more efficient. Their dependency on featured plugins is very low. NodeBB falls far behind on both of those and really hasn't gotten any better in five years.
-
@shinyidol said in Which is better NodeBB or Discourse?:
Jeff is very opinionated and can be difficult to work with.
This alone is a pretty big factor. I've not used Discourse as an admin so not commenting generally. But that kind of view of the person leading the project is all that I would need to know. If he makes using the product difficult and uncomfortable, that's a bigger factor than the other things mentioned.
-
@scottalanmiller said in Which is better NodeBB or Discourse?:
This alone is a pretty big factor. I've not used Discourse as an admin so not commenting generally. But that kind of view of the person leading the project is all that I would need to know. If he makes using the product difficult and uncomfortable, that's a bigger factor than the other things mentioned.
Agree and that is something that has changed, at least from what I have seen. Tags and marked as solved were two things that Jeff was totally against, but the demand was there and they both became so popular that they now maintain the plugins themselves.
-
@shinyidol said in Which is better NodeBB or Discourse?:
@scottalanmiller said in Which is better NodeBB or Discourse?:
This alone is a pretty big factor. I've not used Discourse as an admin so not commenting generally. But that kind of view of the person leading the project is all that I would need to know. If he makes using the product difficult and uncomfortable, that's a bigger factor than the other things mentioned.
Agree and that is something that has changed, at least from what I have seen. Tags and marked as solved were two things that Jeff was totally against, but the demand was there and they both became so popular that they now maintain the plugins themselves.
Good progress then
-
I do wish that a few more things in NodeBB were built in rather than plugins. Not a lot, just a few.
-
@scottalanmiller said in Which is better NodeBB or Discourse?:
I do wish that a few more things in NodeBB were built in rather than plugins. Not a lot, just a few.
Yep like API access to everything. IMO that's huge for customization for various things. (I'm bias because i need all the api's i can get my hands on.)
-
@Joykiller said in Which is better NodeBB or Discourse?:
@scottalanmiller said in Which is better NodeBB or Discourse?:
I do wish that a few more things in NodeBB were built in rather than plugins. Not a lot, just a few.
Yep like API access to everything. IMO that's huge for customization for various things. (I'm bias because i need all the api's i can get my hands on.)
Agreed, that is totally needed and should definitely not be a plugin. That and a TON of more reporting.
-
@scottalanmiller Yeah, im in the middle of writing a system that would love to utilize the API, but the write API and having to manually update other plugins for their routes and all that, along with trying to figure out peoples coding stack is too much. So I'm prob just going to end up writing/searching the mongodb instead. But API would be awesome.
-
@Joykiller said in Which is better NodeBB or Discourse?:
@scottalanmiller Yeah, im in the middle of writing a system that would love to utilize the API, but the write API and having to manually update other plugins for their routes and all that, along with trying to figure out peoples coding stack is too much. So I'm prob just going to end up writing/searching the mongodb instead. But API would be awesome.
Yeah, that's a bit of a problem.
-
Hm... I made the conscious decision to develop the Write API separately mostly because it's not a feature that many people use. Those admins who want deeper integration would, certainly, but I think at the time, I wasn't entirely sure how much it'd bulk up the codebase were I to build it into core itself.
That said, I try to keep on top of it in terms of compatibility... and the Write API's RESTful interface is much more organized than NodeBB's read API, simply because it was designed that way, instead of organically grown. Was there anything specific you wanted me to address in the Write API?
With regards to documentation, I realize we really need some sort of auto-generated doc tool to show API responses. Having to "code it first and see what the responses are" should not be the way to develop...
So many things on our backlog
