I gave up on meteor when they did the version upgrade from 1.2 to 1.3 they changed everything with no easy way of upgrading a big project which made me think future upgrades would be this difficult as well.
And if I’m not mistaken, it can only be run with mongodb.
It seems you misread the stuff around "For some odd reason, people think using Meteor is all or nothing". You don't have to use MongoDB. But you can, and Meteor makes it very easy.
Your claim on upgrading from 1.2 to 1.3 is simply not true. It's actually the other way round. I do not know of another project with as much commitment to backwards compatibility, as Meteor.
There's nothing preventing you from running a Meteor 1.0 project on the latest 1.8.2 beta release. And 1.0 was many years ago.
I guess but then again, you wouldn't be taking advantage of that version upgrade which if I'm not mistaken was when they added code splitting. Before 1.3 I think you loaded the whole SPA in the first payload which wouldn't make sense to upgrade without re-structuring the project to take advantage of this.
Please correct me if I'm wrong as this was some time ago.
If you want to take advantage of code splitting and dynamic importing, then yes, you will have to put some time into refactoring your application to do so. But that's not Meteor specific, it's just how life is.
I guess Meteor does so much out of the box, you might forget it can't (not yet, at least) write your app for you!
The main takeaway from this should be: your Meteor 1.0 project from many moons ago will still run on Meteor 1.8.1 (the latest recommended release). There is no need to refactor anything. During the evolution from 1.0to 1.8.1 Meteor has gained all kinds of great new features, fixes and improvements, but they are, at least to my knowledge, 99% non-breaking and/or optional. That's quite something.
That sounds right. Sure, you obviously may need to update structure to use new features, but old features didn't break. The new structure follows the modern standards of the JS community (ES Modules). It was inevitable for this change to happen; it would be detrimental for Meteor to follow the non-standard and not adapt to the change.
Johhan, I'm not sure what you ran into but the update from 1.2 to 1.3 was surely backward compatible! I've updated projects from 1.1 all the way to 1.8.
I gave up on meteor when they did the version upgrade from 1.2 to 1.3 they changed everything with no easy way of upgrading a big project which made me think future upgrades would be this difficult as well.
And if I’m not mistaken, it can only be run with mongodb.
Other than that, it is a good framework.
It seems you misread the stuff around "For some odd reason, people think using Meteor is all or nothing". You don't have to use MongoDB. But you can, and Meteor makes it very easy.
Your claim on upgrading from
1.2to1.3is simply not true. It's actually the other way round. I do not know of another project with as much commitment to backwards compatibility, as Meteor.There's nothing preventing you from running a Meteor
1.0project on the latest1.8.2 betarelease. And1.0was many years ago.I guess but then again, you wouldn't be taking advantage of that version upgrade which if I'm not mistaken was when they added code splitting. Before 1.3 I think you loaded the whole SPA in the first payload which wouldn't make sense to upgrade without re-structuring the project to take advantage of this.
Please correct me if I'm wrong as this was some time ago.
If you want to take advantage of code splitting and dynamic importing, then yes, you will have to put some time into refactoring your application to do so. But that's not Meteor specific, it's just how life is.
I guess Meteor does so much out of the box, you might forget it can't (not yet, at least) write your app for you!
The main takeaway from this should be: your Meteor
1.0project from many moons ago will still run on Meteor1.8.1(the latest recommended release). There is no need to refactor anything. During the evolution from1.0to1.8.1Meteor has gained all kinds of great new features, fixes and improvements, but they are, at least to my knowledge, 99% non-breaking and/or optional. That's quite something.That sounds right. Sure, you obviously may need to update structure to use new features, but old features didn't break. The new structure follows the modern standards of the JS community (ES Modules). It was inevitable for this change to happen; it would be detrimental for Meteor to follow the non-standard and not adapt to the change.
Johhan, I'm not sure what you ran into but the update from 1.2 to 1.3 was surely backward compatible! I've updated projects from 1.1 all the way to 1.8.
Hi Johhan! The update from 1.2 to 1.3 is backwards compatible. Using non-module JS files still works just like before. Cheers. - Joe