If you had one wish for Meteor, what would it be?


#1
  • Better build tool (code splitting, etc)
  • Scaling for oplog tailing
  • Easy MySQL integration
  • Easy RethinkDB Integration
  • A new, more modern front-end system (i.e. Redux/React/SSR/etc or Blaze 2)
  • A file upload system
  • Easy, non-Galaxy deploys
  • Microservice support
  • Other (please explain)

0 voters

Keep in mind: a faster build tool (faster rebuilds) is on the way, and the idea behind database integrations is to have it as easy as it is with Mongo.


Does It Make Sense to Start a Meteor 2.0 to Retain "Classic Meteor"?
#2

bumping it for more votes


#3

I had a really hard time with this question. I think for me, what I really wish that Meteor had was a true competitor. I mean, we have feathers, ember, pure node, pure js, etc.

But I think that the kind of specific niche that Meteor fills (data layer, accounts, reactivity, etc.) isn’t really filled by anyone BUT Meteor. Which is awesome from a “we made something awesome that nobody else did” mentality. But from the perspective of MDG and the main consumers of Meteor, obviously this can be a bit of a roller coaster.

As odd as it sounds, what I think I ultimately wish is that there were competing mutations for this niche, allowing us (the lucky consumers of OSS :grinning:) to benefit from a multitude of tested, explored frameworks, instead of just one really revolutionary one :heart_eyes:


#4

Totally agree with this - there would be a lot to learn from competitors. I think create-react-app is doing some good stuff though, at least for the UI side!


#5

I feel like the MySQL integration, Oplog Scaling, and Build tool are more reasonable tasks for MDG. The rest of the options seem as if the community should be responsible for such things. Regarding Galaxy, I find your statement somewhat ironic. Galaxy was the “Easy non-insert-anything-here deploys” solution for a plethora of archaic deployment options. It seems like you could go back to things like DO, Heroku, Modulus, etc., but why?


#6

Apollo 1.0 :slight_smile:

Thanks for whoever did this: https://www.codetours.xyz/tour/partyparrot/GitHunt-API-code-tour


#7

I would also say,

  • Easier integration with frameworks like AuthO.
  • Better alignment with the serverless paradigms.

#8

Better build tool: Allow to separate server side from client side to a point, where i could write two client apps (Admin Panel and Main App), publish them through regular ftp upload and let the server side stay on another node-js-only server.


#9

Only one thing: webpack-blaze :slight_smile:


#10

I still wish MDG could return free tier deployment as two-week-life containers for instance.
It was great. An ease of seeing any prototype/test/tutorial you want with one command.

Code splitting by default is cool to. Yet webpack is here and now…
I’d vote for RethinkDB, I kinda love new paths with no overhead.


#11

I guess it wouldn’t hurt to link in this post: What is Meteor missing?
Infinite possibilities!


#12

Let’s not ressurect super old threads though - I’d suggest keeping the discussion in here.


#13

Build tool is of course very important and was biggest pain point for some time but also already worked on. So I voted scaling and performance (second place currently so if MDG is listening it should work on it next). Time for meteor to grow up :slight_smile:


#14

Nice poll, but it would’ve been nice to be able to select multiple answers.


#15

Indeed - we abandoned the poor thing in its childhood!


#16

With the build tool, production source maps that could be sent to various services on deploy (without being deployed to production themselves) would be great (recently mentioned here). I also hope MDG pushes the envelope for something past route-based code-splitting (demand-/ config-/feature-based, etc. Not sure what it’s all called, but with the idea that over- and underbundling and/or over- and underfetching of actual code is kept to a minimum.)


#17

Indeed - though I wonder if the real solution is something like Fast-Boot by Ember. We actually want all the code/templates to load upfront for performance, we just don’t like how long that takes to render for visitors.


#18

The one thing I need for Meteor to be usable for me is better offline support with service worker


#19

My wish would be a meteor fully transitioned to npm.


#20

Ah that would be cool. I suspect someone can roll this functionality on their own though?