Showing posts with label Interview. Show all posts
Showing posts with label Interview. Show all posts

Monday, March 4, 2013

The Engadget Interview: ARM president Simon Segars at MWC 2013

The Engadget Interview ARM president Simon Segars at MWC 2013

We met up with ARM president Simon Segars at Mobile World Congress to chat about the company's recent milestones -- 8-core big.LITTLE processors, the powerful yet efficient Cortex-A50 architecture (which we discussed with James Bruce last year), MediaTek's Cortex-A7 quad-core SoC (the first of its kind) and Samsung's octa-core Exynos 5 chip -- to name a few. Hit the break to watch our video and read the interview transcript.

Myriam Joire: Hi there, it's Myriam with Engadget and I am here with Simon Segars, the President of ARM. And we're here at Mobile World Congress in Barcelona and I wanted to talk to you a little bit about some of the things we've seen in the last few months. I mean, last time I talk to you guys it was with James after the multiple A50 announcements. And you know, obviously there's been a lot new thing since then including some octa-core processors and MediaTek announcing the first A7 quad-core. Let's talk a little bit about some of those new products.

Simon Segars: So I think what you're seeing there is breadth of different types of implementation that can be created around our cores. At one end, the A7 could be used for very low-cost devices. We're really excited about the volume, the size of the market opportunity that comes around that. And then at the other end of the spectrum, you've got big.LITTLE configurations, our 64-bit cores, which can take ARM into very high-performance computers. So I think what's really interesting is how many different types of end application can be built hitting different performance points and crucially different pricing points - just growing the breadth of the market that ARM can address.

MJ: So tell us a little bit: what is your vision in terms of the ARM group? I realize that you are providing technology that you license for people to create their own chips, right, but like you obviously have some direction that you provide along with that, you know, like a semi-conductor manufacturer who provides a data sheet as it were for using their chip. I'm sure you are also providing some advice to people who license your technology. How do you see these crazy octa-core that are made of four A15s and four A7s? How do you see that developing going forward? Are we going to see some other combinations of these cores?

SS: Well yeah, the say octa-cores... I wouldn't describe it as 'crazy,' of course.

MJ: I meant that in a good way, obviously.

SS: Yeah, I think you kind of hit it on the head there. We're providing technology that can be used in multiple different configurations. So at one end, we have very power-optimized cores like the A7. At the other end, very high-performance cores like the A15 and A57 in the future. That gives our partners the flexibility to build different configurations to hit different price and performance points. We don't give a lot of guidance on what the right answer is because we really want to leave that up to the market, up to our customers and their customers to work out what the right combination is. Really what we're focused on is the flexibility of the way you can put all these building blocks together and try to simplify that as much as possible.

MJ: Right, so have I see in front of you, here one of the Alcatel, I believe it's the Scribe?

SS: Yeah, so this one happens to be branded TCL. This has got the quad-core MediaTek chip in, the quad-core Cortex-A7 MediaTek chip in.

MJ: So that was the first quad-core A7 chip, right?

SS: Yes, I believe so.

MJ: And how is that significant do you think in terms of market right now? Obviously the price point is pretty amazing.

SS: Yeah, and I think that's really the significant thing. The level of performance that you get in that chip, they've integrated into their graphics, and video, and the modem. So it's a very highly integrated SoC with a quad-core A7, which is delivering a lot of performance. And in that quad configuration, depending on how many of the cores are switched on at any moment in time, what the frequency of voltage is set at, then you've got a very wide kind of dynamic range of performance and power that you can choose between depending on the complexity of end application that you're trying to run at any moment in time - so very flexible performance and highly integrated and a very low cost point. I think it's going to mean that we'll see some really useful and interesting smartphone being produced at very low cost points - sub-$100 - which is going to enable us to address very large developing economies.

MJ: So obviously with quad-core becoming affordable, the next question is, you know -- and octa-core coming to life with these, you know, combinations of core types being built into the same chip -- where do you see this going? Are we going to, ten year from now, have these like 16 core or like multi-core devices that are going to be prevalent or do you think that from a software engineering point of view it become a challenge and it will kind of top off at a certain comfortable level. You know the PC market for example in terms of Intel architecture seems to have comfortably settled around dual core. Do you think there is something like that is going to happen? What is your prediction in that area? Obviously you don't have control over that, right?

SS: Yeah, I mean I think what you see today, having eight cores on the same die seems like, to use your language, crazy. I mean it's a lot of processing capability in a phone, and on one level it is crazy to think, "Well, what is all that going to get used for?" But the great thing about phones is the fact that it's a very open platform. Developing software is very easy, very low cost; and as you put all this performance in, somebody will think of something to do with it. So eight cores seems like far more in the land of compute power today. Will we see 16, 32 in a few years time? I think two things are going to govern that. Basically the drive of Moore's Law driving cost down meaning that you can put all of those transistors in at very low cost. A few years ago having a quad-core in 28 nanometer at very low price point seemed just unrealistic. But with, you know... technology always gets cheaper, and it's amazing what can be done, and MediaTek have demonstrated that. So overtime I'm sure you'll see more and more cores. And there is a limit to how much parallelism you can get out of any one application, but I think you'll see the different processors being used for different tasks in parallel. Where the limit is of that I don't know. I mean when you think back, you know, the iPad is only three years old. Smartphones themselves are a relatively new product category, and I don't think we're at the end of people just working out what they can be used for by any means.

