Discussion in 'Windows 8' started by FaiKee, Feb 14, 2014.
You need to login to view this posts content.
oh hehe, FaiKee, now you are denying Azure RemoteApp is "Windows-as-a-Service" ? you are contary to yourself here, because if you want to make your Azure slide and "Platform-As-A-Service could apply to Azure, it could apply to Windows too" sentence to make ANY sense at all, the only result you can get is just that, Azure RemoteApp.
as I said, Something-as-a-Service is a vague term with many possible interpretations, and Azure RemoteApp IS "Windows-as-a-Service" in one of many meanings of this phrase, and ironically, this is the same meanning as Platform-as-a-Service as in Azure and your "Cloud-Services" slide, and its clearly NOT the same meanning in that job posting. so .... I really dont know what you are talking about here. not anyone's problem, though.
You need to login to view this posts content.
I was not guessing about how WaaS work in the post above, did I ?
what I pointed out was this:
1, IF, WaaS works like anything on your slide, THEN, it is Azure RemoteApp. but you are laughing at this.
2, IF, WaaS doesn't work like RemoteApp, THEN, you slide is also laughable.
I didn't guess which is true, but I think either way, you are laugh at yourself.
I didn't accuse you of posting fake infos in the post above, did I ?
and I didn't ask for 'verification' in the post above, did I ?
I was asking for a 'clarification', witch is different than 'verification', right ?
because "Windows code name Threshold with a possible release name Windows 9"
is totally different than something like "Windows code name 9".
and Windows code name 9 is a new thing to me, not even mentioned in your famous screen shot of someone's profile.
so are you sure you are talking about "Windows 9" ? or "Windows Codename 9" ????
in other words, is '9' actually a code name ? or possible release name of some version of Windows with whatever code name ? or both ?
@NaiveUser, choose what you wish to think - I am not joining your circle game either, so long.
LOL, @NaiveUser, to-day I've got some time to kill, so have the luxury to hang around in your circle game.
You had already showed that you have your own idea of how WaaS should work, otherwise you couldn't have said(in another previous post)"it has NOTHING TO DO with anything on your slide"
- I didn't laugh at "WaaS work like the slide", I laughed at MJF taking Azure RemoteApp as WaaS(The WaaS worked by another existing team in MS who started recruit new engineers).
- Couldn't see what's laughable, unless your thought my posting the slide was to suggest how WaaS would work- I trust you were constantly hard-stamping this concept.
"Windows CodeName 9" was mentioned by another Taiwan MS guy in 2012, after win8RTM, you could make all kind of guesses or pointless jokes over "Windows 9 or Windows codename 9", I don't care.
FaiKee is talking about the 'built by: win9rel' thingy.
in some header files inside Windows SDK, there are texts like #if (NTDDI_VERSION >= NTDDI_WIN9)
these appeared since Windows 8.1 SDK, some of them actually changed to NTDDI_WINBLUE in RTM bits, but some are still there.
Ok, looks like you are right, "Threshold" and "Windows Codename 9" ARE 2 different thing, 9 was just another Windows Blue (8.1) codename, Threshold is Windows vNext, aka "Windows 9"
Come on, all those DLLs you showed were in 8.1 RTM already, that and NaiveUser's tweet prove that win9rel was just an 8.1 thing, not vNext!
Which ones? Because the first couple of ones in your list were compiled on August 14th 2013!
EDIT: they're all August 14th, except for 2 who were compiled on May 10th...2013
Oops! Sorry made a errror there, anyway, like we agreed, stick with your trusted MJF's words until showtime, no point to discuss things over vacuum.
And no point in providing 'evidence' you don't even fully understand yourself and then blindly dismissing NaiveUser's explanation
Let's just wait until showtime
I didn't dismiss @NaiveUser's explanation, I just pointed out that he was probably talking about build 9220~9600 with the MS guy, don't believe any MS people would discuss about or after build 9622 in a open twitter.
Edit: Ooops, sorry again, they might discuss about PowerShell build 9740, why not try it?
Also, I believe I didn't provide evidence, right ? I think it didn't look like a "evidence" to myself.
We are discussing some FACTS, how's that has anything to do with stupid build numbers ? do you think a fact will suddently change or becoming meaningless when some nightly build of certain software was built ? or do you think they will change code name every build ?? really dont know what you are talking about here
IF that Taiwan guy was really talking about post-8.1 builds of Windows, then I think the code name 'Threshold' was not decided yet at that point, so 9 is still just a placeholder for v.Next. so what ?
and '9' as a placeholder is not 'randomly chosen' of course, it is the next natual number after 8, or 8.1, so what ?
and why you are so interested in 9740 in PowerShell builds ? its just an FBX feature branch specially for Management Infrastructure stuff, not interesting at all. I think you should be more interested in the 9727 build in CoreCLR inside ASP.NET vNext, since thats winmain branch.