|
Microsoft just raised the bar in the tablet market. Unless you’ve been living under a rock for the past 24 hours, you know that Microsoft finally revealed their own tablet device, dubbed “Microsoft Surface”, built independently from its traditional OEMs. This new Microsoft Surface comes in two flavors, running either Windows 8 Pro or Windows RT.
The Microsoft Surface devices are very new and there are still some hardware features we do not know about yet, but the operating systems powering Microsoft Surface are not new. The details about Windows 8 and Windows RT have been known for months, dating as far back as the Microsoft //Build conference last year in September 2011.
However, the differences between Windows 8 and Windows RT are still creating confusion, both for consumers and developers. Some of the common questions asked include:
Is Windows 8 compatible with my current Windows app?
Can I build Windows 8 Metro apps in .NET?
Are Windows 8 games built in C++ or XNA?
Can I build apps for both Windows 8 and Windows Phone?
This post seeks to answer the most common questions and clarify things primarily for developers, with a few consumer tidbits thrown in for form. I’m also addressing Windows Phone development here since many questions arise about the compatibility between the new platform.
More on my blog at: http://community.infragistics.com/blogs/nick-landry/archive/2012/06/19/developing-apps-for-microsoft-surface-windows-8-windows-rt-and-windows-phone.aspx[^]
|
|
|
|
|
ActiveNick wrote: Is Windows 8 compatible with my current Windows app?
If W8 isn't compatible with existing Windows apps, Microsoft will have decapitated itself. Obviously, thousands of business aren't going to migrate to W8 if their existing apps don't run on it.
ActiveNick wrote: Can I build Windows 8 Metro apps in .NET?
At least in my business sector, Metro is an absurd front end. I'm not talking commercial apps, but rather in-house engineering apps, where engineers don't usually care too much about the UI, as long as it looks and feels like Excel. Seriously.
ActiveNick wrote: Are Windows 8 games built in C++ or XNA?
I totally do not care.
ActiveNick wrote: Can I build apps for both Windows 8 and Windows Phone?
If I were to build an app for a pad or phone, it would initially target Apple and/or Android devices. And again, building an app that can load a couple hundred thousand records in a few seconds and do some engineering computation on the dataset, now why would I do that on a freakin' phone???
Just saying. I know I work in a particular business sector, but pretty much, I don't care what Microsoft (or anybody else) does in the pad / phone market. I don't write games or cutesy apps - certainly I enjoy using them, but it's not my area of interest at the moment. Show me a customer willing to pay for some development, and I'll happily learn the ropes. Until then, I'm happy to ignore the whole mess.
Marc
|
|
|
|
|
ActiveNick wrote: Is Windows 8 compatible with my current Windows app?
Windows 8 yes, Windows RT(the ARM version) no.
ActiveNick wrote: Can I build Windows 8 Metro apps in .NET?
Sure. Even Windows RT. Further more, one can debug directly on the ARM machine with the latest release of VS wich is still beta.
ActiveNick wrote: Are Windows 8 games built in C++ or XNA?
Both. You can create in XNA or in C++ or the combination of the beasts
ActiveNick wrote: Can I build apps for both Windows 8 and Windows Phone?
Now that's tricky. Short answer yes. Longer answer some tweaks will be needed for the UI at least.
All the best,
Dan
|
|
|
|
|
As mobile devices and their app stores become more popular, there's a rising risk of more roadblocks for free software. [ITworld]
|
|
|
|
|
I don't see how he makes these connections, giving users access to a unified repository of apps (many of which are free!) will destroy free software? Every Linux distribution I've used has a model fairly close to Google's (there's a central repository for most software that is moderated to some extent to keep out dangerous and broken software, and you can take risks and download them from elsewhere as well).
If anything, this seems like a way to make the distribution of free software easier, because it puts the free and paid alternatives together in one place so even less technically inclined users will be able to download and install them.
|
|
|
|
|
Apparently Linus is not a fan of Nvidia... and he doesn't hold back how he really feels about them.
http://www.wired.com/wiredenterprise/2012/06/torvalds-nvidia-linux/[^]
Can't blame him, drivers have been a major cause of headaches in Linux for years.
Warning: The video in the story is long and it doesn't allow you to skip ahead... thanks Wired...
|
|
|
|
|
Only a little later he says "... because I'm a nice guy".
|
|
|
|
|
I'd hate to see someone he deems not nice
|
|
|
|
|
So let me get this straight...Nvidia is bad because they don't want to spend their money to have their employees develop graphics drivers for a system with only a small market share and almost no programs that even need a graphics card? Just because Linux is free and people donate their time to it, doesn't mean it's free for Nvidia to support it, and unless it's profitable for them they have no reason to support it. It's basic economics...
|
|
|
|
|
Nvidia also tries its best to keep the linux guys from developing their own driver.
|
|
|
|
|
I'm pretty sure the Linux community would be happy to write their own drivers. As I understand, they are pissed because nVidia is an undocumented* moving target of proprietary crapola.
So no, they don't expect Nvidia to spend money to insanely obvious ridiculism. They just want Nvidia to enable others to do so for free.
*) Lower that gun, JoSi, NOT in the sense of "illegal alien"
|
|
|
|
|
That makes sense, but it still takes them some time and money to create and distribute documentation (a lot less I would think, especially if they already have suitable documentation for public distribution being used internally).
As far as the moving target goes, graphics hardware has always been a rapidly changing segment of hardware, they have to keep changing to prevent AMD from getting ahead. I doubt they do it on purpose to prevent the Linux community from making drivers. And like I said, it's not like anything on Linux needs the advanced features of a graphics card, and I wouldn't think the basics change much.
|
|
|
|
|
lewax00 wrote: it still takes them some time and money to create and distribute documentation (a lot less I would think, especially if they already have suitable documentation for public distribution being used internally).
No doubt, it would cost them something. I'd almost expect a crockshit of brittle "only with the right incantation" API's - which is how I meant the moving target. Of course, graphics card drivers are always on the move, but if done right by the manufacturer, that makes them an interesting problem, too
|
|
|
|
|
lewax00 wrote: only a small market share
Only a small market share? ...Linux is probably the most prominent embedded system and server OS in the world... and now owns a huge market share of handheld devices with Android. I'd say that's a pretty big market share.
lewax00 wrote: and unless it's profitable for them they have no reason to support it
Do you think just because people are running Linux they don't buy their hardware?
|
|
|
|
|
Albert Holguin wrote: Linux is probably the most prominent embedded system and server OS in the world...
And generally those two applications do not need graphics cards. So it doesn't effect my point at all.
Albert Holguin wrote: Do you think just because people are running Linux they don't buy their hardware?
Profit is the amount of money gained after costs. Just because they buy the cards does not make them a profitable market if the sales of those cards do not exceed both the cost of manufacturing the card and the cost of developing, distributing, and maintaining a driver.
|
|
|
|
|
lewax00 wrote: if the sales of those cards do not exceed both the cost of manufacturing the card and the cost of developing, distributing, and maintaining a driver.
I don't think you understand the open source community... they want to develop their own drivers. The problem is that Nvidia isn't documenting it's hardware well or at all...
|
|
|
|
|
Even creating documentation takes time. And employee time costs money. Not to mention they may wish to protect trade secrets (which if no longer secret may cause them to lose their competitive edge, and then lose ground to competitors, and as a result, money).
The point is, they expect Nvidia to do what they want, but no one's considering the repercussions on Nvidia's end. And for any successful business, what it comes down to in the end is money. And businesses that do not make money do not last long.
|
|
|
|
|
lewax00 wrote: Even creating documentation takes time. And employee time costs money.
You don't think they have to write that documentation anyway? That has to be written regardless to build a product that is supportable within a large company... that's a fact.
|
|
|
|
|
Internal documentation is not always appropriate for public consumption. And even then, they have to distribute it, which means at the very least they would have to a) pay an employee to design a web page within their site to host it and b) pay for the additional bandwidth (though, with a document that probably won't be downloaded that often it's probably immaterial).
If it were profitable for them to do so, they probably would have done it.
|
|
|
|
|
|
So it looks like the drivers already exists, what's the issue then? It looks like Torvalds is whining for the sake of whining.
|
|
|
|
|
They provide drivers and documentation irregularly... that's the problem.
|
|
|
|
|
lewax00 wrote: And generally those two applications do not need graphics cards.
When did you use a terminal/command line ATM[^]?
|
|
|
|
|
When did you use a ATM with complex 3D graphics? Or maybe high definition video? A low power CPU is more than capable of handling the static 2D graphics used by an ATM...
|
|
|
|
|