由买买提看人间百态

topics

全部话题 - 话题: winrt
1 2 3 4 5 6 下页 末页 (共6页)
Y*********i
发帖数: 215
1
来自主题: Seattle版 - 关于微软的winrt
要明白这个必须有几点要搞清楚。
1、一般大家都认为COM已经没人用了,但事实上有一点不人所注意的事实就是,在
Windows user mode这一层COM无所不在,很多Windows API下面是COM调用。
2、.Net runtime 本身就是一个COM Server。也就是说C#所有涉及到系统API调用的工
作全部是通过这个COM Server来完成的。这样的缺点显而易见就是API调用效率比较低。
3、WinRT和传统API最大的不同就是增加了Namespace的支持比如:Windows::
Foundation::Initialize。其下面虽然仍然是COM但Overhead非常的小,几乎可以忽略。
4、有了WinRT,加上Compiler的支持,C#、Javascript和C++都可以对Windows API进行
直接调用。当然这里面由于Compiler所产生的Overhead在这几种语言中是不同的,具体
来讲仍然是C++最好。但是他们都在同一个数量级上,不再象以前没有可比性。
这样应该明白为什么C#-〉.Net -〉WinRT是没有意义的。同时C#-〉another ma... 阅读全帖
n*w
发帖数: 3393
2
来自主题: Seattle版 - 关于微软的winrt
我的意思是,c++ -> winrt 没问题。
但为什么不是 c# -> .Net -> winrt, 而是 c# -> another managed layer -> winrt.
G*****h
发帖数: 33134
3
来自主题: Seattle版 - 关于微软的winrt
.net 里爱加不加都行吧,加了也没啥大好处,
就算要加,windows team 也没人手,还得 .net team 来做
肯定不会把 winrt 搞成 .net 专用,那可就真脑残了
看这个sample C# 用 winrt 跟用 .net 的语法差不多
加个 .net wrapper 也没啥意思
http://devhawk.net/2011/09/15/using-winrt-from-csharp-build-dem
G*****h
发帖数: 33134
4
来自主题: Seattle版 - 关于微软的winrt
.net 扩大点,包含这个 another managed layer
就是你想要的了吧
这是 .net 里加东西的问题,不是 winrt 的问题

winrt.
s***o
发帖数: 2191
5
来自主题: Seattle版 - 关于微软的winrt
What I mean is that even with WinRT, JS can only be hooked up with HTML,
while C++ and C# use XAML. Of course this is just some implementation
details so what you said about WinRT is still solid.
Many Web developers outside M$ shop are die-hard M$ haters. It is
interesting to see how attractive the Windows Store will be to these people.
I also hope people don't have to pay $100/year or even more membership fee
before they can do anything, as M$ does with Windows Phone, which irritates
many.

cre... 阅读全帖
n*w
发帖数: 3393
G*****h
发帖数: 33134
7
来自主题: Seattle版 - 关于微软的winrt
要下面是 .net 你让人家那么多不肯用 GC 的 C++ 程序猿怎么办
再说做一套 .net 的 winrt wrapper 又不难
w*i
发帖数: 970
8
来自主题: Seattle版 - 关于微软的winrt
Winrt实际上是com啊,com是不是有.net wrapper ?

