On Wed, Oct 17, 2012 at 7:22 PM, Soichi Ishida <li...@ruby-forum.com> wrote: > Thanks everyone. I was worried about both server and client but > especially about the client side. > > Sounds like I should not be worried about it too much.
Now days Javascript parser themselves are pretty efficient, the only problem I worry about with Javascript is how much I'm loading at once, and that's not to do with processing but more load time, if I can load 1kb vs 10kb I will go that route because even though most of us don't like to admit it, some people still do have bad 3G and even dial-up or satellite that isn't so stable on speed. So I always reduce how much I'm loading at once if I can, meaning I treat my front-end like I treat my back-end I only load and use what I absolutely need not what I think will be cool and if I can pull in the cool pieces without a larger dependency I will. What I mean by that is I actually take specific pieces from Gems and just put them in the lib, or I pull specific pieces from Javascript libraries and load them pieces myself. Another side rant on the same subject that some people should actually worry about: The other thing I worry about is what some companies like Twitter do which is activate the GPU for no reason other than rendering CSS animations (which isn't even necessary on a modern computer unless you do quite a few things) or other stuff which isn't always needed at all and in some cases makes things lock up (for a split second) on some smart phones. It makes it even worse when you mix bootstrap with Chrome on Linux which has a huge bug in GPU rendering (with FGLRX and in some cases even Nvidia) in that any page that is rendered by the GPU is completely broken. So if you are worried about the client, disable the GPU enabled parts of your CSS or warn your users to disable the GPU usage in Chrome. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
