Server side rendering and Blaze deprecation

[khamoud]

Hello everyone!

I use React for my front end but I still use Blaze to handle my SEO and email templates. My question is, since Blaze is getting deprecated how will I be able to handle SEO and email with React? From my understanding it is possible to render react templates on the server but I’ve heard that React is much more CPU intensive on the server compared to Blaze.

I just want to hear thoughts people may have that know more about the subject than I do.

[jitterbop]

Blaze is not being deprecated though.

[khamoud]

Next steps on Blaze and the view layer

Hi everyone, For those of you I haven’t met, I’m Geoff Schmidt, one of the original Meteor core developers and CEO of MDG. With Galaxy in the field now and doing great, I’ve been able to clear out a big chunk of my schedule and you can expect to see me much more active on the forums. As we start to approach the end of the year, MDG is taking a look at the Meteor stack from top to bottom and thinking about what’s next. We’re thinking about testing, routing, schemas, and more, and what should be…

They never used the word “Deprecated” but they did say

@gschmidt

Today’s Blaze will continue to work but MDG’s development efforts will be focused on the new React-based templating option, React JSX, and on Angular.

[sashko]

SEO

I’d suggest using a service like prerender to handle server side rendering for SEO, because then the CPU is on their servers, not yours :] http://guide.meteor.com/deployment.html#seo

Server-side email

It seems like email templates wouldn’t be a big issue for CPU, since it’s very predictable when you generate them, and they probably aren’t terribly complicated (maybe?). Do you think this would be a problem?

[jitterbop]

Here’s a more recent account. This helps clear things up. I see it’s not the gist of your post, I just thought to mention it

Angular, React, and Blaze

Late last year I posted a message about how MDG was thinking about the view layer and where we thought we should go next. Since then, we’ve had many more conversations, both here on the forum, with the Customer Advisory Board we formed last year, and 1:1 with teams ranging from large production users to Meteor non-users, and in environments ranging from small startups to large enterprises. Against that backdrop, I wanted to share what we’ve learned and talk about where to go next. The Strength…