MJ: No, there's no doubt. In terms of really low power, high efficiency, low compute power ARM cores like for example what's in a device like the Pebble for example, what needs to happen in that area? Do you think there are some significant breakthroughs coming up?

SS: Well I think a lot of the technology building blocks are there. I think some of the chips we're going see built around very small, very low cost micro-controllers integrated with sensors. Again, I think we're kind of at the tip of that, and again, it's made possible due to the technologies all coming together. And building a chip to do that kind of thing is much less expensive than building a chip to do an eight-core application processor. So I think you're going to see a lot of new device coming out with people using these building block in different ways. And I think it's going to be pretty interesting to see what people do. And then, with low cost connectivity to your phone, and having your phone control that or aggregate the data and interact with cloud services, I think it's going to be pretty exciting to see what people think up, what the end applications are that never have been imagined before.

MJ: Yeah, I absolutely agree. Well listen, thanks for your time, Simon. It's been lovely getting your insight on, you know, some of the kind of forward vision towards what ARM can bring. I mean, you guys are pretty much ruling the world right now so it's an exciting time.

SS: It is an exciting time. Again, from our perspective it's about great technology and in enabling people to build all these exciting products. You know, we don't have a monopoly on great ideas for all of this. What's great is how many users can just interact with technology and build end devices. It makes for a fun time.

MJ: Great. Well thanks for you time again.

SS: Thanks a lot.

MJ: Cheers.


Source

The Engadget Interview: Jolla CEO Marc Dillon at MWC 2013

The Engadget Interview Jolla CEO Marc Dillon at MWC 2013

Jolla launched its Sailfish SDK at MWC 2013 and we got the chance to chat with CEO Marc Dillon about the company's history and find out how things have been coming along with Sailfish OS since our hands-on late last year. We also discussed the time frame for Jolla handsets (still on track for H2 2013) and what the Sailfish SDK brings to the table for developers today. You'll find a full transcript of the interview along with our video after the break.

Myriam Joire: Hi there! It's Myriam with Engadget and I'm here with Marc Dillon, the co-founder of Jolla at Mobile World Congress 2013. Hi Marc, how's it going?

Marc Dillon: Hi. Oh it's great. It's been a great conference.

MJ: Awesome. So big announcement this week for you guys with the SDK, right?.

MD: That's right, we launched the Sailfish SDK. It's at SailfishOS.org

MJ: Awesome. So listen, before we get talking about that, tell us a little bit about the history of where you guys came from. I know it that it kind of all more or less started with the MeeGo team at Nokia. Is that correct?

MD: Yeah, that's right. I was in San Diego at Nokia Product Creation Center in 2001 and had started working on different products, and in 2005 I saw where the future was going... It was this open operating system. And it's also Maemo, MeeGo -- everybody hears about MeeGo now, but that was actually... N9 was the eighth product that we had released. N900 was one that was a really iconic product before that, and we had heard the whole time that having something different is really, really important. And it's even more critical today; there's like a couple of dominant players that are in the market. And when we started the initiative, we knew that there was a need for change and a need for innovation and a need for people to have a different choice, for consumers to be able to buy something a bit different and is offering them different options and offering a platform for innovation. So we really took that to heart, and we took the best people we could possibly get, and people that share a vision with us that are wonderful people to work with and the best talent in the world. So, We started this thing and we've been really well received everywhere we go. This conference, we're treated like rock stars here. And it's really a warm feeling to get so much attention for us just being ourselves and doing the best we can and making the best product that we can. So once again, this is the time in mobile to have innovation. This is the time for something new to happen. We're at a crossroads, and it's either 'we're not going anywhere,' which is the current state, or 'we have to take a new choice. I think we have a great choice with Jolla and Sailfish.

MJ: Alright, so Marc tell us a little bit about the SDK and what we can expect in term of timeline going forward with potentially a release of the OS.

MD: So we got a lot of feedback on the SDK. We ran it through some community members and got some feedback previously, and I believe because we took our time we were able to come out with something that's getting really good feedback... it's really well polished. We're offering a lot of power for application developers. The QT framework makes it really easy to create powerful applications, or to take an application you have for a different platform and be able to port it with a UI that has the features of Sailfish. Like, we have this pulley menu that allows people to perform actions without looking at the device. They can just feel the things that they... the menu choices that they have, and it also doesn't take screen real estate. The ability to export multitasking to the home screen so that... Like you have music controls that are on the home screen of some devices, but it's not that easy for any application developer to use. So our multitasking interface does these kinds of things, and the ability to create these all with the ambience that we have on the Sailfish operating systems. SDK is out now. It's open for application development. And one final thing about that: we're getting feedback from guys that haven't written code for a while, and now they're saying, "Wow, I want to get back and write code." That's one of the warmest things that we can get.

