Caporegime
I thought the Pro was launching 3 months after Windows 8?
*** The Official Microsoft Surface Thread ***
- Thread starter Bennie-Mac
- Start date
I heard that too, but it makes no sense.
As soon as W8 is out other hardware manufacturers will be getting their own versions out. MS simply cannot wait 3 months to launch the Pro version, everyone will already have a competitors device.
Caporegime
"quotation or run along." No where in this thread have you agreed that the Surface will have problems, prior to our squabble.
"crummy" is anything but fact. It's hyperbole.
MS also have a track record of lazily tacking stuff onto Windows. Not everything, and not as bad as what apple have planned for iOS I'll accept and concede on, but they aren't exactly squeaky clean themselves - so you need to accept that there are those who have doubts about it. Particularly when MS's own demonstration of the product goes awry with crashes/freezes which frankly, has become a "Microsoft-ism" because it happens so much. Even on these forums the number of times people say "Wait until SP1 before getting it" is high.
"crummy", "stupid route", "dumb dumb dumb", etc. the blatant air of, well, snobbery in that post quite frankly.
You did nothing of the sort. You've not limited/restrained any of your posts to "certain" flaws at all.
You're the one putting words in, after the fact, to try and put a different angle on something you are being called out on. Who's trolling now? You wouldn't be doing that, would you?
Oh, it'd be you. Wrong end of the stick? How is that, exactly? You said, in your own post, that the entire tech media industry didn't 'get it' - exactly how is that you not posting that the entire industry got it wrong?
Right. So you are saying the entire industry got it wrong. I didn't get the wrong end of the stick. Huzzah.
It is in full context. The entire post is there, and you were practically replying to your self. You give a list of problems that other platforms have, then go on to say "W8 won't have those problems" - sorry, but merely by quoting that entire post puts it into full context.
You've not mentioned a single problem that the surface will or at least could have. Kinda something you might be forgiven for doing in a thread dedicated to the Surface, don't you think? The opportune moments you choose comment on stuff from other platforms to defend MS Surface, at considerable length and detail (which I'm not holding against you in itself) but never once commenting on a potential flaw with Surface is suggestive that you don't think there will be any problems. People get called "fanboi" for less.
An example of how what you pointed out as overpriced development is nothing of the sort, just like the rest of the post it was in. Also a flippant comment.
You wouldn't be trolling again, would you? Surely not!
"Them" being who, exactly? Only those who already use the MS stack?
Granted they probably won't need to buy an arbitrary license - something I do hold in disregard for Apple development -but there will be some learning for them to do, even if they already know the language(s) involved. If they don't have VS already they'll need it.
I actually agree with this. Except the "cheaper" part to a degree. There will be learning costs involved regardless of arbitrary restrictions. This is everyday stuff for everyone across the board, of course. New tech = new learning to be done.
Uh huh.
You wouldn't be trying to put words in my mouth, would you?
Still not the list you tried to claim it.
Spin. Not that niche.
More arrogance, and putting words into my mouth. Perhaps you need to do some research on simple manners? I also thought you were critical of stuff that's "baked right in"? Not so with MS.
So that's a lot of learning to do then. Also not sure on why this is relevant to a discussion about how your viewpoint holds surface as "without fault."
More arrogance. And yes, it is geared towards the thread title -yet you seem to only be able to list faults with competitor products and then finish with "MS won't have that problem."
Nothing, but without any speculation about what problems (new, and/or existing) it might introduce is bit.. fanboyish.
No, it's only part of it.
Zzzzz.
Which has to be considered at compile-time. Ergo, you cannot avoid the macros.
We did just that, thanks. Still needed to use the macro to determine if it is silverlight or not. Can't be avoided. If it's not a macro, it's an if on a config variable. Notably this happens with WPF a lot - Silverlight meaning to be a subset of WPF, but it's not it has API differences which require the use of #if SILVERLIGHT.
Ya think?
Who said anything about leaking between layers?
Are you putting words into my mouth again? That'll be a "yes" then.
Apart from having to use it to determine if Silverlight is in use, or not. Hmm.
Hallelujah! Acknowledgement from NathanE that MS don't always get it right. It's only taken this long.
Absolutely relevant.
Except where right above you've just criticised it for needing to have wrappers to be used with a .NET library/libraries.. contradiction.
What stick? You've grasped the wrong end. All along I've made the same, simple point - you are perma-biased toward MS products, to such a degree that you don't even speculate on problems a new product might present in a thread about what to expect from said product.
You'd might as well have told me "not to worry my pretty little head about it" or other cliché arrogant statement.
More arrogance, again.
I, nor Caged brought the ex-moderator thing into the discussion - you did.
Don't flatter yourself. I'm posting on an internet forum, not starting a revolution.
Aww.
Mr. Kettle, Mr. Pot left you a message: "Black."
Prepare yourselves! More arrogance incoming!
Mr Kettle, Mr Pot called again.
I've nothing to feign. This is also a terribly ironic statement to make. You are trying to feign the upper hand by claiming I am feigning the upper hand. Nobody has the upper hand. It's a squabble on an internet forum, probably glossed over/skipped by everyone except us.
No misquotations - deliberate, or otherwise. From me at least. You've been plentiful in that regard though.
Last edited:
Caporegime
Seriously get a life. That must have taken you ******* ages.
Soldato
Pathetic isn't he. He was still editing it to 1,40am! If there was any doubt left that he was trolling... well it's gone now
Last edited:
I've just had a though... how will the OS know which keyboard to use (on screen or hardware)?
Unlike a slider phone or the keyboard docks for the iPad, the keyboard can't be 'disconnected' or turned off as its part of the case which I assume will remain attached at all times (the rubberised ones at least). So how will the OS know wether to open up the on screen keyboard or not when you select a text input field?
Unlike a slider phone or the keyboard docks for the iPad, the keyboard can't be 'disconnected' or turned off as its part of the case which I assume will remain attached at all times (the rubberised ones at least). So how will the OS know wether to open up the on screen keyboard or not when you select a text input field?
Caporegime
About 10mins to post, and later on an edit. Nice insults btw, really mature.
The covers have in-built accelerometers which can detect whether there closed against the screen, folded out in front of the tablet or folded back.
Soldato
Honestly, what the hell are you going to do next, quote every individual word he says and reply with a contradictory word?
Caporegime
Caporegime
And yet the point I've made all along still hasn't been refuted \o.
Soldato
I hate to tell you this but even if you did have a point you've presented it in such a way that nobody cares anymore. o/
Ah, cool. That should work.
Soldato
When will the first surface device be avilable?
Win8 launch I would imagine oct 26th.
I wish they would release some devices to reviewers and tell us prices(not just Ms all release devices), same with win8 phones, how much do I need to save.
Last edited:
Nope, next one as far as I know is //build/2012 which is oct 30th-nov 5th so after release.
Wonder what it could be.
Last edited: