Dj_Jester said:
Blatant inference/implying that MS/W8 won't have those flaws.
I said, agreeing with someone, that of course it will have bugs and flaws.
You quote me saying that W8 and WP8 will, essentially, be fundamentally more advanced than iOS (and this is not opinion, it is fact). And that it won't have lazily tacked on integrations to Facebook where something better like a Contracts API exposed to third-party usage would suffice.
How is that now a "blatant implication that W8 won't have those flaws"?
I merely stated it won't have *certain* flaws and limitations that exist in current rival offerings. How did you extrapolate that to mean it won't have *any* flaws and limitations whatsoever? You wouldn't be putting words into my mouth, would you?
Dj_Jester said:
Apparently the entire Tech media industry is wrong, but you are right?
And once again you get the wrong end of the stick entirely and make yourself look like a complete idiot.
This has nothing about being right or wrong, me and them or anything. It was simply an amusing reference to the fact that tech media back then couldn't make any sense of the MinWin project. I distinctly remember reading articles suggesting Microsoft was working on a whole new OS from the ground up and that MinWin was it. There was even Slashdot joining in on the action suggesting Microsoft had finally "seen the light" to start debloating their operating system. Ever since W7, the Server Core and Hyper-V projects; the purpose of MinWin has been visible for all to see but even still many of the tech media still simply do not understand it.
Dj_Jester said:
"Windows 8 tablets have none of these problems." O rly? Quote in full context before you cry that one.
No that's not in full context. Not the piece you quoted. Because if you had actually read and understood it you'd see I was referring to a specific set of problems that exist today on rival platforms. The versioning issues of Android, the language barrier issues of iOS, etc. I said that W8 won't have these problems - because it won't. At no point did I suggest it wouldn't have *any* problems. That would be ridiculous. And it is equally ridiculous that you are trying to spin things as though I said that.
Dj_Jester said:
And, whilst I'm quoting this one, you seem to think iOS development is exclusively expensive. MS development is hardly cheap. Many, many, many software houses charge upwards of £1,000 a day for MS stack development. SQL Server DBAs scoff at that amount.
I'm not sure at all the relevance of comparing the cost of a iOS app developer to a SQL Server DBA. But in any case, you missed my original point (again), which was:
From post #189: "
Microsoft's solution is that a company can still re-purpose their existing developers to write their W8 Metro apps. There is no massive sea change to undertake."
I shall expand on that now since you clearly didn't understand. What I'm saying is that any development team with C++, C#, HTML/JS human resources already onboard (and let's face it, that is pretty much all of them) can simply repurpose them to do Metro development. Whilst it is totally possible to repurpose such a developer to write Objective-C, it takes longer and is more costly, and you also have to find a willing individual first.
W8 Metro development will be cheaper, by far. Because you can write real Metro apps (not "websites" like you seem to think) using HTML/Javascript. So literally, almost overnight, every low-salary web developer can jump on the Metro bandwagon and start producing apps.
Dj_Jester said:
Developers still get paid what they get paid, regardless of what tools they use to develop. Sure, a few niché markets here and there may have mild increases in prices - but the extreme differences you seem to think there are, just do not exist, except for some legacy stuff like zOS developers because most of them are in retirement.
You'll see in a few months from now how quickly and cheaply a Metro app can be knocked out. Until then, I guess you'll just have to continue on being extremely sore and irritated about someone's opinion on the internet.
Dj_Jester said:
"HTML/CSS/JS, C++, C# to VB.NET" - so developers can choose between making a website, or a .NET app. Hardly an exhaustive list, but you've spun it none the less to sound like a great deal of choices for developers - which it isn't, and is exactly what you complained about the iOS equivalent choices: Website, or Objective-C.
It's a longer list than what Apple has. I don't see how one language (and an incredibly niche one at that) versus *at least* four mainstream ones can be considered as "spinning". By "at least" I am of course referring to the fact that the .NET CLR is language agnostic and there's a whole raft of less-mainstream languages built on top of it. The big one on that list is of course HTML/JS. Writing true Metro apps with that is, as I said before, going to open up a huge low-cost developer base of Metro apps. And no, these aren't at all the same as "Offline web apps with an icon" like on iOS. Again, do some research and educate yourself about how the HTML/JS apps are baked right into the WinRT and XAML engines. They can inherit and use all the same styles, positioning, layout mechanisms etc that a XAML-authored application can. They can even access certain WinRT functionality through JavaScript, such as sensors, GPS, touch gestures etc.
Dj_Jester said:
People just focus on the bad points - just like you have ignored Apple's great success and only focused on the limitations, yet the complete converse when discussing any of MS' products - and that's not limited to this thread, I might add. You skim over the MASSIVE failures they have had, and continue to praise them, and hail as successes, things that many see as a failure. This very much includes your dismissive unfounded statement that when someone is forced to use #if SILVERLIGHT, that it simply must be a failure in their design. It just cannot be a problem with MS' integration of siliverlight in .NET. No siree.
Is that what this is all about? I've ignored Apple's success? I'm sorry, but I thought this was a Microsoft Surface thread where, you know, the subject of conversation is geared towards the thread title.
What exactly is it that you clearly find so offensive about listing the shortcomings of existing rival products *that are on the market* versus a new upcoming product which, based on publicly available information, has clearly solved some of those shortcomings? This is what technology discussion is all about. It's what technology and the constant evolution is all about. If people weren't allowed to discuss this sort of thing then we'd still all be running, I don't know, Symbian powered phones I guess.
And all that clap trap you KEEP bringing up about pre-processor macros for Silverlight specific code... Silverlight is a presentation layer. If you have designed your application correctly you'd write a presentation layer implementation for each different type of presentation that you require. So you might have a web front end, a Windows application, a Silverlight applet etc etc. There really shouldn't be any reason AT ALL for leakage to occur between layers (or differing implementations of those layers) to such an extent that pre-processor macros are needed. Have you ever heard of MVVM? Of course you haven't. Because otherwise you'd realise that this whole line of argument about Silverlight is utterly deluded.
What's amusing about the Silverlight thing you started is there is actually a far better example you could have and should have used to fortify your argument that Microsoft has damaged its SDKs in the past by segregating them. And that example would be .NET itself. More specifically, that the 2.0, 3.0 and 3.5 versions all ran off a 2.0 CLR. And then 4.0 wiped the slate clean. There is also another example you could have used whereby an assembly that is targeting the WinRT cannot use regular .NET libraries. Which will cause developers to have to write wrappers around all their WinRT code. In any case, none of this is relevant. I said that there will be one SDK, called WinRT, and that that SDK will version gracefully over time. I stand by that. The fact that you ended up grasping the completely wrong end of the stick is not my problem.
Dj_Jester said:
You've "done your homework to come to my conclusion" - could you possibly be any more arrogant?
Why is that arrogant? Is it because you find my conclusion offensive? I didn't realise we were having a religious debate. I thought it was a thread discussing new technology where, you know, opinions are allowed and they can turn out to either fly or sink.
Dj_Jester said:
Oh wait - you can! Must be the holier than thou, do what I say "ex-moderator" coming out, I suppose. I've done my homework on this. That's how I came to my conclusion. You've got a bit of a rep for it.
Not at all. Caged was implying that I was "being the judge of posts" and I said no I'm merely calling out a trollishly written post (and a singular post, at the time). This has nothing to do with being an ex-moderator. Clearly I seem to bother you very deeply. I'm devastated by that. Maybe you should consider getting that chipped shoulder looked at? Or as a more serious piece of advice: Maybe people here would take you more seriously if your posts weren't littered with an extremely aggressive tone, winking smileys trying to feign having the upper hand, deliberate misquotations that can be resolved by a reader simply by backtracking a couple posts to see what was actually originally said and just general misinformation that can be disproved by a top 3 Google hit.