Good lord what a moronic piece of drivel. It screams "I have no idea how this product works, but I won't let that stop me from bashing it!"
- Are you the only person in the world without a charger in your house? If the battery on you phone or tablet gets that low, you can charge it while watching the show.
- It is possible to share smartphones and tablets. Somehow multiple people can control a TV despite only one remote control.
- Any device can control any Chromecast connected to the same wifi network. And can stop, pause, or rewind a program started by another device.
- And the worst, most blatant example that you have no idea how the product you are bashing works. When it comes to streaming shows from the internet like on Netflix or HBOGo or whatever, Chromecast doesn't actually stream from the device that started the program. The device gives the Chromecast the location of the stream, and the Chromecast accesses it directly. If you need to run to the grocery store, it keeps playing even if you take your phone with you.
A someone that easily uses a Chromecast with my wife and children, you need to shut up until you learn about what you are bashing.
High-level theories and models and UMLs and chess board Java CS projects are most definitely useful to 99.9% of tech employers. High quality employees will apply those concepts to write efficient, maintainable code regardless of the particular language being used on a project at a tech company. Once the students have learned those high-level concepts, learning how to apply them to the syntax of a particular language is the easy part, and the student will also be able to go out an learn multiple other coding languages with ease. Like the file out question you mentioned: they might not know how to do it in a 4-line script, but they will know the general algorithm behind how to do it (or at least they ought to if they've learned high-level theories). Teaching them the syntax for it in a particular scripting language is a minimal investment after they are hired.
Techology evolves, software suites come and go, but the theories will be always be applicable. Unless you want the students to become useless once a particular software suite becomes outdated, you teach the theories that will always be applicable. Tech employers that hire solely based on knowledge of a particular software suite are very short sighted and get what they deserve.
Really Windows Phone is not a bad OS and if it was not made by Microsoft it would not be soo bashed here.
This is part of it - people associated Microsoft with horrible experiences when locked in to the Windows monopoly. This deters the "just works" folks compared to iOS. Also, it is just as locked down as iOS. This deters the tinkerers and other people likely to develop apps compared to Android. Combine those with the fact that iOS and Android were already pretty entrenched by the time it came out, and no one really had a good reason to choose it over the other two.