May 9, 2013
Apple and the iWatch

With all the speculation that has gone on around the rumors of the iWatch, the most surprising revelation, to me at least, has been the number of tech pundits who don’t wear watches. The same people who love the Jawbone Up and the Nike Fuelband don’t wear watches? Makes it seem like they might not be horribly qualified to discuss the watch market, doesn’t it.

It seems that there is a divide between people who are into the “quantified self” and those who are watch wearers. The watch wearers, the very people who make up the market that it’s claimed Apple would be selling to with the iWatch, are very different people than the people who are putting up with the looks and design of the smart tracking devices. Watches are a form of jewelry, and in the case of men’s watches, one of the more socially acceptable forms. The tracking devices often have watch features, but they are focused almost solely on the data gathering and the design is a secondary goal.

The way I see it, for Apple to succeed in with this type of device, it would need to build in the tracking features of some of these devices, but with the looks/design of the more traditional watches. This would probably mean a smaller screen than most people are expecting, and less of a iPhone on your wrist and more of a remote sensor for your iPhone. Maybe the iWatch would function more like the Pebble, but either way, the build quality and design would have to be ratcheted way, way up.

The long and short of it is that I can’t see this being anything but a hobby, similar to early Apple TV, but even smaller. Unless… I get my wish and this is all an elaborate prank to get Samsung to make a shitty pedometer watch.

5:10pm  |   URL: http://tmblr.co/ZNUaDykdCwkU
Filed under: Apple Tech watches iWatch 
May 8, 2013
Arnold & Son Time Pyramid Watch

Time Pyramid

One of the best looking skeletonized watches I’ve seen. Love how this looks with the large open spaces.

12:22pm  |   URL: http://tmblr.co/ZNUaDykXFgwU
Filed under: watches 
April 3, 2013
Mozilla's Rust… oh and Servo too

I find it telling that the part of this announcement that I’m most interested in is Rust, and that the article on ARS spends most of it’s time talking about that. Servo isn’t really the focus of the article it seems.

Good luck Mozilla and Samsung. The world needs to get more rendering engine competition going again.

Meanwhile, I’ll be checking out Rust.

March 3, 2013
Serious Outside the Box Engineering

A very interesting find by Panic and interesting discussion (especially this comment) about how Apple designed the Lightning video adapter with an ARM SoC that decodes a compressed video stream from the iOS device and outputs the video on the AV outputs.

The design of this means that the iOS device can output video to any device type as long as there is an adapter that can talk to it. This of course is not limited to video, but designing this way means the only limitation for video is the bandwidth of the lighting port rather than being tied to a specific hardware implementation.

Very interesting to say the least.

12:20pm  |   URL: http://tmblr.co/ZNUaDyfQxA2S
Filed under: Apple iOS tech 
January 30, 2013
New Blackberry…

Brian Lam has the best take I’ve seen so far on the BB10 announcement today.

It was just blah. Nothing to see here, move along.

9:50pm  |   URL: http://tmblr.co/ZNUaDyd2xSDr
Filed under: BlackBerry tech phone 
January 7, 2013
Hypercritical: CES: Worse Products Through Software

siracusa:

Watching the CES coverage out of the corner of my Internet eye, I’m reminded of exactly how bad most hardware makers are at writing software. Mat Honan summed it up nicely last month: No One Uses Smart TV Internet Because It Sucks. Amen to that. But it’s not just TVs. Who really likes the…

Very astute analysis; but it must be noted that the sorry state of “apps” on TVs is not just the fault of the software, specifically in regards to speed.

One significant problem with embedded platforms that used to be focused on a single task, or group of tasks, that are trying to become general computing devices is speed. This can come from a range of factors, but the primary ones are: slow, low powered components; and an overly focused and optimized design.

The former is often related or caused by the latter: the hardware design is optimized for a single purpose, such as displaying video, and may be lacking the features needed for an app that needs to display an interface, connect to the Internet, communicate via YouTube’s protocol, and then display the video. In a TV the designers have most likely placed most of the resources into the DSP and data pipelines from the video inputs to the screen. A YouTube app would need these resources only for the last step; the steps up to that point would need to use the severely limited RAM and general CPU cores that are really only spec’ed for displaying the basic UI of a TV.

Couple these limitations with protocols designed for browsers, and software designed and written as quickly as possible, and you have the mess we are currently in.

(Source: siracusa)

9:56pm  |   URL: http://tmblr.co/ZNUaDybFhzDH
  
Filed under: ces tv embedded 
December 13, 2012
Mind the cracks (at Vigilucci’s Seafood & Steakhouse)

Mind the cracks (at Vigilucci’s Seafood & Steakhouse)

December 11, 2012
Passport to the future… (at Santa Fe Depot)

Passport to the future… (at Santa Fe Depot)

December 11, 2012
Catching a line out of here. (at Santa Fe Depot)

Catching a line out of here. (at Santa Fe Depot)

December 11, 2012
Aye aye Captain. (at USS Midway Museum)

Aye aye Captain. (at USS Midway Museum)

Liked posts on Tumblr: More liked posts »