Next steps: so everybody wants to know "When do you get the device? When do you get the device?" We don't want to release before it's ready. This is out debutante moment so it's always a delicate balance - when you launch, and when you start to sell. So we're still looking at second half of the year. People say, "Why isn't it summer?" It's like, well we realize summer is different in Scandinavia than it is in Asia, is it the 21st or 22nd of September? But the target's still to be in the Christmas market and to be in for Chinese New Year, and we're going to launch the device with enough time to be able to build the logistics and get the demand, and be able to sell the devices. And we're spearheading with this first Jolla device. So we want to show our capabilities and show that these guys can create a world-class and very unique and differentiating product, and we want to shake the market. So we've seen the same thing from the same two big players for a long time, and like when I got here there's a billboard that somebody's reinvented mobile with exactly the same operating system and user experience that everybody else has. So we're really here to shake things up, and we've gotten a lot of warm feedback from that.

MJ: That's fantastic. You are obviously are working closely with some Chinese manufacturers. I know you can't speak to that at this time, but are we looking at actually getting not just in the OS but getting devices by the end of the year then?

MD: Oh absolutely, absolutely. We're going to be selling devices second half of 2013.

MJ: I think you are primarily targeting China right now, is that correct?

MD: We're starting in Finland; you have to sell at home, and then we're moving into the China sales, and then we're going to be penetrating Europe. Also, we have an expansion plan for other tets. The most important thing is to get a wonderful product out, and then we'll sell it.

MJ: Make it delightful, polish it and even if it's not fully featured but it's simple, easy, and people love it, then go from there right?

MD: What you have works as best as possible and as magically as possible.

MJ: So if you are a developer you can just go down to the Jolla website and get the SDK right?

MD: That's right, SailfishOS.org.

MJ: And there is an emulator?

MD: Yes, there's an emulator so you can see how the applications work, and all of our UI features are available as UI components. Actually you can develop applications that have all these different UI components and different elements and use the power of the OS.

MJ: Great. Well listen, it's been great talking to you Marc and getting a overview at Mobile World Congress with Jolla and a bit of a history as well, so thanks for your time.

MD: And we love Engadget.

MJ: We love you guys too.

MD: Alright, thank you.


Source

Saturday, March 2, 2013

The Engadget Interview: Chul Bae Lee, VP of LG's mobile design lab at MWC 2013

The Engadget Interview Chul Bae Lee, VP of LG's mobile design lab at MWC 2013


We first met Chul Bae Lee -- VP of LG's mobile design lab -- in Seoul last fall and were lucky to spend a few minutes with him in the company's booth at MWC. LG's flagship Optimus G Pro made quite the splash in Barcelona but looks rather different from the Optimus G. We asked Mr. Lee to walk us through the design process behind the company's new superphone. He mentioned that LG offers two high-end product lines, one focused on premium design (Optimus G), the other on high-performance design (Optimus G Pro) and shared a diagram with us to illustrate this (after the break). The new handset puts an emphasis on ergonomics rather than style by featuring a comfortable and a friendly shape, with soft edges and round corners.


We discussed the extremely narrow display bezel, striking RGB notification ring around the home button, recessed camera lens and IR blaster (for the QRemote functionality). Mr. Lee explained that the placement of the buttons around the Optimus G Pro was carefully chosen to minimize interference with the power / lock key -- this includes the QNote button, which can be remapped to invoke other apps, and even double as a shutter key. We then talked about the new Optimus F series, which blends the design DNA of flagship devices with performance specs (like LTE) at a more affordable price, and the Optimus L II line, which offers unique designs for specific markets (single SIM in Europe, and dual-SIM in Latin America). Hi the break for our video interview and to check out the aforementioned design diagram.


The Engadget Interview Chul Bae Lee, VP of LG's mobile design lab at MWC 2013


Source

Saturday, February 16, 2013

The Engadget Interview: NASA astrobiologist Dr. David Morrison talks asteroids and the end of the world

The Engadget Interview NASA astrobiologist Dr David Morrison talks Asteroids and the end of the world


Between the recent meteorite strike and our close call with 2012 DA14, we've all been thinking an awful lot about potential impact hazards from the heavens. Thankfully, however, during our visit to NASA Ames last week, much of our fear was put to rest by astrobiologist Dr. David Morrison, the scientist who coined the word "cosmophobia" to describe the fear of external impacts on Earth. Morrison, who recently served as one of the go to sources for science fact (and common sense) in stories about the 2012 Mayan Apocalypse speculation, spoke to us about the likelihood of major asteroid impact on Earth -- and what we can do to stop it. Hang around after the break to check out our full interview with the good space doctor.



Source

Saturday, January 26, 2013

The Engadget Interview: Richard Collins, head of Ubuntu mobile products

DNP The Engadget Interview Richard Collins, head of Ubuntu mobile products

