Next steps on Blaze and the view layer

[aadams]

In my opinion, this is a straw-man argument:

@Siyfion

I’m just simply pointing out the fact that he is complaining about being forced to change his code to get performance improvements and bug fixes… Which implies he has performance issues and bugs now. If he doesn’t, this argument becomes a moot-point, he can continue running the code he has now, as-is, with no issues. [Emphasis mine].

Lets just say I have no issues with Blaze 1 right now, as is (to wipe away the point you made based on assumption).

The second sentence in my original post alone is enough to cause what I believe is a serious encumbrance on my bottom line:

@aadams

If I choose not to do a full rewrite, Blaze and all the bugs and performance issues it has (and now will always have), will start to cause a drag on my bottom line. As packages migrate away from Blaze or become abandon-ware, I’ll be unable to provide meaningful enhancements and bug fixes to my application. [Emphasis added].

---

The following is what I would consider ad hominem comments:

@Siyfion

I don’t think there’s much hope for your customers

@Siyfion

Did you re-read this before you posted it?

I’d like to keep the discussion civil.

---

It is intellectually dishonest to brush off an individual’s reaction to a situation as unacceptable because it is not the same reaction that you would have:

@Siyfion

I just see this argument as making a mountain out of a molehill

---

I’d say this is an appeal to questionable authority:

@Siyfion

The change to “Blaze 2” or whatever they call it I’m sure will be the most minimal change that MDG can make it, whilst still retaining all of the benefits of utilizing React as the underlying view-model. [Emphasis mine]

---

Further, as to your statement about the migration from Blaze 1 to React:

@Siyfion

This is exactly what I am in the process of doing right now. It works, it’s easy, it’s pain-free.

I’d just like to point you back to my original post:

@aadams

Doing a full rewrite in React could cost me months of costly rework with little to no benefit to my bottom line. This rework will [take me away from feature requests] and [bug fixes] that will delight my clients and in some cases enhance my bottom line. [Emphasis added].

---

In sum, my conclusion:

I believe we, the Meteor developer community, has been given False Alternatives, either stay with Blaze 1 or Migrate to React (or Blaze 2). There exists an alternative that seems unconsidered by MDG, I believe to the great detriment of the existing Meteor developer community:

Namely keeping Blaze 1 around for the long term in support of their existing Meteor developer based. And in so doing maintaining, bug fixing, and possibly ever-so-slightly enhancing Blaze 1.

The result I believe will allow MDG’s Meteor developers time to breathe, adapt, adjust, and migrate to new technologies as MDG too adapts to its changing environment.