Earlier quoted context omitted.
"mythz", Merto style apps can always be done in HTML5, CSS, http://msdn.microsoft.com/en-us/library/windows/apps/br21138... so I am not sure why you say that the cross platform rich initiatives have been killed. More details: http://www.winsupersite.com/blog/supersite-blog-39/windows8/...
"This couldn’t be further from the truth. The use of HTML5 + JavaScript in Windows 8 is about as proprietary as using XAML + .NET." http://dougseven.com/2011/10/24/language-choice-in-windows-8... Just because it uses JS doesn't mean its portable! It has proprietary APIS + hooks making it non portable.
Microsoft Open Sources their Entity Framework ORM
51–60 of 83 posts
Re: Microsoft Open Sources their Entity Framework ORM
#52Is Entity used a lot? We looked at using it but it seemed to be inferior to NHibernate (don't remember details, think there was a problem with type error detection and other stuff).
The company I work for uses it, I'm not thrilled - it's still rough around the edges and I'm used to writing my own SQL, but it gets the job done on the few projects I've used it (I only used V1 which was very bad).
Re: Microsoft Open Sources their Entity Framework ORM
#53Re: Microsoft Open Sources their Entity Framework ORM
#54Earlier quoted context omitted.
"This couldn’t be further from the truth. The use of HTML5 + JavaScript in Windows 8 is about as proprietary as using XAML + .NET." http://dougseven.com/2011/10/24/language-choice-in-windows-8... Just because it uses JS doesn't mean its portable! It has proprietary APIS + hooks making it non portable.
That's no different from using HTML5+JavaScript against browser specific APIs or using CSS3 vendor prefixes. Calling external stuff from JavaScript (even if that external thing is Windows itself) is not new and it's not bad that it's not portable any more than writing XUL wasn't portable.
Sure it is if those browsers are cross-platform. I doubt the Windows 8 APIs are cross platform.
Re: Microsoft Open Sources their Entity Framework ORM
#55Earlier quoted context omitted.
"This couldn’t be further from the truth. The use of HTML5 + JavaScript in Windows 8 is about as proprietary as using XAML + .NET." http://dougseven.com/2011/10/24/language-choice-in-windows-8... Just because it uses JS doesn't mean its portable! It has proprietary APIS + hooks making it non portable.
That's no different from using HTML5+JavaScript against browser specific APIs or using CSS3 vendor prefixes. Calling external stuff from JavaScript (even if that external thing is Windows itself) is not new and it's not bad that it's not portable any more than writing XUL wasn't portable.
Since you've mentioned it, Mozilla isn't touting to use XUL for "open" cross-browser apps - although XUL itself, unlike anything Metro, is open source and does run cross-platform. Mozilla is even deprecating the use of XUL for its new Firefox OS (Boot to Gecko) in favor of using pure HTML5 instead. Maybe MS can work together with Mozilla and come up with a common API?
Re: Microsoft Open Sources their Entity Framework ORM
#56Earlier quoted context omitted.
That's no different from using HTML5+JavaScript against browser specific APIs or using CSS3 vendor prefixes. Calling external stuff from JavaScript (even if that external thing is Windows itself) is not new and it's not bad that it's not portable any more than writing XUL wasn't portable.
"That's no different from using HTML5+JavaScript against browser specific APIs" Sure it is if those browsers are cross-platform. I doubt the Windows 8 APIs are cross platform.
Re: Microsoft Open Sources their Entity Framework ORM
#57Earlier quoted context omitted.
That's no different from using HTML5+JavaScript against browser specific APIs or using CSS3 vendor prefixes. Calling external stuff from JavaScript (even if that external thing is Windows itself) is not new and it's not bad that it's not portable any more than writing XUL wasn't portable.
If there's no equivalent work around it's not portable - simple as that. Proprietary hooks and APIs aren't evil, but suggesting developing for Metro is "open" and portable is wrong. Since you've mentioned it, Mozilla isn't touting to use XUL for "open" cross-browser apps - although XUL itself, unlike anything Metro, is open source and does run cross-platform. Mozilla is even deprecating the use of XUL for its new Fir…
Re: Microsoft Open Sources their Entity Framework ORM
#58Earlier quoted context omitted.
"This couldn’t be further from the truth. The use of HTML5 + JavaScript in Windows 8 is about as proprietary as using XAML + .NET." http://dougseven.com/2011/10/24/language-choice-in-windows-8... Just because it uses JS doesn't mean its portable! It has proprietary APIS + hooks making it non portable.
That's no different from using HTML5+JavaScript against browser specific APIs or using CSS3 vendor prefixes. Calling external stuff from JavaScript (even if that external thing is Windows itself) is not new and it's not bad that it's not portable any more than writing XUL wasn't portable.
The only one talking about 'bad' is you saying it's 'not bad'.
Re: Microsoft Open Sources their Entity Framework ORM
#59Earlier quoted context omitted.
Seems more like a desperation move to me. Microsoft have almost no presence in popular web apps or mobile. Almost no startups or established services use the Microsoft stack. Maybe they think that by open sourcing they will get a look by devs/shops that would never have considered them before. I still think it's a long shot. The best development platform for .NET is Visual Studio and Windows. And the "cool startups"…
There are plenty of startups that have been successful on the .NET stack. The one that pops to mind first is Stack Overflow. .NET & XNA are pretty popular in indie games due to exposure to the xbox. There are many examples, but they don't tend to over lap much with the crowd here at HN.
Re: Microsoft Open Sources their Entity Framework ORM
#60Earlier quoted context omitted.
That's no different from using HTML5+JavaScript against browser specific APIs or using CSS3 vendor prefixes. Calling external stuff from JavaScript (even if that external thing is Windows itself) is not new and it's not bad that it's not portable any more than writing XUL wasn't portable.
The point being made by mythz to barista was that Metro's HTML5 + JavaScript was not portable (cross-platform), and you clearly agree. The only one talking about 'bad' is you saying it's 'not bad'.