Don't ask, don't get. That's why we rang up Canonical and requested an early build of Ubuntu for the Galaxy Nexus. (Politely declined.) Next, we asked if maybe the company could speed up development of its dual OS solution for Android, since we're really looking forward to it. (Funny looks.) Finally, we wondered if there was any possibility of dropping by the London HQ and interviewing someone in charge. ("Come on over!") We promptly found ourselves sitting across a desk from Richard Collins, who left the Symbian Foundation 18 months ago to work at Canonical, and who has a very firm grasp of how Ubuntu is going to be hauled into the mobile era. He explains everything after the break, so if you have a big OS-shaped gap in your belly, or if you're just intrigued to hear the proposition of a new player, read on.

DNP The Engadget Interview Richard Collins, head of Ubuntu mobile products

How is Ubuntu on a smartphone really the same Ubuntu we know from desktop PCs?

It's the same code base, with our Unity UI, adapted to provide a very particular experience according to the device it's running on. That makes it straightforward for developers to say, "here's an Ubuntu application that I know works brilliantly on the desktop, I only have to adapt it using the tools that Ubuntu provides in order to make it work on a smartphone."

But legacy desktop apps will still have to be ported?

Legacy apps will have to be adapted. They'll need to compile on ARM processors, but that's not a significant amount of work. When we start launching products, we'll include an SDK which will allow developers to build apps which work on both the smartphone and the desktop interface.

Since Android is also Linux-based, is there any plan for Ubuntu to run Android apps?

Many Android developers already use Ubuntu as their desktop OS and we have a very close affinity with them. We intend to encourage them to make their Android applications run on Ubuntu, but we won't engineer any middleware for running Android apps. Developers are intelligent and capable enough to make their apps run on our devices. We have an active initiative right now to directly help them achieve this. [See More Coverage below.]

Will you have a full app store ready for the launch of your smartphone?

In terms of our first go-to-market product strategy, the intention is not to have an application store full of ready-made applications that are there to download. We have a very definite approach in terms of addressing an important part of the market where users are primarily interested in being able to use a core set of applications.

"The intention is not to have an application store [at launch]"

You're saying people interested in low-cost phones don't need lots of apps?

At launch, we'll have the capability for a mobile app store, but at this stage we don't believe it is essential for the entry-level smartphone market we're targeting. However, we won't just be saying "there's your basic applications, that's all you're going to need." Our strategy includes giving carriers and manufacturers ways of delivering services in conjunction with us -- we plan to give them more influence.

Do you want people buying your entry-level phone, in China for example, to know the Ubuntu brand?

Yes, of course. I want them to associate Ubuntu with a very interesting, relevant and enjoyable experience. The challenge for us is to take the success we have with developers, with enterprises, and take that into the consumer market.

DNP The Engadget Interview Richard Collins, head of Ubuntu mobile products

Are you going after the same market as Mozilla's Firefox OS?

[Mozilla] has a very particular type of technology. We believe that a rich user experience requires a native capability -- it can't be entirely addressed by a phone that only runs web applications. Web apps sit on servers in different parts of the internet, so it's hard for them to interact and share information.

You're also going up against Nokia's Asha series running on S40...

Nokia's S40 is only defined as being a low-end smartphone platform. Ubuntu is engineered to run across different devices, and it's engineered to scale up to higher-end devices.

What advantages do you have over Android as a smartphone OS?

With Android, it's implicit that if you want to run Google services then there's a levy associated with that. Our model is entirely different. We're working with industry partners who want to have more influence over the way services are provided to end users. We won't try to lock people into licensing our services.

Windows already straddles the divide between x86 and ARM. Has Microsoft stolen a march on you?

"Microsoft generates uncertainty and conflict..."

We compete with them, in that sense. There are ways in which Windows is a very costly OS to build hardware on. We have an alternative approach that is more software-based, more collaborative, more open, and offers more promise for developers who want their apps to run on desktops, phones, TVs and so on.

Microsoft generates uncertainty and conflict in the way it's trying to gain market share. They're in conflict with their own hardware partners. There's a very different stance in the way we propose to work with people.

DNP The Engadget Interview Richard Collins, head of Ubuntu mobile products

Many people are waiting on mobile Ubuntu because they want to see boundaries pushed and the market disrupted. Won't your first phone jar with those types of users?

Not if we're clear about where we want to take Ubuntu. We're planning to very quickly follow our initial launch with a high-end converged device, which will have high-performing system components that will allow Ubuntu to run as a desktop OS when docked. It'll also have full access to the Ubuntu Software Center. So we need to be clear about our roadmap -- we don't have tunnel vision around low-end products.

Speaking of which, are you okay with how long it's taking Ubuntu for Android to come to market?

It takes a long time to release a software-based product and turn it into a hardware-based product. But I can tell you that you might not have much longer to wait before you see something on that side.

DNP The Engadget Interview Richard Collins, head of Ubuntu mobile products

You're not going to be like Microsoft or Google, but how will you make money?

