News for hackers. Stuff that matters.
Re:Developer interest in Windows 8 is stagnant, new line of ... by jbk on Wednesday September 26, 2012 @08:47AM (#4575279)
Well, there are a few good reasons for that: coding for WinRT is harder than it should be, and the developers are not fans of the WinRT UI (so they don't use it).

I am in this very situation, with an app with has dozens of millions of users on Windows (and millions daily).

The first reason is the most important. WinRT requires a lot of rewrites of your code. (and the rationale behind some limitation are often political), and Microsoft is not helping or making it easy for you Notably for networking and multimedia.

Networking: everyone uses the BSD sockets, Win32, Linux, OSX, iOS, Android, Symbian, Bada, etc... And you cannot use them on WinRT. There is a very high chance that your code or one of your library uses it, of course. But the bad part is that Microsoft does not make easy with a wrapper exposing WinSock-like API based on their new API. Not even a wrapper than does 80% of the needs.

Multimedia and Games: your videogame that works with a C++ engine and OpenGL ES for casual games that works on iOS, Android, Bada,... does not work under WinRT, because OpenGL is not allowed... And I don't even speak about Video acceleration.

Yes, they need to do a massive change in their APIs, but helping the transition would have been a good idea...

So yes, writing yet another Twitter client is easy on WinRT, for more complex applications, well, it is way too hard and difficult to do it this fast.

Re:Developer interest in Windows 8 is stagnant, new line of ... by bunderbunder on Wednesday September 26, 2012 @09:21AM (#4575418)
Well, there are a few good reasons for that: coding for WinRT is harder than it should be

A lot of us haven't even gotten far enough to figure that out. Microsoft just switched us all over to a new UI toolkit (Windows Presentation Foundation) with the release of .NET 3 five or so years ago. We've invested a lot of time and money into getting up to speed with this new technology. And now we're already being asked to migrate away from it and onto yet another Next Big Thing.

Meanwhile, Microsoft zinged its mobile developers (the very ones they're so desperate to court) even harder by deciding that the new mobile platform they brought out only two years ago would not be compatible with the new mobile platform they're bringing out now.

It was twelve years ago this month that Steve Ballmer did his famous monkey dance while repeatedly shouting "Developers!" and apparently slipping into some sort of fugue state. Well, it turns out that all those developers he wanted to make such a big deal of saying are such a big deal? They're are all kind of pissed off and disgruntled right now.

Re:Developer interest in Windows 8 is stagnant, new line of ... by xradionut on Wednesday September 26, 2012 @09:48AM (#4575558)
"A lot of us haven't even gotten far enough to figure that out. Microsoft just switched us all over to a new UI toolkit (Windows Presentation Foundation) with the release of .NET 3 five or so years ago. We've invested a lot of time and money into getting up to speed with this new technology. And now we're already being asked to migrate away from it and onto yet another Next Big Thing."

Bingo! Talked about disrespecting your developers/users by changing the rules of the GUI every couple of years. Only the hardcore fans, pioneers and draftees are jumping into Windows 8. (The rest of us are keeping it locked up in virtual machines.) There's enough work in the Windows development universe, a developer can ignore Metro till it grows up or decent third party tools come out. For f--ks sake, Redmond, I've got real apps, (both web and desktop) to write.

Re:Developer interest in Windows 8 is stagnant, new line of ... by beagle3 on Wednesday September 26, 2012 @11:50AM (#4576246)
I guess a lot of the people here are too young to remember - but it's always been this way with Microsoft, and admittedly, with most other infrastructure companies out there (Sun had an era like that, NetScape did too). MFC, ATL, ADO, DAO, ...; Win8 might be breaking new ground in how "out of place" your app will be if you don't adopt the latest and greatest, but if you wanted nice modern menubars and toolbars ("Coolbar"), you had to switch from Win32 to MFC in the past. You had to go through hoops to get somethings done with COM without using ATL (with quite a few things working through ATL but not if you try to use COM directly; because no one in Microsoft ever tried to use them NOT through ATL).

And for a long time, it made everyone happy - because jumping on the new thing kept you employable, and actually shipping working products mattered less.

Microsoft did not change its ways. The world did.

Re:Developer interest in Windows 8 is stagnant, new line of ... by pjmlp on Wednesday September 26, 2012 @12:54PM (#4576607)
True most young lads, have this notion that only Microsoft keeps changing the thechnology stack, when actually all companies do the same.

As anyone noticed how many MacOS X APIs have been deprecated since the early days?

Or the API changes in Android?

Every corporation plays this game, as you point out.

I still remember the early COM days, where the only API was C based, and COM was called OLE.

Re:Developer interest in Windows 8 is stagnant, new line of ... by shimi on Wednesday September 26, 2012 @02:14PM (#4577092)
"Or the API changes in Android?" At least Google releases the support library to overcome that
Re:Developer interest in Windows 8 is stagnant, new line of ... by vetinari on Wednesday September 26, 2012 @03:19PM (#4577470)
The support library allows you to use features of newer system releases on older systems. See also GDI+ for Win98/NT4 or Windows feature packs for example.

The API changing game is another problem - it does not allow you to use existing application with newer system. As far as I know, this does not happen on Android (for now).

Re:Developer interest in Windows 8 is stagnant, new line of ... by pjmlp on Wednesday September 26, 2012 @04:00PM (#4577691)
There already a few deprecated API, which so far have not be removed, but until when?
Re:Developer interest in Windows 8 is stagnant, new line of ... by pjmlp on Wednesday September 26, 2012 @02:39PM (#4577243)
Really?!

That is why you have to import android.support.* versus android.app. Which forces you to have some form of preprocessing in the Java code.

Plus the API for the action bar is still missing from the support library.

Re:Developer interest in Windows 8 is stagnant, new line of ... by dredmorbius on Wednesday September 26, 2012 @03:21PM (#4577490)
Linux/Unix are just like this as well.

Except that the old widget sets never die. Xt, Athena, Motif, Lesstif, Tcl, gtk, Qt. Even swing and related tools if you include Java.

And so ... they're still in use. While significant new apps may not be getting developed with these tools, plenty of old ones are maintained, and the toolkits are largely serviceable -- they may be used if desired.

They actually provide a bit of useful visual feedback (if you're versed in Linux/Unix history), in that the style and design of an application gives you some idea of how it's going to work and what its quirks may be.

Consistency? We've heard of it.

Re:Developer interest in Windows 8 is stagnant, new line of ... by guilloche on Wednesday September 26, 2012 @12:09PM (#4576368)
After so much on MFC,OLE,COM/DCOM=>ATL, ADO, DAO, c#,.net,silverlight and now html5, I am not MS fan any more and has zero interest in any MS stuff.
Re:Developer interest in Windows 8 is stagnant, new line of ... by pjmlp on Wednesday September 26, 2012 @12:50PM (#4576583)
Name one single technology company that does not keep changing the developer tools all the time.

edit: typo

Re:Developer interest in Windows 8 is stagnant, new line of ... by bryanlarsen on Wednesday September 26, 2012 @02:04PM (#4577025)
The Linux Foundation, the Apache Project, et cetera.
Re:Developer interest in Windows 8 is stagnant, new line of ... by pjmlp on Wednesday September 26, 2012 @02:40PM (#4577245)
Those are not commercial vendors.

Still, if you want I can post all the Linux kernel ABI changes.

The changes done in Apache during the 1.x to 2.x transition.

Or many other examples, as they are quite easy to find.

Re:Developer interest in Windows 8 is stagnant, new line of ... by bryanlarsen on Wednesday September 26, 2012 @08:46PM (#4578782)
compared to the differences between win32 and WPF those are trivial. Also, the kernel ABI is considered an "internal" ABI, for better or for worse, the kind you wouldn't be able to access without an NDA and signed contract in the commercial world. The kernel's stable interface is its system call interface, which is remarkably stable.
Re:Developer interest in Windows 8 is stagnant, new line of ... by pjmlp on Thursday September 27, 2012 @01:42AM (#4579521)
Go tell that to the guys coding device drivers, so now device drivers API are private?!

Nice to bend the reality to fill into your argumentation.

Re:Developer interest in Windows 8 is stagnant, new line of ... by bryanlarsen on Thursday September 27, 2012 @12:52PM (#4581557)
Companies give out NDA's like candy, so that's hardly private.

I've written Linux device drivers. They're easy to write, and API changes are not a concern at all.

Re:Developer interest in Windows 8 is stagnant, new line of ... by pjmlp on Thursday September 27, 2012 @01:20PM (#4581708)
> Companies give out NDA's like candy, so that's hardly private.

private as "private/internal API" nothing to do with secret.

> I've written Linux device drivers. They're easy to write, and API changes are not a concern at all.

The whole point is that it changes! So it is ok for Linux to change the Kernel ABI, but for companies not?!

Re:Developer interest in Windows 8 is stagnant, new line of ... by WayneDB on Wednesday September 26, 2012 @02:18PM (#4577115)
And which one of those doesn't work anymore?
Re:Developer interest in Windows 8 is stagnant, new line of ... by jasomill on Wednesday September 26, 2012 @05:48PM (#4578232)
In Metro-style/Windows Store apps? MFC, ATL, ADO, DAO, and Silverlight, large parts of .NET, and COM components not written against the subset of Win32 supported by Metro.
Re:Developer interest in Windows 8 is stagnant, new line of ... by WayneDB on Thursday September 27, 2012 @10:55AM (#4580958)
Those kits still do work for the platform they were built for though.

New platform, new kits. Same as any other company.

Re:Developer interest in Windows 8 is stagnant, new line of ... by narrator on Wednesday September 26, 2012 @12:03PM (#4576329)
Way back in the day I used to be a Microsoft developer. I got tired of them changing the database API every other year. All the open sources platforms are much more stable. Knowledge in these other platforms doesn't decay as quickly or is at least somewhat useful even after 10 years.

In contrast, Microsoft will just go and kill whole platforms from time to time (e.g Visual Basic) rendering useless years of experience building deep understanding of a platform.

Re:Developer interest in Windows 8 is stagnant, new line of ... by elorant on Wednesday September 26, 2012 @01:33PM (#4576853)
I used to be a vb.net developer and I'm glad they killed the language. C# is far more elegant and sophisticated.
Re:Developer interest in Windows 8 is stagnant, new line of ... by bryanlarsen on Wednesday September 26, 2012 @02:05PM (#4577036)
Nobody mourns vb.net which is essentially a bastardized C#. Many mourn the original Visual Basic which was killed off by vb.net.
Re:Developer interest in Windows 8 is stagnant, new line of ... by EdiX on Wednesday September 26, 2012 @02:49PM (#4577296)
The original VB was a far worse language than VB.net ever was.
Re:Developer interest in Windows 8 is stagnant, new line of ... by smacktoward on Wednesday September 26, 2012 @03:25PM (#4577508)
A far worse language with enormous hordes of programmers who had bet their careers on it.

"Classic" VB was the PHP of the client/server era: ugly, reasonably capable, and everywhere.

Imagine the screams you would be hearing across the Internet if the PHP core devs all decided en masse to go work on something else, and PHP was under a closed, proprietary license so nobody could fork it, and you get a sense for what it was like when Microsoft killed VB.

Re:Developer interest in Windows 8 is stagnant, new line of ... by gaius on Wednesday September 26, 2012 @03:05PM (#4577399)
To be fair, ODBC is by far the most common DB API.
Re:Developer interest in Windows 8 is stagnant, new line of ... by jasomill on Wednesday September 26, 2012 @05:23PM (#4578140)
ODBC, which, along with every other database API released by Microsoft in the past decade, is not supported in Metro. Astonishingly, it currently appears to be easier to query a Microsoft SQL Server from an iOS app than from a Metro-style app. Presumably someone could port ODBC and a driver like FreeTDS to Metro, but it'd be made more difficult by the radically different networking APIs, and would still suffer from annoying limitations like the inability to connect to local database server instances (per Windows Store policy).
Re:Developer interest in Windows 8 is stagnant, new line of ... by pjmlp on Wednesday September 26, 2012 @12:55PM (#4576610)
Like any other commercial vendor.
Re:Developer interest in Windows 8 is stagnant, new line of ... by bunderbunder on Wednesday September 26, 2012 @01:20PM (#4576769)
I think Microsoft is worse about it that other commercial vendors. Perhaps due to a perception (not necessarily incorrect) on their part that their customers are locked in.

If a vendor who only supplies a single product decides to torpedo the APIs that you rely on, they create an easy opportunity for you to switch to another vendor entirely. Whereas historically Microsoft could wreak havoc upon an entire development platform (Visual Basic) knowing that probably all you'll be able to do about it is huff and puff around a bit on the Internet. After all you couldn't jump ship on Windows development - all your customers were Windows users, or your entire IT department was built around Windows, or your corporate intranet is all dependent on IE6, or whatever.

Re:Developer interest in Windows 8 is stagnant, new line of ... by cooldeal on Wednesday September 26, 2012 @01:41PM (#4576894)
Funny you say that, because Microsoft's software problems are often attributed to bending over backwards to be backward compatible while other vendors like Apple quickly kills compatibility with almost ever release, with even point releases.

Take this game bundled with Windows 95. ftp://ftp.microsoft.com/deskapps/games/public/AAS/Hover.exe

It runs even on Windows 8. Upgrading from Windows 1.0 to Windows 7.

http://www.youtube.com/watch?v=vPnehDhGa14

As I said in another comment, I still see some ASP and Visual Basic usage even after all these years, those applications are still supported in Windows 8 and Windows Server 2012. Microsoft stopped making new versions because it wanted to move on to better technology. Want to take a poll on HN about what developers think of Visual Basic and Classic ASP? A case of damned if they do, damned if they don't.

Re:Developer interest in Windows 8 is stagnant, new line of ... by jasomill on Wednesday September 26, 2012 @05:36PM (#4578186)
Right, but this is largely orthogonal to the problems with Metro on the desktop. Sandboxed Mac App Store apps are limited, but need not be written against an entirely new set of APIs that is not only unsupported by previous versions of the OS, but unsupported by non-App Store apps running on the current OS version. Say what you will about the Mac App Store, it at least doesn't suffer from all the problems inherent in the iOS App Store model. Metro does.
Re:Developer interest in Windows 8 is stagnant, new line of ... by cooldeal on Wednesday September 26, 2012 @01:18PM (#4576756)
I am sure there are a lot of people who rejoiced at Microsoft "killing" Visual Basic. And I say "killing" because I see a lot of it in use, they just stopped adding new features to it, the old applications written in the early 90s still work in Windows 8. Try that with other OSes or GUI toolkits.
Re:Developer interest in Windows 8 is stagnant, new line of ... by MattRogish on Wednesday September 26, 2012 @09:41AM (#4575526)
Fire and motion, my friend. Fire and motion: http://www.joelonsoftware.com/articles/fog0000000339.html
Re:Developer interest in Windows 8 is stagnant, new line of ... by beagle3 on Wednesday September 26, 2012 @12:28PM (#4576475)
Yep. And like in the battlefield, fire and motion works when you already have an advantage, but doesn't when you're in an inferior position (Which Microsoft is right now in the mobile market - and are not as dominant in the desktop[1] market)

[1] by which, I don't mean they are remotely in danger of being dethroned. Just that they can't dictate application standards anymore, because most activity happens on the web.

Re:Developer interest in Windows 8 is stagnant, new line of ... by z92 on Wednesday September 26, 2012 @11:45AM (#4576216)
That article was exactly what I was thinking of while reading this post. Thanks that you posted the link.
Re:Developer interest in Windows 8 is stagnant, new line of ... by dredmorbius on Wednesday September 26, 2012 @03:22PM (#4577495)
Fire and motion refers to your own forward momentum.

Using it to put developers within your own ecosystem off-balance is an antipattern.

Re:Developer interest in Windows 8 is stagnant, new line of ... by pjmlp on Wednesday September 26, 2012 @09:37AM (#4575504)
Metro is WPF based.
Re:Developer interest in Windows 8 is stagnant, new line of ... by mariusmg on Wednesday September 26, 2012 @09:45AM (#4575551)
Technically. In reality WinRT is missing A LOT of stuff from WPF (heck WinRT doesn't even reach parity with Silverlight). Simple stuff la x:Static, x:Array are not available.

WinRT 1.0 is basically a subset of Silverlight with a few specific controls thrown in.

Re:Developer interest in Windows 8 is stagnant, new line of ... by beagle3 on Wednesday September 26, 2012 @11:45AM (#4576212)
> heck WinRT doesn't even reach parity with Silverlight

That reminds me: WPF is not even a superset of Silverlight; There's functionality I need in Silverlight (regarding media codecs) which is not available in WPF, and my only way to get it is to instantiate a browser, run a silverlight app inside, and somehow bridge it all underneath in my app.

Pure madness.

Re:Developer interest in Windows 8 is stagnant, new line of ... by bunderbunder on Wednesday September 26, 2012 @10:11AM (#4575691)
You can use Xaml with WinRT. But beyond that cosmetic similarity, it gets pretty different. WPF is implemented in .NET, whereas WinRT is more of a replacement for Win32.

You can still write WPF apps for Windows 8, of course, but they won't be Metro apps, they won't run on ARM tablets and, significantly for the current conversation, they won't be allowed in the Windows app store.

Re:Developer interest in Windows 8 is stagnant, new line of ... by recoiledsnake on Wednesday September 26, 2012 @11:35AM (#4576152)
>Meanwhile, Microsoft zinged its mobile developers (the very ones they're so desperate to court) even harder by deciding that the new mobile platform they brought out only two years ago would not be compatible with the new mobile platform they're bringing out now.

WP7 apps will run on WP8 without any modifications or even without anything needing to be done by the developers.

>Well, it turns out that all those developers he wanted to make such a big deal of saying are such a big deal? They're are all kind of pissed off and disgruntled right now.

Citation needed and content farms like TNW who will "print" anything to drive clicks don't count.

I know it's hip on HN to rag on Microsoft, but cmon, two thousand apps for a platform that is a month away from release(only available to MSDN users right now) and everyone is predicting doomsday? Perhaps developers are making use of the last month to further enhance apps before submitting them?

Re:Developer interest in Windows 8 is stagnant, new line of ... by partisan on Wednesday September 26, 2012 @10:33AM (#4575827)
"So yes, writing yet another Twitter client is easy on WinRT, for more complex applications, well, it is way too hard and difficult to do it this fast."

Almost every Metro style application demo I've seen is some variant of a "social" app. Do they really think that the millions of windows developers all suddenly started working on social apps?

Every one of the pivots that they have made in the past few years has been in reaction to some external threat and the developers are in the crossfire. Windows developers are too weary to be excited about yet another wide ranging change.

Re:Developer interest in Windows 8 is stagnant, new line of ... by sageikosa on Wednesday September 26, 2012 @09:02AM (#4575342)
Visual Studio 2008 to Visual Studio 2010 Professional upgrade price: $249. Visual Studio 2010 Professional to Visual Studio 2012 Professional upgrade price: $499.
Re:Developer interest in Windows 8 is stagnant, new line of ... by Ntrails on Wednesday September 26, 2012 @09:23AM (#4575428)
Eyestrain within 8 minutes of looking at VS2012: Priceless
Re:Developer interest in Windows 8 is stagnant, new line of ... by mtgx on Wednesday September 26, 2012 @08:55AM (#4575308)
I didn't even think of that, but all mobile games on iOS and Android are done with OpenGL ES, and Microsoft doesn't even support it. That could be a major problem for Microsoft.
Re:Developer interest in Windows 8 is stagnant, new line of ... by pjmlp on Wednesday September 26, 2012 @09:40AM (#4575521)
Most game engines support multiple graphics APIs.

Contrary to popular belief by many geeks, game consoles do not support OpenGL as well. When they do, like the PS3, is a kind of subset that most studios avoid using anyway, and prefer to make use of the lower level APIs.

Re:Developer interest in Windows 8 is stagnant, new line of ... by trotsky on Wednesday September 26, 2012 @10:40AM (#4575865)
maybe someday microsoft will be able to build its own stable of titles if these xbox and direct x projects ever take off
Re:Developer interest in Windows 8 is stagnant, new line of ... by pavlov on Wednesday September 26, 2012 @09:01AM (#4575341)
You can use the ANGLE library [1] to translate OpenGL ES to DirectX. It's used by both Chrome and Firefox, so it's widely deployed and also tested for OpenGL ES conformance.

Re: networking, you are of course right. At the same time, I can sympathize with Microsoft's decision to abandon Winsock. Cross-platform use of BSD sockets is mired in a deplorable mess of #defines and '90s incompatibilities. For new code, the non-blocking WinRT API is a million times better -- the question is, what can Microsoft do to make porting easier?

[1] http://code.google.com/p/angleproject/

Re:Developer interest in Windows 8 is stagnant, new line of ... by melling on Wednesday September 26, 2012 @09:12AM (#4575373)
Isn't DirectX part of a walled garden? If more games are written in OpenGL, for example, they will be easier to port to Android, Linux, Mac OS, and even the iPhone. A decade ago, it looked like OpenGL was dead. I, for one, am glad to see its resurgence.
Re:Developer interest in Windows 8 is stagnant, new line of ... by mtgx on Wednesday September 26, 2012 @09:28AM (#4575455)
OpenGL ES 3.0 and OpenGL 4.3 are going to be even more interesting in regards to that, as developers can write OpenGL ES 3.0 games for iOS and Android devices, and then do a 1:1 port to OpenGL 4.3 PC's, without further modifications, because OpenGL 4.3 fully incorporates OpenGL ES 3.0.

What I find mind-blowing, though, is that Intel's new architecture Haswell which will come out mid 2013, and is supposed to be even more GPU-oriented than previous chips, will only support OpenGL 3.2, which will be 4 years old by the time the chip launches (some sources say OpenGL 4.0 - still 3 years old though)...and yet it will support DirectX 11.1. I find that incredibly disappointing.

I guess Intel just doesn't care about OpenGL. I'm not sure how they are supposed to make us believe that they are serious about entering the mobile market with that kind of attitude towards OpenGL.

Re:Developer interest in Windows 8 is stagnant, new line of ... by binarycrusader on Wednesday September 26, 2012 @01:33PM (#4576855)
Intel's OpenGL support is a software, not hardware issue. The hardware is capable, but their OpenGL stack is pretty limited right now.

They've publicly stated that the hardware is OpenGL 4 capable. (Google it.)

Re:Developer interest in Windows 8 is stagnant, new line of ... by stephengillie on Wednesday September 26, 2012 @01:35PM (#4576864)
Won't it be possible for newer versions of OGL to be implemented in drivers? Or is there a hardware piece required for newer OGL which that chip lacks?
Re:Developer interest in Windows 8 is stagnant, new line of ... by rbanffy on Wednesday September 26, 2012 @10:19AM (#4575741)
> they will be easier to port to Android, Linux, Mac OS, and even the iPhone.

Bingo. Microsoft was never very fond of the idea of people porting Windows apps to other platforms. If people develop portable apps that run everywhere, the network effects achieved by having OEMs bundling Windows on every PC are neutralized.

Re:Developer interest in Windows 8 is stagnant, new line of ... by taude on Wednesday September 26, 2012 @10:32AM (#4575825)
The irony is now MSFT needs these other developers to port their successful iOS/Android games to their platform. MSFT shouldn't be making this a difficult choice for devs. The few people who do end up with Win RT tablets and such will likely hear about games/apps working on other platforms and then look to see if they are available on the Win device...and since MSFT put up this wall....well....users will think should've bought an iPad.

(Note, i'm actually a little excited about the Surface tablet as a potential device that crosses the chasm between full tablet and laptop. But I don't have very many apps that I use now on my iPad.)

EDIT: Also, I don't know much about any game development SDK engines that abstract devs from these proprietary libraries and runtimes...however I think they must exist?

Re:Developer interest in Windows 8 is stagnant, new line of ... by ISV_Damocles on Wednesday September 26, 2012 @11:01AM (#4575970)
You can already get something like the surface: Asus' Transformer series.

I have a Transformer Prime (#2, Transformer Infinity is the newest one) and the keyboard dock. Android apps/games, plus terminal, VNC, etc for doing real work.

And Android 4.0 looks more like Windows 7 than Windows 8 does (black "taskbar" on the bottom with clock and notifications on the right, home button, back button, and app switcher button on the left, and the 'desktop' can have icons and widgets).

Re:Developer interest in Windows 8 is stagnant, new line of ... by prodigal_erik on Wednesday September 26, 2012 @09:33AM (#4575481)
It's incompatible (for reasons that didn't used to be gratuitous) but you don't need Microsoft's permission to do anything with it.
Re:Developer interest in Windows 8 is stagnant, new line of ... by 0x0 on Wednesday September 26, 2012 @09:35AM (#4575492)
Not to mention WebGL! :)
Re:Developer interest in Windows 8 is stagnant, new line of ... by jbk on Wednesday September 26, 2012 @09:07AM (#4575358)
> Re: networking, you are of course right. At the same time, I can sympathize with Microsoft's decision to abandon Winsock. Cross-platform use of BSD sockets is mired in a deplorable mess of #defines and '90s incompatibilities. For new code, the non-blocking WinRT API is a million times better -- the question is, what can Microsoft do to make porting easier?

That is not a reason to not code and offer a code wrapper for BSD-sockets-like API based on WinRT sockets.

Of course, no need to cover 100% of the API and they could use lots of warnings to force developers to slow transition.

Re:Developer interest in Windows 8 is stagnant, new line of ... by beagle3 on Wednesday September 26, 2012 @12:24PM (#4576453)
> Re: networking, you are of course right. At the same time, I can sympathize with Microsoft's decision to abandon Winsock. Cross-platform use of BSD sockets is mired in a deplorable mess of #defines and '90s incompatibilities.

Oh, the irony. If you actually look at those #ifdefs, the vast majority of them are #ifdef __WIN32__ - because Microsoft didn't really care about compatibility when they first adopted BSD code. Compared to Unix/Windows, the differences between BSD and Linux are almost nonexistent.

Re:Developer interest in Windows 8 is stagnant, new line of ... by davedx on Wednesday September 26, 2012 @08:55AM (#4575306)
> because OpenGL is not allowed

Wow. That's pretty ridiculous. So DirectX is allowed?

OK if you're a triple A studio with a cross-platform engine. Show stopper for most other devs.

Re:Developer interest in Windows 8 is stagnant, new line of ... by jbk on Wednesday September 26, 2012 @09:00AM (#4575332)
> Wow. That's pretty ridiculous. So DirectX is allowed?

DirectX11 with 2 compatible modes (D3D9 and D3D10)

Re:Developer interest in Windows 8 is stagnant, new line of ... by radicalbyte on Wednesday September 26, 2012 @09:41AM (#4575524)
Funny, I have exactly the opposite opinion: because Metro supports html + javascript it's very easy to get data-driven apps out with very little effort.

Of course if you're doing anything interesting then it's probably a nightmare.. but the vast majority of applications aren't doing anything interesting, so Win RT is great for them.

Re:Developer interest in Windows 8 is stagnant, new line of ... by andywhite37 on Wednesday September 26, 2012 @11:01AM (#4575973)
From what I understand, the HTML+Javascript WinRT APIs are really only supported on the "full" Windows RT/Metro environment, not Windows Phone 8. Windows Phone 8 supports C#/VB+XAML, C/C++, and you can use HTML and Javascript, but only in a web browser control, which is not the same as a true Javascript API with hooks into lower-level constructs. Apparently, you can also run legacy Windows Phone 7 Silverlight apps on Windows Phone 8 as well, but that is just a stopgap to not completely cut ties with the legacy apps.
Re:Developer interest in Windows 8 is stagnant, new line of ... by riviera on Wednesday September 26, 2012 @01:54PM (#4576969)
My guess is that PhoneGap is going to be massively successful with WP8 apps, if the platform is ever to take off.
Re:Developer interest in Windows 8 is stagnant, new line of ... by bornhuetter on Wednesday September 26, 2012 @08:51AM (#4575290)
Do you think that WinRT will cause anything important to be broken in VLC, or is it just making your life harder to get it working?
Re:Developer interest in Windows 8 is stagnant, new line of ... by jbk on Wednesday September 26, 2012 @08:59AM (#4575329)
Well, outputting video and audio should not be too hard to adapt (almost work out of the box).

Decoding does not do system calls, except for hardware decoding, so no worry.

File input is worrying because of the sandbox, but should be doable with some work.

But networking is a nightmare. 20 libraries are using WinSock2 (including some codecs like FLAC), plus libVLC's core. Sure HTTP access is fine, but RTP, RTSP, FTP, HTTPS, multicast UDP are weirder beasts...

To add it to the pain, VLC is a mostly C99 project, but C99 is too new a standard for Microsoft to implement it :)

Re:Developer interest in Windows 8 is stagnant, new line of ... by bornhuetter on Wednesday September 26, 2012 @09:09AM (#4575363)
Microsoft seems to have borderline personality disorder when it comes to supporting developers and standards.

Good luck with it – I’m sure you know it’s one of the Killer Apps on any platform.

Re:Developer interest in Windows 8 is stagnant, new line of ... by jbk on Wednesday September 26, 2012 @10:25AM (#4575787)
Thanks.
Re:Developer interest in Windows 8 is stagnant, new line of ... by chj on Wednesday September 26, 2012 @09:08AM (#4575360)
Missing c99 support is really a pain in the ass. I can't believe they don't care about it.
Re:Developer interest in Windows 8 is stagnant, new line of ... by stonemetal on Wednesday September 26, 2012 @10:12AM (#4575696)
I can't believe they don't care about it.

Considering the last time MS released a C compiler I can fully believe it.

Re:Developer interest in Windows 8 is stagnant, new line of ... by pjmlp on Wednesday September 26, 2012 @01:12PM (#4576719)
Microsoft cares about C++, which already includes most of the C99 changes.

GCC has recently migrated to C++ and CLang is developed in C++.

So Microsoft reasoning is that C89 is good enough for them, and you are free to buy a compiler from another vendor if you really want to use C99.

Re:Developer interest in Windows 8 is stagnant, new line of ... by pjmlp on Wednesday September 26, 2012 @04:01PM (#4577703)
Ooops, I pissed off the C fanboys!
Re:Developer interest in Windows 8 is stagnant, new line of ... by masklinn on Wednesday September 26, 2012 @01:53PM (#4576960)
> To add it to the pain, VLC is a mostly C99 project, but C99 is too new a standard for Microsoft to implement it :)

Hah, better than that, Herb Stutter explicitly stated they don't give a flying fuck about C99: http://herbsutter.com/2012/05/03/reader-qa-what-about-vc-and...

> If you really need [...] features in C95/C99/C11 that are not part of ISO C++[, use] a different compiler

Re:Developer interest in Windows 8 is stagnant, new line of ... by supersaiyan on Wednesday September 26, 2012 @08:58AM (#4575326)
I'm surprised they didn't release an updated version of XNA for windows 8, that's by far one of the best game dev tools out there.
Re:Developer interest in Windows 8 is stagnant, new line of ... by tluyben2 on Wednesday September 26, 2012 @09:41AM (#4575531)
Disclaimer: I have no clue about Win specific game development, but I thought this would be interesting for others.

I read in a lot of places recently (this year) that XNA is 'dead' (search Google for instance). Is this true? What replaces it?

Re:Developer interest in Windows 8 is stagnant, new line of ... by aschearer on Wednesday September 26, 2012 @10:15AM (#4575722)
MonoGame replaces it and is available now for Windows 8. In fact I've completed two games using MonoGame which run using 95% the same code on Windows XP, Vista, 7, and 8. Pretty soon there will be a Linux and Android version as well.

If you want to see what's possible you can check them out:

1) Adlib: http://apps.microsoft.com/webpdp/en-US/app/adlib/9cc0809e-b0...

2) Petunk http://apps.microsoft.com/webpdp/en-US/app/petunk/c03ecbca-4...

You can also read a great deal more about the process as well as watch me convert a game live here: http://www.reddit.com/r/windows8/comments/10g4r2/check_out_m...

Re:Developer interest in Windows 8 is stagnant, new line of ... by tluyben2 on Thursday September 27, 2012 @05:10AM (#4579948)
I was looking for an 'official MS technology' replacing it. I know monogame. I wouldn't think anyone NEW to game dev would start with it; it's for XNA devs wanting a life after, right?