Nvm, I thought @exodo was replying to me specifically, not the thread.

I did, it's the last link on my original post: https://github.com/NodeBB-Community

I think @Nicolas' ns-awards plugin does that?

There are a lot of factors that could go into choosing which technology to use for your web application stack, which are probably too numerous to list here. However, some reasons to choose NodeJS come with advantages like:

• Its the same language one the client and server side
  • code can be shared
  • Less context switching when developing FE vs. BE
• It's designed to be asynchronous, so it forces encourages you to think in terms of delegation
• the ecosystem is huge
• the language is developing rapidly (could also be a disadvantage)

Some disadvantages might be:

• Not strongly typed (but there are a solutions to that problem like TypeScript and Flow)
• JS is single-threaded, so it's not a good choice for CPU-intense operations
• It can be harder to do things you need to do synchronously (not impossible, but more verbose compared to an imperative language like Java or python)
• There are some oddities to the language that can be frustrating.

In terms of tutorials, I've watched a few of Derek Banas' videos, and I like his teaching style. I've heard the Egghead tutorials are really good too, and definitely check out MDN as you progress. Nothing beats actually getting in there and trying stuff though, developing a plugin for NodeBB can teach you a few tricks.

You mean this?

It might be too late, but piggybacking off of what @rbeer was trying to start, perhaps for a plugin to be accepted into the ecosystem, permissions should be given to some community group responsible for maintaining plugins that are in demand. That way, if some author goes AWOL, there won't be that single point of failure of a plugin breaking and / or not getting updated any more, that namespace effectively hijacked, and other bad things that generally happen to plugin ecosystems of nascent technologies.

If that's too draconian, maybe there could be the concept of supported and unsupported plugins, where the supported ones are part of that community team?

I'm sure you guys have thought of a lot of things like this...

@AOKP ah damn. I usually do but I missed it this time. Somehow showed up in my newsfeed and looked recent

Well this looks really exciting:

@exodo said in Plugin List / wip:

nowadays third party plugins are nearly all abandoned

Maybe the plugin contests should be reinstated? @julianlam

It still seems that there is a core of veteran plugin devs around, but I think it might just be that the authors of some of the plugins important to you have left.

It's too bad that the GitHub org that @rbeer started never took off, that might have solved some of the issues you have been having

@scottalanmiller said in MongoDB reliability called into question?:

NoSQL pre-dates relational data, I've been a NoSQL engineer since 1989 and it was OLD then

That's an interesting tidbit, what was it called before NoSQL and what were the technologies?

Something else I've been looking at are graph databases like Neo4j and Arango, and now I'm kind of anticipating that you're going to tell me that it's in the same boat (i.e. old tech with a new name)