The simplest model would be per-unit licensing. Then there's also the fact that hardware manufacturers and carriers don't want to focus on software. They want people like us to manage that on their behalf and it might be possible to commercialize that.

So you'd directly look after the software -- including updates, for example?

Yes, absolutely. There's no fragmentation in terms of the way we will progress our OS. Each update will come on a six-monthly basis and manufacturers will be able to rely on that. They'll be able to deliver their services without worrying about OS versions.

How would those services run regardless of OS version?

Because often those types of services will be web-based. With Ubuntu, web applications can feel more like part of the main operating system. We can make them feel very native.

Will you try to advertize on mobile Ubuntu?

That has to be done in conjunction with carriers and manufacturers. But part of what we're doing with the OS is providing direct access to services that the user has subscribed to, and putting them in the main UI -- like with Amazon.

Where do you want to be in two years' time?

I want to be shipping in mass volume, in the millions of units, and for Ubuntu to be recognized globally as one of the major platforms. Our analysis says there's the opportunity to gain a 7-8 percent market share by 2016. There's a window of opportunity for a new player to capture that kind of share.


Sourse

Saturday, January 12, 2013

Live from the Engadget CES Stage: an interview with Canonical's Mark Shuttleworth



Canonical's Mark Shuttleworth has a long history of disrupting the industry, and this year's CES is no different. The entrepreneur / space tourist will join us to day to discuss his company's swipe at the smartphone space.

January 11, 2013 7:00 PM EST

Check out our full CES 2013 stage schedule here!

$LAB.script("//live.huffingtonpost.com/hpl-embed.js").wait(function() { HPLEmbed.load({ targetId: 'HPLContent', app: 'hplive_player', width: '550px', height: '309px', streamType: 'live', autoPlay: 'true', thumbnail: 'http://cp171154.edgesuite.net/SMIL/engadget-live-from-ces-2013-screen.jpg', sources: { 'video/hds': 'http://aolhdstreaming-f.akamaihd.net/z/engadgetcesremuxing1_1@97213/manifest.f4m', 'video/hls': 'http://aolhdstreaming-f.akamaihd.net/i/engadgetcesremuxing1_1@97213/master.m3u8' }, comScore: { c4: 'us.engadget' }, freewheel: { plugin_freewheel: 'http://adm.fwmrm.net/p/aol_osmf_live/OsmfPlugin.swf', freewheel_namespace: 'http://www.freewheel.tv/config', freewheel_adManagerUrl: 'http://adm.fwmrm.net/p/aol_prod/AdManager.swf', src_namespace: 'http://www.freewheel.tv/config', src_adManagerUrl: 'http://adm.fwmrm.net/p/aol_prod/AdManager.swf', src_networkId: '174938', src_playerProfile: '10886:aol_as3_prod', src_serverUrl: 'http://2a86.v.fwmrm.net', src_siteSectionId: '151098', src_sitSectionIdType: 0, src_videoAssetAutoPlay: true, src_videoAssetDuration: 5000, src_videoAssetId: '50915315', src_videoAssetIdType: 0, src_videoAssetNetworkId: '10886', src_siteSectionNetworkId: '10886' }, AMAConfig: 'http://ma180-r.analytics.edgesuite.net/config/beacon-3967.xml' });});

when.eng("eng.perm.init")

Live from the Engadget CES Stage: an interview with Marvell's Winston Chen

Live from the Engadget CES Stage an interview with Marvell's Winston Chen


Marvell's been all over the place this week, showing of some the best technology of 2013 it'll be helping to power. We'll be sitting down with the company's vice president of the smart home, Winston Chen, to talk set top boxes.

January 11, 2013 6:30 PM EST

Check out our full CES 2013 stage schedule here!

$LAB.script("//live.huffingtonpost.com/hpl-embed.js").wait(function() { HPLEmbed.load({ targetId: 'HPLContent', app: 'hplive_player', width: '550px', height: '309px', streamType: 'live', autoPlay: 'true', thumbnail: 'http://cp171154.edgesuite.net/SMIL/engadget-live-from-ces-2013-screen.jpg', sources: { 'video/hds': 'http://aolhdstreaming-f.akamaihd.net/z/engadgetcesremuxing1_1@97213/manifest.f4m', 'video/hls': 'http://aolhdstreaming-f.akamaihd.net/i/engadgetcesremuxing1_1@97213/master.m3u8' }, comScore: { c4: 'us.engadget' }, freewheel: { plugin_freewheel: 'http://adm.fwmrm.net/p/aol_osmf_live/OsmfPlugin.swf', freewheel_namespace: 'http://www.freewheel.tv/config', freewheel_adManagerUrl: 'http://adm.fwmrm.net/p/aol_prod/AdManager.swf', src_namespace: 'http://www.freewheel.tv/config', src_adManagerUrl: 'http://adm.fwmrm.net/p/aol_prod/AdManager.swf', src_networkId: '174938', src_playerProfile: '10886:aol_as3_prod', src_serverUrl: 'http://2a86.v.fwmrm.net', src_siteSectionId: '151098', src_sitSectionIdType: 0, src_videoAssetAutoPlay: true, src_videoAssetDuration: 5000, src_videoAssetId: '50915315', src_videoAssetIdType: 0, src_videoAssetNetworkId: '10886', src_siteSectionNetworkId: '10886' }, AMAConfig: 'http://ma180-r.analytics.edgesuite.net/config/beacon-3967.xml' });});

