It seemed that the general idea of web being slow is so polarizing that each and everyone of us can't even pinpoint where the problem is. I suspect the problem is a multidimensional one.
Happy to see that these powerful little things are getting more affordable. What does those expansion pins do? Can they be used for I/O like button and LED?
Just about every pin on this processor can be used for GPIO. Some pins, like the DDR interface, can only perform one function, but the vast majority can be configured to do one of seven different functions.
Same here. I used D-U-N-S Profile Lookup[1] and entered the company's detail (Singapore company). An hour later, I received an email containing the D-U-N-S number from noreply-appledev@apple.com
It started with the implementation of an Infinite List Component that handles items with unknown sizes. Only a very small set of DOM nodes is actually created to fill in the actual visible screen area. They will then be constantly recycled to render next / previous data on-demand. As a result, memory footprint is kept minimal, regardless of the amount of data in the Store. Making this work is the easy part. Making it fast with the complexity and variety of items such as News Feed stories is the real challenge. The bottleneck lies within the core processes that a browser has to perform: layout and compositing.
I wished jQuery Mobile has Infinite List Component that handles the list item recycling the last time I used it. It is the equivalent of UITableViewCell's dequeueReusableCellWithIdentifier.
While I agree that Esplora is a true departure from previous designs, I don't think "fragmentation" is really an obstacle here. As always, users just need to choose the board model under Tools -> Board menu. As the underlying library and code, I believe are still the same.
Yeah, I read that Objective-C got it's ARC feature after static analyzer was integrated to Xcode. No more manual reference counting is definitely a plus.
