Server-side rendering is the technology of the past. You wouldn't be able to go anywhere good if you use that. Now, there are people like this who have been defying odds like Gods (oh, it rhymes).

Meteor gives you a client-side framework, and a server-side framework. The server-side framework is used for, well, your backend and the client for your front-end. The rendering part is completely optional. It's a full-stack framework so long so you have backend code embedded (monolithically or generally.)

I guess I won't be wrong if I say that the semantics of the last interrogative is a little dicey. What do you understand by Full Stack? Full stack essentially means that you work in both: the front and the backend. And Meteor offers that, therefore it's a full-stack framework!

I hope this helps! :)

Modern Browsers are capable of doing the heavy weight lifting - Rendering the UI! They aren't the dumb terminals anymore that simply display whatever the server sends!

This point also makes Server-side rendering is the technology of the past viable, somewhat! :P

Meteor makes use of this fact and sends "Data over the Wire", not HTML. And the meteor front-end on the browser consumes the data and takes care of the rendering the UI.

I think that's the reason why Meteor doesn't support server side rendering, quite yet! :)

btw, there are some attempts to bring SSR to Meteor: meteor-ssr

But hey, again, why to let the server do all the heavy lifting when the browser can jump in do it? Let the server have some fun! :P