[citation][nom]math1337[/nom]Custom UI in metro?--possible, but any apps that break "guidelines" will be rejected by the store[/citation]
Show me where in the guidelines you've got support for this being a sweeping generalization you can make that disallows a "custom UI".
Performance?You want performance with no access to native code? no direct access to system function? Limited unsafe code? WinRT give access to a subset of managed libraries. You think you can write high performance c++ within the WinRT box? good luck.
Unsafe doesn't mean fast, and safe doesn't mean slow. WinRT is just a layer of abstraction that's primarily designed to INCREASE responsiveness. The restrictions keep you from doing things like performing network operations in the main thread, and other newbie mistakes that destroy performance. This is why most of the APIs are asynchronous. Performance.
You keep saying that WinRT is going to be slow, but you've yet to actually say why. Stop making things up, spouting a new lie in every post is not only easy to spot, but makes you look stupid too. If you really want to point to the restricted API and say that makes WinRT slow and bad, tell me how. The lack of what functionality, exactly, is the culprit? Show off that developer knowledge you keep pretending to have.
You think devs will be piling at the door to get in the windows store?Mozilla won't make Firefox for WinFo7 because of the extreme limitations set by the store. You think they'll make it for metro? You know what, the WinFo 7 App selection still sucks. I wonder why?
Yeah, you're just totally wrong here. Mozilla abandoned Firefox on Windows Phone 7 because of the requirement to develop in C#. It had nothing to do with the store, but the platform. Try again.
New features in VS? They'll still be there for normal c++ and .net apps
Yeah, you have fun writing your xaml interfaces for native C++ projects. Oh, wait, you can't. The new features are tailored to the new display technology.
Want to run new APIs? you can still use them as long as they're not metro APIs
You must have missed the part where WPF and MFC were deprecated as of the next release of the SDK. They won't get API updates. What you've got now is all you're ever going to get.
Want to run on arm? write a web app.
Oh, so you bitch and moan over and over again about how WinRT is some performance boogeyman, but running inside a goddamn web browser is fine and dandy? You'll say anything to win this, won't you?
That's about what you're doing developing in whatever HTML5/javascript/winRT stuff that Metro is made of.
Yeah...no. You can indeed use javascript and other unusual languages for the display, if you want to. But it's certainly not required, and it's only for the display portion. You know, the portion for which performance doesn't matter. If you're hammering your GUI thread with performance intensive tasks, you're a moron and you deserve to be frustrated by Metro's guidelines on that kind of ***.
Using my Win8 Dev preview build App, I think the VS improvements were a bit more emphasized
Again, I'm lost as to what you're trying to say. Are you trying to say you were following Build? Because from what you wrote, I'm skeptical. Visual Studio certainly wasn't front and center, though it would get used a lot because that's the Microsoft way of developing software. Saying it was the focus simply because it was present is a lot like saying CES is about tables because all the products are sitting on them.
How about this for a change. Why don't you pull your head out of your ass, stop reiterating your idiotic points about how Metro is the devil and will never be adopted, and actually address any of the points I've brought up. Why don't you get back to the original point you were trying to make, because you've been trying REALLY hard to change the subject into a broad attack on Metro.
This all started because you
insisted on shouting over and over again that nobody would recognize Windows 8 on a tablet, because nobody on the desktop version would be using Metro.
Please, succinctly, explain to me why exactly the world will shun Metro without saying "ZOMG METRO IS DIFFERENT AND SCARY!" Explain to me how there will be no brand recognition because the tablet doesn't have a desktop interface.
Do that or shut the hell up. You are about the loudest, most ignorant wannabe developer I've ever seen. Running inside a browser is the same as using Javascript for the display layer? Lack of access to the entire Windows API hurts performance? Rendered interfaces won't be used because there are guidelines on interfaces for the Windows Store? You're trying way too hard, man.
It's like you get a half valid idea about the restrictions on WinRT, but then need to blow it up and show how that one little thing means nobody's ever going to adopt. By the time you've made your point (and I use that phrase loosely), you've lost all touch with reality.
Restrictions and app store guidelines will stop people from developing? Look at the iPhone, you dolt. People won't use the new metro interface (followed shortly by claiming that they'll use it, but only as it was intended, as if this were a bad thing) because it's not the way they've always done things? It's close enough to the way they've done things, and simpler to navigate. It's a small learning curve at best.
Your points ring hollow, your lies and misrepresentations of the truth are the only things that stand out in your posts. If you had a valid point to make, you lost it somewhere while shouting over and over again how you were right rather than acknowledging that maybe not everyone will walk into Windows 8 with a "Die Metro Die" mindset.
Not everyone is a power user. Not everyone is so in love with their start menu as you are. But then again, most people wouldn't come onto a forum and rant at such great length about topics they know very little about, like you have.
If I had to guess, I'd say you knew about as much about programming as the average high school geek, and absolutely nothing about software development processes. Might have had a course, maybe self taught. You know two,
maybe three languages, but only one well enough to be called fluent. You've never touched any of the more difficult aspects of programming like thread safety, networking or working with bit streams (not setting bit flags, that *** is child's play).
Your small amount of experience put you a head and shoulders above most everyone you know, so you start to think you're hot ***. You post on computer forums showing off your knowledge, with a healthy dose of sarcasm and self importance to really hammer home that you know your stuff. Problem is, you said something really stupid and an actual software development professional read it.
I've probably forgotten more programming languages than you know. I write more lines of code in the average workday than you've written in your life. I bust out dynamic programming solutions with concurrency controls like they're nothing, while you go look up what dynamic programming even is. I've written assemblers, virtual machines, low level network traffic analyzers, HTTP servers, encryption algorithms and more.
There is real knowledge behind what I'm saying, not to mention more than a decade of experience and a degree. Repeating your idiotic points over and over again might work on people who don't know what they're talking about, but I do. I eat, drink and breath Windows development. It is my job to keep up with what's happening, and use those new technologies once they become available.
Do you really think you know more than me? Have great insights that my puny mind just can't comprehend?
Or are you just wrong?
Facebook
Twitter
Instagram