Which side are you on?
-
Server-side rendering versus client-side rendering, which is better and why?
CarelAgain wrote:
Server-side rendering versus client-side rendering, which is better and why?
I'm on the fence. :) There is no black and white one is better than the other answer. Personally, I typically like declarative UI markup on the server sent down to the client for rendering. If you're talking about reports "rendering", often it makes more sense to generate the report document on the server. etc. Marc
-
CarelAgain wrote:
Server-side rendering versus client-side rendering, which is better and why?
I'm on the fence. :) There is no black and white one is better than the other answer. Personally, I typically like declarative UI markup on the server sent down to the client for rendering. If you're talking about reports "rendering", often it makes more sense to generate the report document on the server. etc. Marc
Marc Clifton wrote:
I'm on the fence. :)
...painful.
Michael Martin Australia "I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash 24/04/2004
-
Marc Clifton wrote:
I'm on the fence. :)
...painful.
Michael Martin Australia "I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash 24/04/2004
-
CarelAgain wrote:
which is better and why?
both, depending on needs. If you are looking to heat of the lounge, you may do it. Still, the honest answer is both. If your needs match client-side advantages, then it is best, if your needs match server-side, then it is best. Either/Or, black and white, this or that, arguments tend to get clouded. One person can say server-side because all their requirements and needs best match that, none of their needs match client-side, so that is the perception they will have. The reverse can also be true, for some where server-side is a disadvantage, and they have never needed, nor have any advantages with server-side anything, then client-side is best and that will be their perception. Both are true, for those individuals. Match the operation to the requirements/needs.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
no fair injecting logic into flame bait.
-- You have to explain to them [VB coders] what you mean by "typed". their first response is likely to be something like, "Of course my code is typed. Do you think i magically project it onto the screen with the power of my mind?" --- John Simmons / outlaw programmer
-
and how you're sitting on it :)
-- You have to explain to them [VB coders] what you mean by "typed". their first response is likely to be something like, "Of course my code is typed. Do you think i magically project it onto the screen with the power of my mind?" --- John Simmons / outlaw programmer
-
Server-side rendering versus client-side rendering, which is better and why?
Client-side. Reasons:
oAllows for easier localication - the user's system already knows its locale, without it having to be sent to the serveroMay allow for client-side accessibility aids to work better (e.g. screen readers understand what a label, and button control are, whereas things may not be recognized well as rendered in a browser)oDistributed processing - client-side rendering spreads out the workload to client machines, which reduces the burden on the servero"Prettier" interfaces - the client-side system knows what its display facilities are and can customize for larger screens, better use of colors & graphics, etc.oAdded: Less round-trips - results can be sent to the client-side and it can render it in whatever form the user requires (view, save, export, etc.) Server-side rendering has its benefits, too:oIt eliminates much of the the variability of client-side systems - all you need is a supported browser and off you gooUse of thinner clients (less processing power) becomes possible ---------- --modified at 11:16 Wednesday 22nd August, 2007 Note that the above implies a difference between processing and rendering, where rendering is presenting the results of processing in a usable form. But generally, I would lean toward client-side rendering, unless the particular application REALLY operates better with server-side rendering. People tend to forget that not every application should run as DHTML in a browser... A good acid test: if you could not imagine it working well using a IBM 3270-style terminal and form interface, it probably should not be running in a browser. Oh, and trying to avoid requirement/installation of a client-side component is usually not a valid excuse for doing everything server-side - users have been installing software for years just fine, and if you cannot write good quality client-side software, with a working installer, you should stay the**_hell_**away from server-side stuff. Peace!-=- James
Please rate this message - let me -
no fair injecting logic into flame bait.
-- You have to explain to them [VB coders] what you mean by "typed". their first response is likely to be something like, "Of course my code is typed. Do you think i magically project it onto the screen with the power of my mind?" --- John Simmons / outlaw programmer
dan neely wrote:
no fair injecting logic into flame bait.
I know... bad habit... just like my over use and abuse of ellipsis.... ;P
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Server-side rendering versus client-side rendering, which is better and why?
Still topside, thankfully. :-D
-
Server-side rendering versus client-side rendering, which is better and why?
The Dark Side.
-
Server-side rendering versus client-side rendering, which is better and why?
Both. Each have their place. I'm against client side rendering of stuff that should have been pre-chewed on the server (since it means my poor machine gets bogged down) and in some cases server-side rendering doesn't take into account the capabilities of my machine. It's a delicate balance that requires common sense
cheers, Chris Maunder
CodeProject.com : C++ MVP
-
The Dark-Side. I admit. It was the blue lighting bolts from the finger tips that got me. :rolleyes:
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTLDouglas Troy wrote:
It was the blue lighting bolts from the finger tips that got me
I prefer the Lite-side of the force... then you can talk like Fozzy bear and everyone forgets Fozzy and remembers only you years later. ;P
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
and how you're sitting on it :)
-- You have to explain to them [VB coders] what you mean by "typed". their first response is likely to be something like, "Of course my code is typed. Do you think i magically project it onto the screen with the power of my mind?" --- John Simmons / outlaw programmer
dan neely wrote:
and how you're sitting on it
and who you are sitting with. ;P
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
The Dark Side.
-
The Dark Side.
The Emperor hasn't driven it from you fully!
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
When someone at work was talking about that I replied "Dear, I am the Dark Side." :-D
Visit http://www.readytogiveup.com/[^] and do something special today.
I used to have hair that was a tad more red than now. Hard to see any red now. But I love a bumper sticker I've seen, "Forget the dark side I'm a red head.":-D That might explain a lot to many here. :omg:
-
The Emperor hasn't driven it from you fully!
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
El Corazon wrote:
The Emperor hasn't driven it from you fully!
Does that mean I have to use Java?:wtf: NEEEEEEEEEEEEVVVVVVVVVVVVEEEEEEEEEEEEERRRRRRRRRRRRRRRRRRRRRRRR!!!
-
and how you're sitting on it :)
-- You have to explain to them [VB coders] what you mean by "typed". their first response is likely to be something like, "Of course my code is typed. Do you think i magically project it onto the screen with the power of my mind?" --- John Simmons / outlaw programmer
Or the way the sitting pose is captured on a photograph. You can capture a snap by just being close to the fence without even sitting by little-to-neat camera tricks. :)
Vasudevan Deepak Kumar Personal Homepage Tech Gossips
-
Both. Each have their place. I'm against client side rendering of stuff that should have been pre-chewed on the server (since it means my poor machine gets bogged down) and in some cases server-side rendering doesn't take into account the capabilities of my machine. It's a delicate balance that requires common sense
cheers, Chris Maunder
CodeProject.com : C++ MVP
Chris Maunder wrote:
It's a delicate balance
True. A meticulous, careful and a striking balance between the two components is required for the success of any application.
Vasudevan Deepak Kumar Personal Homepage Tech Gossips
-
Server-side rendering versus client-side rendering, which is better and why?
-
Server-side rendering versus client-side rendering, which is better and why?
I would tend towards client side Smart Apps. And also pie and chips for dinner.
"It was the day before today.... I remember it like it was yesterday." -Moleman