when.eng("eng.perm.init")

Live from the Engadget CES Stage: an interview with Node's George Yu



CES 2013 has been a big week for crowdfunded success stories. Node is amongst those whose Kickstarter campaign has resulted in a real, salable product. We'll be discussing the modular iPhone sensor and what it's like to be a small company in a place like CES with founder George Yu.

January 11, 2013 7:30 PM EST

Check out our full CES 2013 stage schedule here!

$LAB.script("//live.huffingtonpost.com/hpl-embed.js").wait(function() { HPLEmbed.load({ targetId: 'HPLContent', app: 'hplive_player', width: '550px', height: '309px', streamType: 'live', autoPlay: 'true', thumbnail: 'http://cp171154.edgesuite.net/SMIL/engadget-live-from-ces-2013-screen.jpg', sources: { 'video/hds': 'http://aolhdstreaming-f.akamaihd.net/z/engadgetcesremuxing1_1@97213/manifest.f4m', 'video/hls': 'http://aolhdstreaming-f.akamaihd.net/i/engadgetcesremuxing1_1@97213/master.m3u8' }, comScore: { c4: 'us.engadget' }, freewheel: { plugin_freewheel: 'http://adm.fwmrm.net/p/aol_osmf_live/OsmfPlugin.swf', freewheel_namespace: 'http://www.freewheel.tv/config', freewheel_adManagerUrl: 'http://adm.fwmrm.net/p/aol_prod/AdManager.swf', src_namespace: 'http://www.freewheel.tv/config', src_adManagerUrl: 'http://adm.fwmrm.net/p/aol_prod/AdManager.swf', src_networkId: '174938', src_playerProfile: '10886:aol_as3_prod', src_serverUrl: 'http://2a86.v.fwmrm.net', src_siteSectionId: '151098', src_sitSectionIdType: 0, src_videoAssetAutoPlay: true, src_videoAssetDuration: 5000, src_videoAssetId: '50915315', src_videoAssetIdType: 0, src_videoAssetNetworkId: '10886', src_siteSectionNetworkId: '10886' }, AMAConfig: 'http://ma180-r.analytics.edgesuite.net/config/beacon-3967.xml' });});

when.eng("eng.perm.init")

Sunday, December 23, 2012

Interview: How Linux reads your fingerprints, helps national security

Gunnar Hellekson has many awesome-sounding job titles.

He's the chief technology strategist for Red Hat's US Public Sector group, where he works with government departments to show them how open source can meet their needs, and with systems integrators to show them what they can do to provide the government with what it needs.

He's co-chair of Open Source for America, which campaigns for software that has been funded by the tax-payer to be open sourced, so that all Americans can benefit from it. He's also on the boards of the Military Open Source Working Group, Civic Commons and the SIIA Software Division.

He's a clever chap with the ear of some pretty influential people, so we sar down with him for a chat.

Linux Format: First thing: Is the US government in favour of open source, or does it see it as stealing food from Microsoft's children?

Gunnar Hellekson: The government was actually an early user of open source, going back to 1978. You had the US government funding the development of things like the BSD TCP/IP stack; the ping tool was developed by the army research lab, and at some point in the 90s people started to wonder more, look more carefully at open source; and the government started passing rules like the Clinger-Cohen Act of 1996, which formalised the rules around IP acquisition. Suddenly, there were rules, which meant that there were concerns about whether people were following the rules or not.

When we had no rules, open source made sense. When the rules came in, people started to ask: "Wait, can we do open source?" And it wasn't until about 2003–4, when the Department of Defense [DOD] and the Office of Management and Budget said: "Actually, open source is fine. Don't worry about it, open source is just like any commercial software licence."

The irony of this is that while the slow gears of policy were moving, the Department of Energy and DOD, and the NSA [the National Security Agency] were all releasing source code out to the public, uninterrupted. So to say that the government has one position or another on open source is not only inaccurate, but it's impossible to describe, because the government is 12 million people. Some of them are great open source advocates and some of them aren't.

LXF: Didn't the NSA come up with SELinux, which is in the kernel now?

GH: Security Enhanced Linux, in 2001. And the reason why they did that is the classic story, right? They did it for a number of reasons. First, they wanted to relieve themselves of the technical debt of having developed the technology. If they had developed it and kept it to themselves, only they could have maintained it, and that's expensive.

So by putting it out to the open source community, into the Linux kernel, they could get some help, which was nice for them.

