7 ms·

Wekan uses meteor.js which is really one of the worst frameworks out there. It breaks on so many ocasions and has really bad OS support. Event he current mainta

Wekan uses meteor.js which is really one of the worst frameworks out there. It breaks on so many ocasions and has really bad OS support. Event he current maintainer kind of dislikes the framework... The worst part about metor is that it forces you to use MongoDB!

extrememacaroni 6y ago
oh no!
nebulon 6y ago
While I tend to agree from a personal perspective, however the Wekan project especially seems to be able to pump out lots of very nice features at a high rate, thanks to meteor. Additionally to this, we at Cloudron update the app package about twice a week due to that and so far had very little breakage or regressions, compared to other apps. We do not update meteor often though, which is maybe contributing to the stability.
- carlos22 6y ago
  Yes that helps but brings in other problems. For example many many security problems in the thousands of used npm packages of meteor and its dependencies.
  - enitihas 6y ago
    Unfortunately thousands of dependencies is not unique to meteor, it is the hallmark of any popular npm package. So even react and vue would have too many dependencies.
  - ocdtrekkie 6y ago
    I think at a certain point, very restrictive sandboxing is going to be the only way to safely run JavaScript-based projects.
deleted 6y ago
[deleted]
aogaili 6y ago
So what is your go-to nodejs framework? and which NoSQL database do you use?
- lioeters 6y ago
  Not the parent commenter, but.. Having only a superficial knowledge of Meteor, I prefer a more modular approach: - React/Preact with context or hooks instead of Redux - Micro for server - https://github.com/zeit/micro https://github.com/zeit/micro - Postgres with Knex for data persistence - https://knexjs.org/ https://knexjs.org/ Add authentication, WebSockets, etc., and it starts to look like an ad-hoc framework - except that all layers are generic and replaceable (theoretically) with equivalent features, like using Express or MariaDB. I'm also quite fond of Next.js, which lets me have all the above. https://nextjs.org/ https://nextjs.org/
  - aogaili 6y ago
    Thanks, but the issue with the modular, ad-hoc approach is that you need to do a lot of integration and leg work before you get to the domain problem in hand and you'll need to maintain those integrations going forward.
    - lioeters 6y ago
      I agree, and that might be the most valuable thing about frameworks like Meteor. It provides a curated developer experience, where most of these common features and integrations are solved. They tend to have far superior documentation than any ad-hoc approach, making it more suitable for teams. And a whole community that continues to debug, improve, and maintain it. Well, I'm with you in the search for such a framework!
      - SparkyMcUnicorn 6y ago
        FeathersJS + Nuxt/Next (or any front end you want) has been a good combo for me. Meteor always had a blocking issue for me every time I'd try to use it.

extrememacaroni 6y ago

oh no!

nebulon 6y ago

While I tend to agree from a personal perspective, however the Wekan project especially seems to be able to pump out lots of very nice features at a high rate, thanks to meteor. Additionally to this, we at Cloudron update the app package about twice a week due to that and so far had very little breakage or regressions, compared to other apps. We do not update meteor often though, which is maybe contributing to the stability.

carlos22 6y ago
Yes that helps but brings in other problems. For example many many security problems in the thousands of used npm packages of meteor and its dependencies.
- enitihas 6y ago
  Unfortunately thousands of dependencies is not unique to meteor, it is the hallmark of any popular npm package. So even react and vue would have too many dependencies.
- ocdtrekkie 6y ago
  I think at a certain point, very restrictive sandboxing is going to be the only way to safely run JavaScript-based projects.

deleted 6y ago

[deleted]

aogaili 6y ago

So what is your go-to nodejs framework? and which NoSQL database do you use?

lioeters 6y ago
Not the parent commenter, but.. Having only a superficial knowledge of Meteor, I prefer a more modular approach: - React/Preact with context or hooks instead of Redux - Micro for server - https://github.com/zeit/micro https://github.com/zeit/micro - Postgres with Knex for data persistence - https://knexjs.org/ https://knexjs.org/ Add authentication, WebSockets, etc., and it starts to look like an ad-hoc framework - except that all layers are generic and replaceable (theoretically) with equivalent features, like using Express or MariaDB. I'm also quite fond of Next.js, which lets me have all the above. https://nextjs.org/ https://nextjs.org/
- aogaili 6y ago
  Thanks, but the issue with the modular, ad-hoc approach is that you need to do a lot of integration and leg work before you get to the domain problem in hand and you'll need to maintain those integrations going forward.
  - lioeters 6y ago
    I agree, and that might be the most valuable thing about frameworks like Meteor. It provides a curated developer experience, where most of these common features and integrations are solved. They tend to have far superior documentation than any ad-hoc approach, making it more suitable for teams. And a whole community that continues to debug, improve, and maintain it. Well, I'm with you in the search for such a framework!
    - SparkyMcUnicorn 6y ago
      FeathersJS + Nuxt/Next (or any front end you want) has been a good combo for me. Meteor always had a blocking issue for me every time I'd try to use it.