It's not just tablets, organisations everywhere have for years been deploying new technology that brings with it the promise of improved productivity. In reality it often does not... You take old hardware and old software that works just fine, and spend a fortune replacing it with new faster hardware running new slower software. The end result often isn't any faster, and users have to take time getting used to it while not using any of the new features. Often the new version is much worse than what it replaced, and instead of the software supporting the business, the business has to adapt to the way the software works.

Not at every entry point, security should be a serious consideration on every device. Work on the assumption that everything is directly exposed to the internet and start from there.
Trying to only monitor the entry points is the problem, if anything makes it past your entry points then it could have free reign over everything inside.

Then work in the office...
Google's plan is to do away with a local corporate network, so that the network available in the office is just an internet connection and you connect over the internet to whatever services you require. If you are in the office then your connection will be just as fast since the services you generally access are just as likely to be local as they were before. It's just that now instead of being on a flat network with insecurely configured devices, you will connect to those devices over a public network and they will be hardened just as you'd expect servers connected to the public internet would be, instead of assuming that only trusted employees can get to the servers and slacking off on server hardening.

Endpoint assessment is a stupid idea, a malicious (i.e. owned) client can easily lie to the server while a legitimate user wanting to use a configuration not thought of by the sysadmin gets screwed.
Also having to use a proprietary client is terrible, you end up being unable to update your OS because doing so can break the third party vpn client, or finding yourself with extremely restricted choices as to what os you can use.

Most corporate users, and home users for that matter have no idea how to repair computers. They will simply send it back to the manufacturer to be replaced.

You run a graphical web browser on a file server? wtf?

A lot, if not most users only use it because they're stuck with it at work.. It's amusing how the user-agent stats swing significantly at weekends and evenings on some sites.

What about if you purchased copies of the games, and played them on an emulator instead of buying the official hardware?
Not only would this not be piracy, but the console manufacturer would benefit because the hardware itself is usually sold at a loss, and the user would benefit as they could use hardware they already own instead of purchasing extra hardware solely for playing games.

The PS4/XB1 will remain the same spec, while PC hardware advances... Before too long it won't be very difficult at all.

The monopoly commission should investigate exFAT...
It's not the best filesystem on offer, there are many much better filesystems which are more suitable for use on flash media, and which are available royalty free... The only reason anyone even considers exfat is because microsoft will intentionally never support anything else.

Even with access to the source, we're talking about running services rather than code you run on your own hardware. There is no reason to believe that the source they provide is the same as they're running, and there's no way to tell who else has access to their systems.

Most other big providers such as google and yahoo run most of their stuff on open source software, so while we have the code we have no way to tell what they're doing with it.

Or they can simply provision the availability of service at the boundary of your property, and make it your responsibility to deal with getting it across your own private land (or not, if you dont want the service).

Note that at some point every service anyone uses will have had to cross private land in that way, any house built before the days or electricity, sewerage, telephone and running water had to have these services retrofitted at some point. Installing fibre is simply the next logical step on from installing copper telephone wires.

Sure, it is often more expensive to replace something when it catastrophically breaks, and your more likely to screw the process up because at that point you no longer have the luxury of being able to plan the transition.
That said, IT departments are often sailing on luck alone, lots of places have no redundancy, no DR plan, no backups, massive easily exploitable security holes etc and yet they get away with it out of pure luck. So this crufty old system that needs replacing may well continue running for a long time.

The problem is that upper management rarely understands IT, they see it as a necessary but unwanted cost and will try to minimise it. They also rarely see any downside to minimising costs.

And then those who do understand IT are generally not very good at explaining things to those who don't, or they create the wrong image (geeky etc) which causes upper management to disrespect their opinion.

Plus the inherent complexities of the problem...
Someone who is extremely competent will be able to keep a system running on a low budget, but not everyone is so competent and the typical people doing the hiring aren't qualified to judge IT competence, plus while a lot can be done with a small budget and lots of knowledge there is still a limit...
Also its possible to make a lot of extremely poor decisions in IT and simply get lucky... You can do with no redundancy, no DR plan, poor security etc and if your lucky nothing will go wrong and you won't get hacked. A lot of companies are in this boat, basically riding along on luck with a highly risky setup.

Upper management focuses on the bottom line because thats what they understand, it is their core business and they founded the business or were hired into a high position in it specifically because they understand it... They often don't understand other areas of business, and will often trust the wrong people (ie salesmen instead of their own staff) when it comes to matters they themselves don't understand.

Another serious problem is short term thinking... Your existing IT system may be slow, unreliable, clunky, but it limps along and the staff are familiar with it... If you replace it, users will have to get used to the new system, a new way of working and probably a new set of bugs to work around. A new system may cost a lot to implement, may result in a long period of reduced efficiency as staff get used to it etc.

And then you have history, many IT projects promise to deliver all manner of amazing improvements, but the reality when implemented can often be a system which is worse than what it replaced. This happens in a number of ways, external salesmen talk up a product which is nowhere near as good as they claim, the purchasing decision is made by upper management or by IT without any involvement of the people who will actually be expected to use the system.
And on the flip side, those people expected to use the system will often resent and resist change simply because they've had experience with poorly implemented systems in the past.

So you have a lot of hurdles to overcome implementing a new system, and although the end result *can* be a significant improvement, often it's not and in the short term there will often be a negative impact to the bottom line.

A lot of people just overwork themselves trying to get everything done... If they succeed, then management think everything is just fine and ignore the fact you've been working twice your contracted hours to get everything done. As far as they're concerned, the existing staff are achieving everything required in the contracted hours and they have no need for extra staff. If you keep working like this it creates precedence and upper management will expect things to continue the same.

They will only take notice if there is an obvious problem, ie projects getting delayed and other areas of the business complaining about the delays.

The problem is if you suddenly stop overworking yourself and doing so causes these delays, management won't accept that you were overworking before, they will assume that you were doing your contracted hours before and are therefore slacking now.