More importantly, the part of the mission that everyone forgets is that the NSA is also responsible for protecting the country's information infrastructure and making commercial products more secure. And so by making SELinux highly available – it's in every copy of Linux – it's actually improved the overall security of the country. So there were a bunch of reasons to do it.

LXF: What does your role with Red Hat entail? Are you trying to push this agenda to various government departments?

GH: In part, that's what it is. The best way to describe my job is telling the government what's happening in open source, and telling open source communities what the government is after.

LXF: Right, kind of like a community manager for those 12 million people who work in government?

GH: More like a hostage negotiator.

LXF: Have you seen any of the IT projects that are going on in the UK? Like the NHS IT project, for instance. That's an enormous project, and a black hole for tax-payers' money. Do you think there's anything inherent in a government that makes them think along such large lines?

GH: Well that's interesting, because in the United States we're heading in the opposite direction. The federal CIO has declared an end to large procurements, so rather than having one $500 million contract, we have 100 $5 million contracts. And it was the reason for the change, not just because it's more efficient and because there's less risk, but also because the current procurement system can literally not keep up with advances in technology.

At the DOD, the lead-in time for a top-level program takes 48 months to get from initiation to requirements. You haven't even put a bid out, you haven't even made a tender yet, but you've spent four years developing requirements. And in those four years, the entire world has changed. And so it's just not practical to run an IT project like that.

Open government

And so, in 2012 in the Appropriations Bill for the Defence Department, Congress ordered the DOD to come up with alternative acquisition strategies specifically for IT to fix this problem. They were asking for things like continual involvement of the user, an iterative, evolutionary approach... and what they were describing was that they wanted an agile IT project.

And so, subsequently, we've seen this model all over the government, with a more iterative approach and projects broken down into tiny chunks.

LXF: Our secretary of state has said that should happen, that you should break down contracts in to small chunks, but as yet, that's all that has happened: that he has said that it should happen.

GH: Well, from what I understand, since the early 2000s the UK Government put out a number of very large contracts with very long performance terms, like 10-year engagements.

I'm thinking specifically of the MOD, which visibly took most of its IT organisation and threw it up for ransom to a consortium of five companies... what were they called? Fujistu Siemens, those kinds of people. And you're getting exactly what you paid for, right?

Not only was it a huge amount of cash up-front, but also the government has no negotiating position, because any change they want to make translates into more money that you have to pay the consortium.

And so that's what agile IT combats: not only is it more iterative, but there's more competition for each iteration.

LXF: Do you see that agile, more responsive development... do you think that's a key advantage of open source in big government projects, as compared with open file formats, for example.

GH: Yeah, so, what's more important? Open source or open standards, right? I think they both solve a different set of problems. When you have an open standard, you're creating a market. You're creating the opportunity for many people to perform the same task.

So if I'm using a standard like, say, IMAP for email, then I can ask any number of IMAP servers, and I don't have to change clients every time I change my server, because if I'm on IMAP I can compete all my IMAP servers against each other, which will drive down the cost.

With open source, what I'm giving myself is a vendor of first resort or of last resort, and I always have that option. So that even if... you can have an open standard and if only one company implements it you're just as locked-in as you were before.

But with open source, you always have an alternative. I can use the code unsupported, or I can find a clever open source hacker who can support it for me.

LXF: What about the argument that free software is crowding out commercially-made software, and stopping companies from making money?

GH: The government has always been concerned about... the Clinger-Cohen act, passed in the 90s, created a preference for commercial software in government, and what they meant by that was software that the government didn't make. What they wanted to do was to make sure that the government didn't end up doing itself something that could be done more effectively by the private sector.

So the rules say that before you go and build something, you have to look outside and make sure that nobody has already built one. So when government starts writing software, there's an immediate gut reaction that it's duplicative.

But, of course, there are cases where it makes sense for the government to be writing its own software, and Accumulo is a great example because Accumulo has features that didn't exist in any other project at the time.

The way they do charting, the way they do document storage, the way they do cell-level security, so I can determine for each individual piece of data who's allowed to talk to it or not. These features were unique to the Accumulo project, and the government did the right thing, because they open-sourced it.

And when you open-source it, it becomes a commercial item, because it's released under a commercial licence, which is the Apache licence. So it's under the Apache licence, which means that it's a commercial product. The senate is rightly concerned about crowding stuff out, but we have a case where it's not government-owned software anymore.

LXF: And rather than crowding out private enterprise, they've actually created a market for support services.

GH: There's a company called SQRRL, which closed its first round of funding a few months ago, wanting to be the Red Hat for Accumulo. So, here's an example of a government technology transfer that works. So I think that the senate concerns are valid, but in this case they're conflating government software with government-produced open source software, which are two very different things.

LXF: The other thing that we're always pushing as an advantage of open source is that it costs less, because you're not paying a licence fee. Is that an important factor, or is it irrelevant at government level? Because I imagine that the number of hackers you'd need to employ would be pretty expensive.

GH: Writing software is expensive, and it's even more expensive to maintain software. We've spent a lot of money writing code. Cost is often a factor in open source software for all the reasons you mentioned. It's often cheaper.

