Tuesday, September 7, 2010

Android & iPhone App Design: Is it twice the work?

http://johnnyholland.org/2010/09/06/android-iphone-app-design-is-it-twice-the-work/

So we’re back to the dilemma: do designers have to do twice the work to create native apps for the iPhone and Android?  Based on my recent analysis, I came to this conclusion: the app definition and concept phases would be very similar regardless of platform, but the app refinement and production phases would require adaptions to create full-fledged native apps for each platform.

Posted via email from miner49r

Thursday, September 2, 2010

DBMS Musings: The problems with ACID, and how to fix them without going NoSQL

http://dbmsmusings.blogspot.com/2010/08/problems-with-acid-and-how-to-fix-them.html

Our objective in this post is to explain why ACID is hard to scale. At the same time, we argue that NoSQL/NoACID is the lazy way around these difficulties---it would be better if the particular problems that make ACID hard to scale could be overcome. This is obviously a hard problem, but we have a few new ideas about where to begin.

The full paper is here:  

Posted via email from miner49r

Sunday, August 29, 2010

Less Framework 2

http://lessframework.com/

> A css framework for cross-device layouts

Posted via email from miner49r

Thursday, August 26, 2010

Java tip: How to read files quickly

http://nadeausoftware.com/articles/2008/02/java_tip_how_read_files_quickly

For the best Java read performance, there are four things to remember:

  • Minimize I/O operations by reading an array at a time, not a byte at a time. An 8Kbyte array is a good size.
  • Minimize method calls by getting data an array at a time, not a byte at a time. Use array indexing to get at bytes in the array.
  • Minimize thread synchronization locks if you don't need thread safety. Either make fewer method calls to a thread-safe class, or use a non-thread-safe class like FileChannel and MappedByteBuffer.
  • Minimize data copying between the JVM/OS, internal buffers, and application arrays. Use FileChannel with memory mapping, or a direct or wrapped array ByteBuffer

Posted via email from miner49r