I watched the open keynote from Rails World 2024, which launched Rails 8. It was cool to see DHH explaining how powerful Rails 8 is, especially because they've solved all the main use cases you'd have in a web project.
This has been my goal for a long time, but now I've decided we really need to solve it. With Meteor 3, we don't have any major technical debt like fibers or Node.js 14, so I believe we can create a simple use case of all popular features in the Quave Meteor template project.
We also need to check if Meteor Migrations is ready for Meteor 3.
[ ] so you can run async database migrations.
If we find more common cases, we should adopt them in this Meteor template to show that Meteor 3 is ready for prime time and can solve any typical web application issue.
Another important thing is to provide common actions, like, create a new collection with schema prompts so people can scaffold projects fast. We don't think generators of code are still necessary with all the new AI Tools, but good prompts with good examples are important. Specially due to the changes in Meteor 3.
Prompts:
[ ] create a new collection
[ ] Create a new collection with schema
[ ] Create a new collection with schema and composers
After finishing the code and package level work, I'd like to
[ ] record a video showing all these features together and creating a new project easily.
Our objective here is focused on Meteor 3, we don't care about Meteor 2 for this to work there, and we can also create breaking changes in the packages but following SemVer.
If you want to help, send a message to me (filipe@quave.com.br).
An additional point (not the main goal) could be to have a way to generate CRUDs easily, but that's just a bonus!
We have this internally at Quave and it could be helpful to open source it as well, but that is something for another issue.
Additional point (not the main goal as well) Slingshot compatible with Meteor 3 and also supporting CloudFlare R2 besides AWS S3.
I watched the open keynote from Rails World 2024, which launched Rails 8. It was cool to see DHH explaining how powerful Rails 8 is, especially because they've solved all the main use cases you'd have in a web project.
This has been my goal for a long time, but now I've decided we really need to solve it. With Meteor 3, we don't have any major technical debt like fibers or Node.js 14, so I believe we can create a simple use case of all popular features in the Quave Meteor template project.
The Quave template already does a lot:
We still miss a few details about the Cron package. It's there and can run jobs, but it needs attention to:
We also need to check if Meteor Migrations is ready for Meteor 3.
If we find more common cases, we should adopt them in this Meteor template to show that Meteor 3 is ready for prime time and can solve any typical web application issue.
Another important thing is to provide common actions, like, create a new collection with schema prompts so people can scaffold projects fast. We don't think generators of code are still necessary with all the new AI Tools, but good prompts with good examples are important. Specially due to the changes in Meteor 3.
Prompts:
Promote the way
After finishing the code and package level work, I'd like to
Our objective here is focused on Meteor 3, we don't care about Meteor 2 for this to work there, and we can also create breaking changes in the packages but following SemVer.
If you want to help, send a message to me (filipe@quave.com.br).
An additional point (not the main goal) could be to have a way to generate CRUDs easily, but that's just a bonus!
We have this internally at Quave and it could be helpful to open source it as well, but that is something for another issue.
Additional point (not the main goal as well) Slingshot compatible with Meteor 3 and also supporting CloudFlare R2 besides AWS S3.