4 ms·

You missed that the MeteorJS ecosystem has a lot of packages that take care of i18n, routing support (iron router), SEO (spiderable), basic forms support (autof

by charif 12y ago

You missed that the MeteorJS ecosystem has a lot of packages that take care of i18n, routing support (iron router), SEO (spiderable), basic forms support (autoform). I agree that there is room for improvement, but I am confident that the team behind MeteorJS will make MeteorJS a success.

alexandernst 12y ago
No, I didn't. I'm aware of the existance of those. But those , as you say, external packages are lacking any type of official support. And that is just no acceptable for any serious/big project. A project manager will be rofl-ing hearing those words, I'd say.
- subpixel 12y ago
  There has been some unofficial recent discussion on certain Slack channels about MDG introducing their own versions of key packages. I hope that happens - I think it would go a long way towards addressing concerns like yours, which I share.
- kowdermeister 12y ago
  I know these project managers. They ask for a 15 line JS helper "library" enterprise level support and they start to scratch their head "what if the developer abandons it".
  - alexandernst 12y ago
    Only that we're not talking about a 15 lines JS helpers, but about quite big parts that should be in the core and instead they are some 3rd party plugins.
    - dandv 12y ago
      If you're looking for a monolithic solution, Meteor may not be for you. Check out Wakanda and Servoy. Delegating quasi-core parts of the platform to 3rd party libraries is quite common. For example, the preferred routing package for Angular, ui-router (https://github.com/angular-ui/ui-router https://github.com/angular-ui/ui-router) was born four years after the release of Angular, and for DOM state preservation, the ui-router-extras (https://github.com/christopherthielen/ui-router-extras https://github.com/christopherthielen/ui-router-extras) addon is required.
- towelguy 12y ago
  Almost all the node.js ecosystem consist of external non-official packages. I don't get your point.

by charif 12y ago

alexandernst 12y ago

No, I didn't. I'm aware of the existance of those. But those , as you say, external packages are lacking any type of official support. And that is just no acceptable for any serious/big project. A project manager will be rofl-ing hearing those words, I'd say.

subpixel 12y ago
There has been some unofficial recent discussion on certain Slack channels about MDG introducing their own versions of key packages. I hope that happens - I think it would go a long way towards addressing concerns like yours, which I share.
kowdermeister 12y ago
I know these project managers. They ask for a 15 line JS helper "library" enterprise level support and they start to scratch their head "what if the developer abandons it".
- alexandernst 12y ago
  Only that we're not talking about a 15 lines JS helpers, but about quite big parts that should be in the core and instead they are some 3rd party plugins.
  - dandv 12y ago
    If you're looking for a monolithic solution, Meteor may not be for you. Check out Wakanda and Servoy. Delegating quasi-core parts of the platform to 3rd party libraries is quite common. For example, the preferred routing package for Angular, ui-router (https://github.com/angular-ui/ui-router https://github.com/angular-ui/ui-router) was born four years after the release of Angular, and for DOM state preservation, the ui-router-extras (https://github.com/christopherthielen/ui-router-extras https://github.com/christopherthielen/ui-router-extras) addon is required.
towelguy 12y ago
Almost all the node.js ecosystem consist of external non-official packages. I don't get your point.