4 ms·

Microsoft didn't ditch "metro".. its just UWP.. they were sued because metro was apparently copyrighted. UWP is good.. wish devs would embrace it but to be hone

Microsoft didn't ditch "metro".. its just UWP.. they were sued because metro was apparently copyrighted. UWP is good.. wish devs would embrace it but to be honest, the dev community is up the asses of iOS so deep they can't see the forrest form the trees.. Windows 10 has 400million + users and growing and Xbox One has 25 million devices... come on devs.. write some (good) apps please! C# is actually kind of fun too

seanmcdirmid 10y ago
UWP takes away a lot from the platform though, like compilation via the DLR, and deploying can take an hour or so of building (I went through a nightmare experience trying to demo on a surfacehub, worked in the end, but damn). I want to like it (Win2D in particular is nice for my needs), but the execution has been lacking.
- supernovae 10y ago
  the "iron" languages never got much adoption though.. perhaps if .net had gone open source before ironpython, ironruby and iron. this would have been more important. With that being said, I believe its only a matter of time before Microsoft brings this to UWP as all the insider and developer surveys have been focusing on asking what other languages people use and want to be able to write in within the context of UWP (Xbox/Surface/Win10)
  - seanmcdirmid 10y ago
    I was using the DLR for my live programming research and was kind of bummed when it was effectively deprecated via nerfing; I never used the iron languages, just the infrastructure used to build them. In fact, this was one thing that Microsoft had that everyone else was lacking, a real unique advantage, dynamic compilation with statically types performance via a tree API and JIT. My use case was really niche, however.
ComputerGuru 10y ago
I think we are talking past one another here. I've been a Windows developer longer than I've been a Mac developer, and write C# on a daily basis. Microsoft _did_ ditch the all-metro approach they took with Windows 8. You start up your PC and you see the familiar desktop. There's a start menu, even if it's different, with live tiles and all. It feels like an improvement, not like an alien intrusion. But the biggest difference is that metro apps and native Win32 apps can and do co-exist side-by-side on the same desktop. Metro/UWP apps are no longer full screen on a 30" desktop, they just have a different "feel" but they're otherwise treated the same way as any other app you use. A dashboard with "tiles" to access your apps Xbox-style was never the right interface for PCs (touch screen is such a fad and even if it's not, it's not for everyone, everywhere and it isn't productive) and MS finally realized and embraced that with Windows 10.
- supernovae 10y ago
  The start bar is a simplification of the start page. Its one single option to turn it back into a start page. As for the full screen stuff, that was fixed in 8.1.. I'm not even sure what we're debating anymore. You're just obfuscating the truth that the reality is Windows 10 is ALL about 'metro' just under the premise of UWP.

seanmcdirmid 10y ago

UWP takes away a lot from the platform though, like compilation via the DLR, and deploying can take an hour or so of building (I went through a nightmare experience trying to demo on a surfacehub, worked in the end, but damn). I want to like it (Win2D in particular is nice for my needs), but the execution has been lacking.

supernovae 10y ago
the "iron" languages never got much adoption though.. perhaps if .net had gone open source before ironpython, ironruby and iron. this would have been more important. With that being said, I believe its only a matter of time before Microsoft brings this to UWP as all the insider and developer surveys have been focusing on asking what other languages people use and want to be able to write in within the context of UWP (Xbox/Surface/Win10)
- seanmcdirmid 10y ago
  I was using the DLR for my live programming research and was kind of bummed when it was effectively deprecated via nerfing; I never used the iron languages, just the infrastructure used to build them. In fact, this was one thing that Microsoft had that everyone else was lacking, a real unique advantage, dynamic compilation with statically types performance via a tree API and JIT. My use case was really niche, however.

ComputerGuru 10y ago

I think we are talking past one another here. I've been a Windows developer longer than I've been a Mac developer, and write C# on a daily basis. Microsoft _did_ ditch the all-metro approach they took with Windows 8. You start up your PC and you see the familiar desktop. There's a start menu, even if it's different, with live tiles and all. It feels like an improvement, not like an alien intrusion. But the biggest difference is that metro apps and native Win32 apps can and do co-exist side-by-side on the same desktop. Metro/UWP apps are no longer full screen on a 30" desktop, they just have a different "feel" but they're otherwise treated the same way as any other app you use. A dashboard with "tiles" to access your apps Xbox-style was never the right interface for PCs (touch screen is such a fad and even if it's not, it's not for everyone, everywhere and it isn't productive) and MS finally realized and embraced that with Windows 10.

supernovae 10y ago
The start bar is a simplification of the start page. Its one single option to turn it back into a start page. As for the full screen stuff, that was fixed in 8.1.. I'm not even sure what we're debating anymore. You're just obfuscating the truth that the reality is Windows 10 is ALL about 'metro' just under the premise of UWP.