Comment by Shreyansh Pandey on "Why do developers claim that Meteor can help build universal JavaScript apps when it can't render apps on server?" | Hashnode

Jan 24, 2016

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! :)

Björn

Insane Full-Stack Developer

Jan 25, 2016

"Server-side rendering is the technology of the past." ... Wut?

I think it really depends of the use case. For example the AngularJS Directives. If you iterate over an object, adding directives and building your webpage dynamically it would be a rather huge load, especially for mobile devies.

So why should it be a "past technology" if it helps speeding up the performance of such frameworks?

I agree with you, that Server-side rendering does not belong to "Full Stack" it's just a component you can use but doesn't define the stack.

Well, for performance, we have ReactJS and vDOM manipulation. It works flawlessly, without any server-side rendering, on a datastream which has an output of 1500 objects/s.

But, it surely is a technology of the past. Its usage went from "mainstream" to "performance enhancer". People are moving away from server-side rendering to client-side rendering. What I am trying to say here is that it "is a technology of the past" as its usage it not what used to be; that should justify my point.

You give an example of Angular. Okay. Its DOM updates and repaints are expensive; so, again, I publicise React. Have a look at it, and tell me if it's slow.

Search Hashnode