★ 发自iPhone App: ChineseWeb - 中文网站浏览器
Y*********i
发帖数: 215
9
来自主题: Seattle版 - 关于微软的winrt
What you said is true before Win8. After Win8, with WinRT, JavaScript
language projection and the new JavaScript UI framework in place, you can create a
Metro application which lives out of Browser and, in this case, the
JavaScript Metro application is running inside a process named WWAHost. This
means all of the current JavaScript programmer can easily create the same
kind of application that could only be done with C++ or C# before Win8.
This is very attractive to current web developers becaus... 阅读全帖
Y*********i
发帖数: 215
10
来自主题: Seattle版 - 关于微软的winrt
Sorry, I don't know. Never programed on it.But assuming it is true on WebOS, the application created for WebOS probably would not be able to run on PC or phone. It should be easy to create an application which can be run on PC, phone and tablet with Javascript+XAML+WinRT after Win8.
N********n
发帖数: 8363
11
来自主题: Seattle版 - 关于微软的winrt
Btw what about the native desktop apps running outside of WinRT? What's
the improvement in Win8 over there?
n*w
发帖数: 3393
12
来自主题: Programming版 - 关于微软的winrt (转载)
【 以下文字转载自 Seattle 讨论区 】
发信人: nkw (非死非活), 信区: Seattle
标 题: 关于微软的winrt
发信站: BBS 未名空间站 (Sat Jan 21 17:51:40 2012, 美东)
下面这段话是真的吗?
The new Windows API is unmanaged because the leaders in the Windows teams (
and Office team, whose former leader –Sinofsky- is now the president of the
Windows and Windows Live Division) had no part in the design and
distribution of .NET, never promoted it in any way, and its popularity is
actually a threat to their personal careers (imagine: if .NET became an even
bigge... 阅读全帖
l*s
发帖数: 783
13
来自主题: DotNet版 - [合集] .NET 何去何从
☆─────────────────────────────────────☆
BubbleSort (亚特兰蒂斯) 于 h 提到:
我们组的Silverlight网站,头决定用Java Spring MVC完全重做,因为
微软今后不会对Silverliht继续升级了。
这一两年,微软的脑残决定可不少啊。看看这篇评论:
http://www.i-programmer.info/professional-programmer/i-programm
网友的杰作:
http://www.youtube.com/watch?v=RRFiu0xfQzw&autoplay=1
☆─────────────────────────────────────☆
rodney (√) 于 (Sat Jan 12 13:46:05 2013, 美东) 提到:
NeverLearn会给你定心的。

☆─────────────────────────────────────☆
goodbug (好虫) 于 (Sat Jan 12 23:00:26 2013, 美东) 提到:
Hi... 阅读全帖
B********t
发帖数: 1321
14
来自主题: DotNet版 - .NET 何去何从
呵呵。你很乐观,可惜WinRT不是.NET,当然,没人否认.NET在win8的地位,.NET只是
众多可用技术之一而已:
http://community.devexpress.com/blogs/seth/archive/2011/09/23/w
看这一段:
http://www.zdnet.com/for-windows-developers-sinofskys-legacy-is
When designing the new APIs for the new platform, Microsoft -- well,
Sinofsky -- had two options. Base it on .NET or do something different. He
should have based the new platform on .NET -- but for various reasons he
chose to reboot the entire developer story on WinRT. The most likely reason
is that .NET... 阅读全帖
r****y
发帖数: 26819
15
感觉XAML是用来取代WPF和SL的,换句话说,SL和WPF是基于CLR的,配合的语言是c#或
VB,而XAML framework是WinRT的一部分,底层实现的语言是native code和c/c++。
也就是说,SL的run-time environment不在winRT里,还是只会在desktop 浏览器的插
件里。而XAML会成为WinRT的一部分,替代SL和WPF。
SilverLight不在winRT里,SL还是插件,可以参看这张图:
B********t
发帖数: 1321
16
来自主题: DotNet版 - .NET 何去何从
从你这段评论可以看出,你对WinRT的认识相当的肤浅和错误。作为Windows Developer
,你不会没开发过Win32 COM程序吧?看看WinRT的定义吧:
WinRT is essentially a COM-based API, although relying on an enhanced COM.
Due to its COM-like basis, WinRT allows interfacing from multiple languages,
just as COM does, but it's essentially an unmanaged, native API.
r****y
发帖数: 26819
17
来自主题: DotNet版 - .NET 何去何从
“used SL/XAML model to build a different runtime”是什么意思?runtime只有一
个WinRT,不是用SL/XAML做出来的。
WinRT有三个编程方式,一等首选是Native c++,其次是.NET语言和WinRT的XAML frame
work,其次是JS。
N********n
发帖数: 8363
18
来自主题: DotNet版 - .NET 何去何从

Have no idea what you are talking about. 桌面开发 can ALWAYS be
done in pure C++/Win32. That option is always there especially
for multimedia apps. .Net never has a monopoly on 桌面开发.
The situation remains the SAME in WinRT. You can code METRO apps
in either .Net or VC++. There's no such thing as '比以前弱了'.
And Win32 is not a "WinRT里的小子集". It's the other way around.
WinRT is a tightened-up pure GUI environment. A lot of Win32 APIs
are not available in METRO due to that tight control, and I think
COM A... 阅读全帖
s****a
发帖数: 794
19
来自主题: JobHunting版 - 微软没落的根源
.net开源更合理的解释是微软工作重心移到winrt上了 .net上太多的债不想再弄了 虽
然winrt恶心的不行 以后还是要继续发展的 .net就被甩掉包袱了
s******v
发帖数: 4495
20
来自主题: Stock版 - 大家千万不要买INTC
Only 20% of Intel Rev is from server, more than 70% from PC.
What do you mean transaction cost? Intel i3/5/7 is priced at $200 level,
while the typical price of ARM cpu is only 15-30. Intel has much better
performance, but most of average pc users don't need that high power if
there is MS office can run on the ARM. And ARM is making steady progress on
the performance perspective. Looking at the arm cpu 2 years ago, and mirror
down the 1-2 year later, you can tell intel is having some big trouble... 阅读全帖
p******9
发帖数: 7130
21
【 以下文字转载自 PDA 讨论区 】
发信人: GoTouch (够她吃), 信区: PDA
标 题: 送 ipad 给老人用,后悔死了
发信站: BBS 未名空间站 (Tue Jul 23 15:16:04 2013, 美东)
老人现在都用 qq 种花
ipad 不支持 flash,玩不了。。。
还不如 winrt,慢是慢点,还凑合能用
不过偶把winrt 拿出来
人一听是微软的
第一句话就说这个毛得 ipad 好吧
s******e
发帖数: 114
22
来自主题: DotNet版 - .NET 何去何从
>在传统Desktop里面,CLR一切如故。在Merto环境下,CLR是位于WinRT之上的
不懂这个,
desktop CLR 在 win32 之上,
metro CLR 在winRT 之上,
有什么问题么? 看不出严重弱化。
r****y
发帖数: 26819
23
来自主题: DotNet版 - .NET 何去何从
解决DLL HELL问题的关键是metadata,所有CLR app都可以使用metadata.
现在的WinRT是unmanaged native layer,直接在NT Kernel上面,而不需要CLR。Win32
,COM,.NET API和HTML5/CSS3 API都是WinRT里的小子集。所以,现在.NET在桌面端的
替代开发方式更多了,地位是比以前弱了。在服务器端,.NET是微软平台唯一的官方
选择,所以地位没变。
r****y
发帖数: 26819
24
来自主题: DotNet版 - .NET 何去何从
HTML加JS在微软WinRT平台就是rich client了。
这个话题就到这里吧,以后还有XAML,但没有SL了。HTML在WinRT是不是ironPython,
看看再说。
r****y
发帖数: 26819
25
来自主题: DotNet版 - .NET 何去何从
这是不假。但对于RT API来说,其它语言也是来调用API。API就是做这个用的。应该说
微软在WinRT上给了JS跟C#、C++同等的地位。那回过头来问,为啥给JS这么高的从没有
过的地位?还不是因为JS的人气,因为现在client端的潮流是HTML5+JS+CSS3,这样在
用JS写其它程序的人可以很方便地顺手开发WinRT上的版本。换句话说,微软很在乎技术
的延续性,这也就是为什么SL虽然死掉了,但是微软要把XAML延续下去的原因,SL插件
平台可以没有,人气得保留下来。一个道理。
r****y
发帖数: 26819
26
来自主题: DotNet版 - .NET 何去何从
就拿微软的WinRT平台为例,以前要做一个Win App,需要Win32 API,后来需要MFC,后
来需要.NET,现在只需要JS + WinRT API,对非微软平台的程序员来说,学习成本还是
在一步步减少。
mobile app确实还不能完全由HTML5取代。不能说mobile app就是HTML app。只不过web
下一个功能如果不用plugin就做得到,那么这个必然胜过其它用plugin的,是现在的趋
势。就步步为营往前走的方向来说,HTML5没有问题。起码你前面说的那几条,不会有
问题。
w*******j
发帖数: 70
27
10 skills for developers to focus on in 2013
By Justin James
December 16, 2012, 6:21 AM PST
Takeaway: Development trends that began to emerge in 2012 are picking up
steam. Here’s a look at the must-know technologies for the year ahead.
Editor’s note: At the beginning of 2012, Justin James wrote a list of
technologies that were gaining momentum in the dev world. Now he revisits
that list with an eye toward 2013.
Looking back on this article after nearly a year, I’m struck by how quickly
some of t... 阅读全帖
w*******j
发帖数: 70
28
10 skills for developers to focus on in 2013
By Justin James
December 16, 2012, 6:21 AM PST
Takeaway: Development trends that began to emerge in 2012 are picking up
steam. Here’s a look at the must-know technologies for the year ahead.
Editor’s note: At the beginning of 2012, Justin James wrote a list of
technologies that were gaining momentum in the dev world. Now he revisits
that list with an eye toward 2013.
Looking back on this article after nearly a year, I’m struck by how quickly
some of t... 阅读全帖
1 2 3 4 5 6 下页 末页 (共6页)