More benefits of using translate3d()

So, I’m working on some code for doing a progressive render for HTML.  What that means is that rather than using pagination a user will simply scroll down and when they get to the bottom more data will be rendered at the bottom of the screen.  I was playing around with pagination and really did not like the way it was looking.  So I did a Google search and I came upon a blog post that said that for modern web applications you really shouldn’t use pagination.  Google does, but

Transform performance on mobile applications

Just a quick one today.  I have read on several web pages that if you want to speed up the rendering of your site that you need to add -webkit-transform: translate3d(0,0,0) to the page elements to have the browser use the GPU to render the page instead of the CPU. I tried this trick several times and it never seemed to work.  But I think that today I figured out why not. I would apply this trick to a container element that houses the things that were animating.  This may not

JSON parsing error in function return

OK, so I am building out a data-driven Twitter application.  Woo hoo.  One of the things I’m doing is mocking up my JavaScript API and having it return example JSON data to build the UI components.  I do this because while some may argue that you might want to build out your API’s first I believe that the customer experience is the first thing that should be working on.  Figure out the customer experience required and the API’s should follow nicely.  Should.  We’ll see if I’m blowing smoke. Anyway, so