4 ms·

I've been using Meteor since this past September. Great to see there's only 1 more update prior to 1.0.

by malokai 13y ago

xiaoma 13y ago
What happens in 1.0? Is it primarily the marketing buzz you're looking forward to, or is there a specific feature?
- deleted 13y ago
  [deleted]
- heck0045 13y ago
  The last major hurdle for 1.0 (as I understand it) is final integration work with Atmosphere and updates to the package management system. While this is no small feat, it is far less of an engineering hurdle than either Blaze or the opLog tailing which was implemented in 0.7.0.
- mcrider 13y ago
  I'm looking forward to a more stable API. I think a lot of things are solidified by this 0.8.0 release, but working up to it I've had to deal with a lot of upstream changes that forced me to refactor a lot of code. Of course, its all in the name of progress and the Meteor community is super helpful and friendly, so no big whoop.
- maxharris 13y ago
  I'm looking forward to each template having its own local reactive state so that I can get away from storing everything in session variables, which are global. Without this feature, it's hard (or harder than it should be) to create reusable user interface code.
- TylerE 13y ago
  More the just marketing buzz, imo. I know the IntelliJ guys have said they will build in first-class Meteor support once it hits 1.0.
pbreit 13y ago
Maybe you're kidding but I'm not sure that's really how it works. I'm sure they will do as many updates as necessary prior to a 1.0 regardless of current numbering.
- uberc 13y ago
  Last line of the blog entry announcing Blaze as the new feature in the 0.8.0 release: "Just one more big item to go before 1.0 now!"
  - pbreit 13y ago
    Ah, OK. I stand corrected. Although I guess my comment isn't exactly incorrect.
malokai 13y ago
Now that I've had time to check out the update in depth, I can say that this update actually affects my project in a huge way. It'll require refactoring probably around 500 of lines of code because of the elimination of {{#isolate}, {{#constant}} and preserve-inputs, and the new template.rendered functionality.

I've been using Meteor since this past September. Great to see there's only 1 more update prior to 1.0.

by malokai 13y ago

I've been using Meteor since this past September. Great to see there's only 1 more update prior to 1.0.

xiaoma 13y ago

What happens in 1.0? Is it primarily the marketing buzz you're looking forward to, or is there a specific feature?

deleted 13y ago
[deleted]
heck0045 13y ago
The last major hurdle for 1.0 (as I understand it) is final integration work with Atmosphere and updates to the package management system. While this is no small feat, it is far less of an engineering hurdle than either Blaze or the opLog tailing which was implemented in 0.7.0.
mcrider 13y ago
I'm looking forward to a more stable API. I think a lot of things are solidified by this 0.8.0 release, but working up to it I've had to deal with a lot of upstream changes that forced me to refactor a lot of code. Of course, its all in the name of progress and the Meteor community is super helpful and friendly, so no big whoop.
maxharris 13y ago
I'm looking forward to each template having its own local reactive state so that I can get away from storing everything in session variables, which are global. Without this feature, it's hard (or harder than it should be) to create reusable user interface code.
TylerE 13y ago
More the just marketing buzz, imo. I know the IntelliJ guys have said they will build in first-class Meteor support once it hits 1.0.

pbreit 13y ago

Maybe you're kidding but I'm not sure that's really how it works. I'm sure they will do as many updates as necessary prior to a 1.0 regardless of current numbering.

uberc 13y ago
Last line of the blog entry announcing Blaze as the new feature in the 0.8.0 release: "Just one more big item to go before 1.0 now!"
- pbreit 13y ago
  Ah, OK. I stand corrected. Although I guess my comment isn't exactly incorrect.

malokai 13y ago

Now that I've had time to check out the update in depth, I can say that this update actually affects my project in a huge way. It'll require refactoring probably around 500 of lines of code because of the elimination of {{#isolate}, {{#constant}} and preserve-inputs, and the new template.rendered functionality.