Intel's CTO Justin Rattner stepping down

Intel's CTO and director of its labs Justin Rattner is stepping down to meet a requirement under the company's bylaws that employees cannot serve as corporate officers after the age of 65.

Rattner will, however, return to Intel at a later date in an as yet undetermined role after taking personal leave immediately to deal with a "pressing family matter," Intel said.

[ Keep up on the day's tech news headlines with InfoWorld's Today's Headlines: Wrap Up newsletter. ]

The company did not immediately announce a successor to Rattner, whose exit on account of the age limit would have been expected within the company. Intel Labs will report to Intel president Renée James until further decisions related to its leadership are made, the company said.

After Rattner's return, he and the management team will decide what role he will play, said Intel spokesman Chuck Mulloy in an email. "While we were certainly aware of Justin's age our management team will use this opportunity to evaluate how we organize our R&D efforts including Intel labs," he added.  

The company has found it difficult to make a large impact on the smartphone and tablets markets, which have been dominated by chips built around the ARM architecture.

Intel's new CEO Brian Krzanich admitted in May that the company has been weak in smartphones and tablets, but aims to improve by advancing chip and manufacturing technologies. Intel's main focus is to produce more power-efficient chips, as it also adds features for connectivity and security. Intel's upcoming chips based on its Silvermont architecture aim to outstrip ARM chips on both performance and power-efficiency.

Krzanich has thanked Rattner, who joined Intel in 1973, for "his leadership in creating one of the leading research organizations in the high tech industry", according to a statement from Intel Thursday.

Rattner was named Intel's first principal engineer in 1979, its fourth Intel Fellow in 1988 and was in the first group of Intel Fellows to be named Senior Fellow in 2001.

John Ribeiro covers outsourcing and general technology breaking news from India for The IDG News Service. Follow John on Twitter at @Johnribeiro. John's e-mail address is john_ribeiro@idg.com

View the original article here

Developers ramping up for Microsoft Windows Store apps

Developers are showing interest in building Windows Store (formerly Metro) applications with tablet-style functionality, but the platform is still in its early stages as far as building a base of apps.

Metro, a name that is no longer supposed to be used because of a trademark conflict, was introduced two years ago. Now, Microsoft is referring to these apps as Windows Store apps, bearing the Modern UI interface, complete with Microsoft's live tiles for accessing functionality. "We're just doing our first Metro Windows 8 commercial application," said Jeff Torkington, CEO of retailer software developer Ontempo.

Microsoft cites about 100,000 Windows Store apps, which would pale in comparison to the more than 975,000 Android apps in the Google Play store and the estimated 850,000 iPhone, iPad, and iPod touch apps in Apple's App Store. But Windows 8.1 looks like it will be a more appealing platform for users, which should boost Windows Store application development, said Wes Miller, analyst at Directions on Microsoft. "In general, the navigation is better," in version 8.1, he said. "Microsoft has made some of the right changes with [Windows 8.1]. It could be an interesting holiday season for sure." Microsoft has just begun offering a preview of Windows 8.1.

Microsoft also is leveraging XAML to try to make development easier, Miller said. Previously, the company focused on Web languages like HTML5 and JavaScript. "[With] their XAML architecture, they've got a lot better story on how you would build an app for Windows 8."

Developers thus far are giving the Windows Store application style mixed reviews. New to the Windows Store application experience, Kristofer Linnestjerna, a developer at NetClean Technologies, said he found himself confused by the platform when he took a look at it. He noted how different it is from the desktop. "It's made for touch," he noted.

Developer Robert Keiser, owner of Row Five Information Systems, has done some Windows Store app development. "It's very easy. The only problem that I have is if you program for the tablets, you have to rewrite some of the code, some of the front end, to make it work on the phone."

While developer Martin Bennedik, a freelancer in Frankfurt, Germany, has developed some Windows Store apps, he has not seen much interest in the platform from his clients so far. "They're just waiting to see where this is going." But Microsoft is making the application development process better for Windows Store, he said.

At the Achmea insurance company, developer Tom van de Meent has not built any apps for Windows Store yet but anticipates a need in the future. Thus far, there he has only seen "a little" interest in Windows Store apps from customers, he said.

This story, "Developers ramping up for Microsoft Windows Store apps," was originally published at InfoWorld.com. Get the first word on what the important tech news really means with the InfoWorld Tech Watch blog. For the latest developments in business technology news, follow InfoWorld.com on Twitter.

View the original article here

Build 2013: Microsoft renews its relationship with developers

Microsoft is more than an operating system company. It's a platform company.

That's the overall message from its Build developer conference this week. And if it's going to remain a platform company, it needs to keep developers on its side. With much of the developer messaging over the last year focusing on the new WinRT runtime at the heart of Windows 8, it's no wonder that many developers -- especially those building enterprise Windows applications -- were feeling a little left out. Build 2013 was Microsoft's chance to reconnect with those developers and to showcase new tools, technologies, and roadmaps.

[ Also on CITEworld: Here Are The Top-Rated Enterprise Apps In Google's Store | Stay on top of CITE: Subscribe to the InCITE newsletter. ]

Making WinRT more palatable -- and less central
WinRT remains an important part of Microsoft's developer story. It's the foundation for creating Windows Store apps, and it's where much of Microsoft's API attention remains focused. That's not a bad thing -- it's designed for the next generation of app development and for building smart endpoints for cloud-hosted services.

Even so, there's renewed focus on .Net. It's the heart of the server and cloud story, and if WinRT is about building endpoints for devices, .Net is about building services in the cloud and in the data center (and also for desktop apps).

So where did WinRT fall down over its first year? Firstly, it was designed to work with a limited set of use cases. That, combined with its strong sandbox, meant it was hard to build apps that worked together, and there were limited tools for connecting to external hardware and for displaying built-in help.

The Windows 8.1 refresh of WinRT begins to fix many of those issues, with improved tooling for handling communication with external devices (including Bluetooth connections, and for working with a range of USB inputs and outputs). It also introduces the concept of child security domains, which will allow applications from the same developer to communicate across the walls of the Windows 8 sandbox without using Microsoft's built-in contracts. Contracts remain the key to allowing communication between apps, giving users the ability to construct their own workflows between apps from many different developers.

Getting the evangelists out there
New features in WinRT are all very well and fine, but developer engagement is key to Microsoft's future. Recent changes at the top of its developer evangelism team are a hopeful sign, as are admissions that the company has failed to encourage developers to use technologies like Portable Class Libraries (a way of encapsulating common code so that it can be used across WinRT, desktop and server .Net, Windows Phone, and Web services).

Build put the evangelism team front and center, publishing email addresses and Twitter handles and showing demonstrations of how new tools and services would work in developers' own applications, not just in Microsoft's.

Another interesting note: This was the third Build conference, but the first to be held in the San Francisco Bay Area -- the heart of Google and Apple territory. (Prior to Build, Microsoft held a similar event called the PDC or Professional Developers Conference; the last time it was held in the Bay Area was 1996.) While Microsoft says it was a decision made around available space and hotel capacity, the choice of venue could also speak to the fact that Microsoft knows it needs to reach the large base of developers who are intrigued with -- and building for -- Android and iOS. Certainly Microsoft went out its way to show more than its own Visual Studio IDE, with cross-platform development tools like Xamarin used in many presentations, and keynotes showed Git being used to manage iOS code generated by the Azure mobile services platform.

View the original article here