geowa4

Re:The Problem with AMP on Tuesday January 17, 2017 @06:17PM (#13422438)

I agree, and I live in the US. I couldn't care less about seeing the original URL and have never run into a broken page.

Re:Flux is the new WndProc on Wednesday October 14, 2015 @02:35PM (#10388462)

I've never liked the comparison of Flux to functional reactive programming. It's really just good ol' object-oriented design. Actions are akin to the Command pattern and the Dispatcher feels like a Mediator. Passing callbacks instead of objects and making a mostly directed graph does not yield FRP.

In my latest project, I used React with rx-react (https://github.com/fdecampredon/rx-react) and RxJS. That combination definitely made for some FRP fun.

Re:Call Me Maybe: MongoDB Stale Reads on Wednesday April 22, 2015 @09:20AM (#9420149)

Since Postgres added a JSON type and Docker made running it simple in development, I haven't had a need for anything else. Call me old school, but I prefer starting with a relational database and changing when it's no longer appropriate.

Re:Mobile development with HTML5 on Thursday August 25, 2011 @10:16PM (#2927098)

I agree that it is important that you keep your application small. However, using the application cache like the author suggests means that you will never have to download the specified content, like jQuery, again. Additionally, since you have 5MB of storage, I really don't think the 31KB of jQuery really matters.

I agree that client-side rendering is not optimal, but for different reasons. This isn't 2006 anymore, phones are more powerful now. Unless I absolutely have to, I'm not going to care about your Nokia from back in the Stone Age. My problem with client-side rendering is that it chokes on large data-sets. You also have to pay the penalty to download the dynamic content after you download the static content, but this can be mitigated by only updating the content, rather than using AJAX to load it all to begin with. That also kills the author's use of the plug-in that stores AJAX data locally, but that's a separate issue.

My advice: Use jQuery, jQuery Mobile, and AppCache. When combined, jQuery and jQuery Mobile (including CSS) take up 58KB of space. Oh, and since you're storing it all locally from now on, there's no need to cry about the time (less than 1s on 3g) it takes to download all those fancy JS files.