But I always caution people against saying that open source is always cheaper, or always more expensive, because although there are a number of advantages to the open source process it's always possible that a project is going to be very expensive to run.

Or bring it to your IT shop. So when we talk about saving money, it's important to look at what purpose you're using it for. So the economic value of open source is going to be very specific to which software project we're talking about.

All that said, there are a number of second-order effects to using open source that are definitely advantages.

And it's stuff like: you can always compete for maintenance; you can always fix it if it breaks; and the most important thing for me is that it gives you access to a whole bunch of innovation that would not be available to you otherwise.

LXF: Which you don't get if you're locked in to a ten-year contract with Capgemini.

GH: The way we look at it is this: take your favourite software vendor and draw a circle around all those developers. In the world, are there more smart people inside or outside that circle? And that's true of any organisation.

If you're buying from a proprietary vendor, your software is only as good as how many smart people they can hire, which doesn't seem like a very good risk proposition to me. You want to use software and software vendors that have access to as many smart people as possible.

Open government

LXF: How's Red Hat doing?

GH: Well great, you just saw the press today. I heard the number three and I heard the number 12, but we're one of the few pure software companies to go over $1bn revenue.

One thing that's exciting for me about Red Hat right now, I love working for Red Hat, I love my job, I've been here for seven years. And I've never been as excited about anything as I am about OpenShift.

I know it's not on your beat, but having an open-source platform for a server is a complete game changer for my customers to the way they plan on procuring software. Giving them a way to control all of their technology going forward from that point of view is to start looking at platforms as a server.

And I'm going to be blogging a bunch about that. It's a huge deal, and it's really exciting.

LXF: Is that related to OpenStack?

GH: It lies on top of OpenStack. So OpenStack will give you a VM; OpenShift will let you say, "give me a Python environment, give me a PHP environment and put WordPress on it".

And then it will automatically create these things we call cartridges; cartridges for Mongo, PHP, Perl, Ruby, Java... so all the building blocks have already been laid out, already secure. And you're not even looking at the virtualisation layer.

In fact, you don't even know where the stuff is running. As a developer, all you're working with is Git. You write your code, then you do a Git push, and once you've pushed it, it's running inside the environment. It's really cool.

LXF: It sounds kind of like Ubuntu's Juju thingamibob, the cloud as a service product they launched earlier this year.

GH: I sat in front of a Juju session two days ago, and I'm still trying to figure out what it is. But Juju is coming at a similar problem from a different angle. OpenShift has a bunch of other stuff. Juju is a way of helping sysadmins; what OpenShift does is, it lets you create these Linux containers so you can confine applications inside. One container, one jail, and nobody can talk to anybody else.

We've got it running on EC2; it'll spin up VMs, then spin up containers within those VMs, so we can get 400 customers on one box, which is awesome. OpenShift is a way to manage who owns what.

The way we make money is that you can spin up three cartridges for free, but if you want extra stuff, if you want management tools and all the rest of it, then you sign up for the service and you pay for additional space. The navy are looking at it, the air force...

LXF: Did you see that Linux is being used in one of the US navy drones now?

GH: Uh-huh. The Firescout. We actually made fun of that article. If you look at the timeline of government use of open source, you see that there are all these data points going back to 1978 all the way up to 2012, there's this mass of articles all calling for advocacy and adoption of open source projects.

Then you get this one $26 million contract to put Linux on a Firescout, which is like an insignificant dot, right? The thing we were talking about in the session was, "when do we get to stop talking about open source in government?"

What I said was: "Every time we talk about open source being a big deal in government, that's us not winning". We want open source to be totally unremarkable. It should just be part of the infrastructure.

And so when someone is surprised that the US government is using Linux... you know, governments have been using Linux for a very long time. The government has been contributing to the Linux kernel since at least 2000. It's kind of funny to see people say "Ooh, Linux is in the Firescout". It's as if it's going to force cataclysmic changes in the GPL. No! It's not a cataclysmic event, it's a contract.

LXF: Are there any particularly awesome Red Hat adoptions in the US government?

GH: Sure. The FAA, their traffic flow management system, since 2001 has been running on Linux. So, every time you take a civilian flight in the United States, there's a Linux workstation managing it. US Census is a Red Hat user.

Every week, the government puts out employment numbers. If they are even five minutes late announcing it that is an apocalyptic event on Wall Street. They're running Linux.

The Patent and Trademark office, what else... the national weather service, every weather forecast comes off a Linux box.

Oh, the FBI, this is kind of fun. Every time you see a fingerprint check or a background check on somebody, that is all going back to a system that is running on... I think they're using every Red Hat product that there is.

They have 16 million records, and they run every background check, every fingerprint, all the biometric data, and when you crossed the border they took a fingerprint, right? That fingerprint went back to a data centre running all that stuff and came back in under 15 seconds to make sure that you weren't flagged. That's all Red Hat.


View the original article here

 

© 2013 PC Tech World. All rights resevered. Designed by Templateism

Back To Top