web analytics

Home of my tech rants, free programs, and a story or two…

Windows 10 Build 10166, A “Hail Mary” if I’ve ever seen one

A month ago I talked about how I thought that Windows 10 wasn’t going to be ready by July 29th because of how many bugs still existed in the older Build 10130. I also said that Microsoft would have to pull off a Hail Mary of a miracle to get this thing together for the July 29th release.

Well, with Build 10166 it appears that Microsoft managed to do just that, pull off a Hail Mary of a miracle because Build 10166 is stable, rock-solid stable. I didn’t at all think it was possible but they did it, they actually did it! I even ran 10166 as an every-day use OS for some time before I went back to Windows 8.1 to reserve my free Genuine copy of Windows 10. (To see why I did this, read this post)

A warning to those people thinking about upgrading to Windows 10 Technical Preview…

Those people who have upgraded to Windows 10 Technical Preview WILL NOT be eligible for the free upgrade to Windows 10. Those users will be forced to reformat and reinstall a prior version of Windows (Windows 7 or 8.1) before they can get their free version of Windows 10. Not only that but their prior version of Windows 7 or 8.1 MUST BE A GENUINE license or they WILL NOT be eligible for the free upgrade to Windows 10.

If you want to upgrade from Windows 10 Technical Preview to Windows 10 RTM, you have to ask yourself these three questions…

* Do you want to continue as a Windows Insider and keep getting preview builds after 7/29?
* Or do you want to upgrade your Genuine Windows 7 or Windows 8.1 system that has been getting Windows 10 Insider Preview builds to the 7/29 release and stop being an Insider?

I want to continue as a Windows Insider!
If you want to continue as a Windows Insider past 7/29 there is nothing you need to do. You’re already opted in and receiving builds in the Fast or Slow ring depending upon your selection. This is prerelease software and is activated with a prerelease key. Each individual build will expire after a time, but you’ll continue to receive new builds so by the time an older prerelease build expires you’ll have received a new one. Since we’re continuing the Windows Insider Program you’ll be able to continue receiving builds and those builds will continue to be activated under the terms of the Windows Insider Program. We provide ISOs for these builds for recovery from any significant problems, but they are still pre-release software. As part of the program we’ll upgrade Insiders to what is for all intents and purposes the same build as what other customers will get on 7/29, but that will be just another build for Insiders, and those who stay in the program will simply get the next build after as well.

I want to opt out of the Windows Insider Program on 7/29.
If you decide to opt-out of the program and upgrade to the 7/29 build you will be subject to exactly the same terms and conditions that govern the offer that was extended to all Genuine Windows 7 and 8.1 customers. This is not a path to attain a license for Windows XP or Windows Vista systems. If your system upgraded from a Genuine Windows 7 or Windows 8.1 license it will remain activated, but if not, you will be required to roll back to your previous OS version or acquire a new Windows 10 license. If you do not roll back or acquire a new license the build will eventually expire.

The problem with the second scenario is that this only holds true if your machine had a prior version of Windows installed (7 or 8.1) and it was a Genuine License. How will Windows 10 know that you had a Genuine version of Windows 7 or 8.1 installed prior to the installation of Windows 10 Technical Preview? It won’t, therefore you will not have a genuine version of Windows 10 after the RTM upgrade.

Those users will have to go back to a prior version of Windows with a Genuine license of Windows before going to Windows 10 to get a free version of Windows 10.

I don’t know how it’ll work for OEM machines that have a key for a prior version of Windows tattooed on the motherboard in BIOS/UEFI but for those of us who have vanilla home-built machines with no OEM key tattooed on the motherboard, those users will have to go back to a prior version of Windows before going to Windows 10 to get a Genuine version of Windows.

My iPhone Experience… Four Months Later

I have had my iPhone 6 Plus for four month now and like anything there’s some things that annoy me about it.

The biggest issue is that sometimes, for no reason at all, Safari on my iPhone 6 Plus will trigger a full page refresh of tabs in Safari. Some people say that it’s because the iPhone still only has 1 GB of RAM whereas most Android phones have 2 GBs of RAM and sometimes even 3 GBs of RAM and that often times is one of the biggest criticisms that hardcore Android users say about the iPhone.

I have done a lot of experimentation on my iPhone. I’d open two tabs in Safari and then go back to the home screen. I would then proceed to open an app, play with the app for a couple of seconds, close it, open another app, play with it, close the app, open another app, lather, rinse, repeat. Every five apps I’d open and play with I’d go back to Safari and check it, my tabs would still be there and not cause a page refresh. Strange. So I would repeat the open app and play with it scenario with five more app and then check Safari again, no page refreshes. What’s going on here? I would have thought by now that I would have exhausted the system RAM and would have triggered a page refresh in Safari; but I didn’t. Very weird, very weird indeed.

Sometimes these Safari tab refreshes would be completely random and the strangest part is, I can’t manually trigger a page refresh in Safari even though I pushed the device pretty damn hard.

One of the greatest thing that I love about the iPhone is that it gives the best battery life I’ve ever seen in a mobile device.

Let’s take a look back at the time I had a Samsung Note 3. I would wake up in the morning after having the phone charging all night. I would go to my computer and put the phone next to me on my desk. I would most often do this on my days off from work. I would just let the phone sit there; I wouldn’t touch it, I wouldn’t do anything with it. It would sometimes sit there for two to three hours at a time without anything being done on the phone. And what was the battery life? 95%, sometimes even 92%. What the hell?! I wasn’t using the device, it was just sitting there doing absolutely nothing. Why did the battery drain that badly? I’ll never know. There’s no reason on this Earth that a device that was just sitting there doing absolutely nothing with no one touching it for hours on end should be down 5% to 8% on the battery.

Compare that experience to the iPhone. I unplugged my iPhone at 10:30 AM this morning. It’s 2:30 PM now. Same exact scenario plays out, nobody touched the phone for four hours. What’s the battery life on my iPhone 6 Plus? 100%. Yes, 100%! I have been able to go as much as three days on a single charge on my iPhone 6 Plus. Last night my battery was at 27% and that was after three days and during the third day I was streaming NetFlix for nearly an hour on LTE and we all know how LTE can chew through your battery like a child to a juice box.

Overall, the Apple iPhone has got to be hands down one of the best mobile devices I’ve ever owned. The battery life is one of the best in the industry. Everything just works. I can’t say that about Android. Android is a hot mess; it’s garbage.

Is Windows 10 ready? Not by a long shot!

From the looks of things with the Windows 10 Technical Preview that if this is what Windows 10 is going to look like, they are going to be in for a lot of trouble. If the release date is really going to be August 31st, 2015 like what Newegg has said it’s going to be, it’s going to be a mess. That’s three months away and there’s still serious issues with Windows 10 code. Correction, two months away.

Why two months? You may ask. Well, you have to remember the release cycle for Windows. In two months Microsoft will release the “gold code” to the OEMs and their distribution partners. That means the OEMs and their partners and other various distribution chain partners will have a month of time to get their products ready before the “official” launch date of August 31st, 2015.

With that being said, Microsoft has exactly two months to get things ready for the “gold code” release and sadly, it doesn’t look at all like Windows 10 is going to be ready for that. There’s still a massive load of bugs that plague Windows 10 and it seems that for every bug they fix they seem to add ten more.

It’s going to take a Hail Mary of a miracle for Microsoft to get things shaped up for the release of Windows 10 based upon what I’ve seen with Build 10130. For being this late into the development process, Microsoft should be simply polishing things up and fixing minor bugs, not the kinds of showstopping bugs that I’ve seen in Build 10130.

If Windows 10 is released the day that Newegg supposedly says that it’s going to be released on, good God almighty, we’re going to be in for a real rough ride. I don’t at all have any kind of faith in Microsoft to pull this thing together. I figure that the first few months after Windows 10’s release it’s going to be hell for their users.

Maybe the Microsoft of yesteryear could pull off a Hail Mary of this importance but not this Microsoft. This is the same Microsoft that has released not one, not two, but several Windows Updates that have broken thousands of computers across the globe.

Their overall code quality, hell, the entire computing industry’s code quality has really gone down the toilet as of late. Microsoft, Google, Adobe, Mozilla, hell, even Apple are all guilty of the same issues with overall code quality as of late. They have all sucked in this quite vital department.

Is this the end of a Microsoft dominated world?

Here I am, and I can’t believe that I’m saying this, but I am seriously looking at the Mac as a future for my computing needs. Why? Well, I don’t like the way that Microsoft is going so if I were to switch to the Mac I really wouldn’t have that much trouble finding software to run on it. A lot of software, mainstream software, is cross platform compatible. It’s not like the dark days in which Windows was it; if you didn’t run Windows you were sunk.

In fact, that’s why I figure Microsoft is going the way they are. They see their one time desktop monopoly slipping away and they are grasping at straws trying to hold onto relevance in today’s cross platform, non-Microsoft dominated world. You can see that in how they are making apps for the iPhone and Android devices. Things like Office, OneNote, Skype, Outlook, OneDrive, etc. They aren’t making these apps for other platforms just for the sake of making them available, they are making them available because they need to or they’re dead.

The computing industry that we have today is not a Microsoft dominated industry anymore and Microsoft knows it. They sat on their desktop monopoly for too long and the rest of the industry flew past them while they were sleeping. But like any big ship it will take time for a gigantic behemoth such as Microsoft to change direction. Unfortunately for Microsoft, other companies that are smaller and more agile are slowly killing Microsoft.

Will Microsoft ever recover and get back to their glory days? I don’t think so. There’s too much competition and smaller companies that can quickly and easily change direction at a moment’s notice.

One of the problems that Microsoft has is that they are dragging behind them almost twenty years of code dating back to the early 1990s. One of the biggest advantages of Windows is that it’s compatible with legacy software but in doing so it’s dragging behind it twenty years of buggy, security hole ridden code from the dark old days of computing. It would be in Microsoft’s best interest to simply scrap Windows as we know it today and rewrite the thing, from the kernel upwards. But that’s never going to happen. Like a rusty bucket, it keep leaking and they keep patching it.

Other companies that are smaller, more agile, and don’t have to answer to decades of legacy software can change direction and make their software leaner, cleaner, more efficient, and faster than anything Microsoft has.

Samsung 840 EVO and the NAND flash 20nm wall

A new firmware has been released for the Samsung 840 EVO and it appears to have fixed the issue with speed degradation of older data but… and you knew that was coming, it has some side effects.

Samsung has stated that there will be periodic refreshes of the data in the background either by the firmware of the SSD itself or by a tool in the Samsung SSD Magician. To quote Anandtech…

Ultimately Samsung’s second fix is a bit of a brute force solution to the problem, but at this point there doesn’t seem to be anything Samsung can do about 19nm TLC cell charge decay other than to refresh the data, as the problem is intrinsic to the NAND itself. Pre-release versions of the firmware show that this fix works, and conceptually this is much more likely to work over the long run than Samsung’s initial fix. The tradeoff is that it does consume P/E cycles to refresh the data, but by our own calculations even 5 years of refreshes at 1/week would only be 26% of the drive’s rated 1000 cycle lifetime.

And it seems that TLC NAND isn’t the only type of NAND that’s having a problem at process nodes of 19nm or less. The Crucial MX200 SSD which uses 16nm MLC 128Gb NAND flash chips appears to be having the same very issue that the Samsung 840 EVO had, namely NAND flash voltage drifting which causes read speed performance issues on older data.

What does this mean? Well, it means that pretty much NAND flash memory becomes unreliable as the process node shrinks past 20nm. NAND flash manufacturers have hit the wall when it comes to planar NAND. From this point on the only way to make NAND flash reliable is to reverse the process node shrinkage and go to 3D-NAND where NAND cells are stacked on one another instead of laid out flat.

Samsung started this trend in which they released their 3D-VNAND and reversed the process shrinkage to 40nm with their 850 line of SSDs. Other manufacturers are also doing the same with their own approach to 3D-NAND. Ultimately it comes down to the fact that NAND flash memory manufacturers have hit the wall in terms of shrinking NAND and that as you shrink the process node the NAND has far more of a chance of voltage drifting that can effect read speed performance as the data ages.

Avoid Samsung SSDs at all costs! (Part 2)

Alright, some more information to go on.

As you can see in the above image, you can see how TLC NAND Flash works. TLC which stands for Triple Level Cell and is named that because it stores three bits or three binary states per cell. 000, 001, 101, 011, 100, 101, 110, and 111

Each binary state requires a different voltage state to represent the binary state in the NAND flash cell, specifically eight different states. This is much different from traditional MLC NAND in which it only has to hold four different binary states.

What is being theorized is that there is voltage drift inside the NAND flash cell. To show what’s going on, we have another image.

Notice how you have two voltage states, the 010 and 011 states. They are closer together because the voltage state drifted. When we read the cell and we get a cell voltage back we have an issue. Does that cell contain a 010 or 011?

So now, we have to read the flash cell multiple times to come to a general consensus on what that cell is storing. If a majority of reads come back with a voltage state that represents 011 then it must be 011.

Therein lies the problem. Because of voltage drift in the NAND Flash Cell a Flash Cell must be read multiple times because we need to figure out what that cell is storing because of voltage drift.

Because both the 840 and 840 EVO use much smaller NAND Flash Cells, 21nm and 19nm respectively. Because the flash cell is so small there’s not a lot of room to store a lot of electrons thus any change in voltage state caused by an electron or two escaping the flash cell can cause the voltage drift to be very detrimental to reading the binary state back from the NAND flash cell.

Samsung has gone back to 40nm with their new 3D NAND technology which should in theory solve the issues with voltage drift but like the 840 EVO, the 850 EVO is also TLC or Triple Level Cell and thus open once again to voltage drift inside the cell effecting read speeds because of the many various forms of voltage states needed to represent eight voltage states for eight binary states.

With that being said, Samsung should be forced to do a massive world wide recall of the 840 and 840 EVO because the voltage drifts can become a bigger issue with reading data back as the NAND flash cells become older and more writes have been done to the flash cell. More voltage drifts means more time needed to read data and quite possibly lead to mass data corruption due to the inability to read data back from older flash cells.

But, Samsung won’t do this. This is why I call for a boycott on Samsung SSDs until they do right for the owners of the 840 and 840 EVO. They are playing with people’s data integrity here.

Avoid Samsung SSDs at all costs!

This includes the new 850 series!

To those that may not know about the issue that has been plaguing many users who have both the 840 and 840 EVO SSD products, the 840 series (non-Pro) has a serious hardware design flaw in which data that is older than 60 to 90 days reads far, far slower than data that is newer. Some people have seen read speeds as low as 50 MB/s, yes you read right… 50 Megabytes per Second! That’s slower than slow notebook hard drives!

The reason is that the Samsung 840 and 840 EVO uses TLC NAND Flash Memory, specifically 19nm NAND Flash. There is much speculation but the most logical reason why the data read speeds become lower as the data ages is because of severe electron leakage between the NAND flash cells which results in a much larger voltage drift inside the NAND flash cell.

Lets rewinds back a couple of months ago to when Samsung acknowledged the issue in the first place. They promised a firmware fix for the SSD along with a performance restoration tool. All the performance restoration tool did was rewrite the data to get the data’s read speed performance back. The firmware fix promised that this issue would never come back because they supposedly tweaked the voltage calculation algorithms and that data read speeds would be consistent from there on out. Fast forward to today and we know that that promise was something not to be believed.

So here we are, owners of the Samsung 840 and 840 EVO drives sit with SSDs that will forever experience these data read speed slow downs along with a very good possibility that data may become corrupted in the SSDs due to voltage drift in the NAND cell. Samsung said that something would be coming out in March and again, here we are in April and nothing but silence from Samsung.

Samsung lied to us when they told users of the 840 EVO that the firmware fix will solve the issue. And then when the problem came back, they lied to us again when they said that they would deliver another supposed fix. Samsung has no intention of fixing this issue. They can’t fix this issue. This is a hardware design flaw and one that would need a worldwide recall of the 840 EVO and by extension the 840 but Samsung won’t do that.

So at this point I call upon all users to avoid Samsung SSDs at all costs! Hell, I’d go so far as to avoid all Samsung products. If it has Samsung’s name on it, avoid it like the plague! This includes SSDs, hard drives, computers, televisions, tablets, smartphones, etc. Anything made by them, do not buy! Boycott this lying and cheating company!

The Samsung 840 EVO… An SSD with an obvious hardware design flaw.

The Samsung 840 EVO SSD has a very well known issue that results in reduced performance while reading older stored data. The issue manifests itself as reduced read speeds when you start to read data that is older than three months (90 days). This has been talked about in length on Overclock.net’s SSD forum as well as several reputable technology enthusiast news sites. Normally the SSD can read data from the drive at speeds around 500 MB/s but when reading older data read speeds can be as low as 50 to 100 MB/s which is drastically lower than that of the advertised speed of the SSD. This can effect the speed of loading programs as well as Windows itself.

Samsung admitted that there is indeed a problem and released a firmware patch back in October of 2014 that promised to fix the issue with the SSD. Now, several months later and we are back to where we started; reduced read performance. Samsung stated that they have plans to release some kind of software solution to improve performance of the SSD but that it would need to be done every couple of months. This is nothing but a band-aid, it is not a solution. It’s only purpose is to mask the issue and make it less noticeable to the users of the device.

The general consensus of users of the Samsung 840 EVO the world over is that this issue is a hardware design flaw and one that Samsung is simply trying to cover up.

I call on Samsung to refund or recall every single 840 EVO that has been sold.

Setting The Record Straight

My last couple of posts have made several people call me a fanboi. And you know what, I may have very well sounded like one. That’s right, I may have very well sounded like an Apple fanboi.

Putting The Blame Where The Blame Needs To Be Put

My last couple of mobile devices have been Android devices. First a Motorola Droid Charge, then a Galaxy Nexus, followed up by a Galaxy S4 and then finally a Galaxy Note 3. What really turned me off of Android recently is how Samsung treated the last two devices I had, namely the S4 and the Note 3. Both of those devices had not seen updates in many months. Meanwhile, Google kept churning out new versions of Android. Though, I can’t blame Samsung completely, some of the blame can be put on my cell carrier; AT&T. They don’t want to invest the time and money into approving and releasing new Android OS updates when they can just turn around and sell you a new device. Putting together, approving, and distributing software updates isn’t cheap; it takes a lot of time and effort to make sure that the update goes relatively smoothly and even then, the updates don’t always go as clean as one would want them to go. So when something does go wrong more often than not the customer blames the carrier and demands a new device which of course costs the carriers money. So really I put the blame for the mess that Android is in squarely on the shoulders of the OEMs and carriers, they’re the reason why Android is so fragmented.

Some people brought it to my attention that Google can seamlessly upgrade certain parts of the Android operating system regardless of which carrier sold you the device or what Android OEM made the device. Those updates are pushed out via updates to the Google Play Services Platform. So now people can have parts, perhaps the most critical parts of the Android system, seamlessly updated without having to do anything. This is good for the Android user. The fact that Google has to sneak these updates in behind the backs of carriers and OEMs shows how Google has lost control over Android.

I understand that Android is an open platform; one in which anyone can do anything they please to the platform. This can be anything from installing it on whatever device they choose to modifying it as they see fit. This is how Google licensed Android. This is what I have a problem with, the license that Android is licensed under. There’s far too much room for those who take Android to abuse it. We can see this in how Google has no say-so in how and when Android devices get core OS software updates. And by that I mean the base operating system (4.4 KitKat, 5.0 Lollipop, etc.) Instead, they have to sneak in updates through some kind of back door. If Google had written into the Android license a legal clause stating that when Google comes out with a new version of an Android OS release all devices running Android must get that update in a specified amount of time, we would not be in the mess we are in.

I also understand that people say that if you want a more pure version of Android you should get a Google Play Edition device or one of the other Moto devices. If you ask me, this is a sign that Google has realized their mistake in licensing Android the way they did. They have come to the conclusion that if they want control over the destiny of Android they must produce their own hardware. This is what Apple has done from the very beginning with their iOS platform.

Why Android Core OS Updates Are Important

I also understand that there is the idea that if devices get Google Play Services updates they won’t necessarily need core OS updates. I beg to differ. New versions of Android bring new features, bug fixes, and fundamental changes to how Android works at much lower levels than just updates to Google Play Services can bring to the device. For instance, the most notable change between 4.4 KitKat and 5.0 Lollipop is the forced introduction of ART or Android Run-Time.

The idea behind ART is that when an app is installed the app’s APK file (similar to an EXE file on Windows) is fully compiled to machine code upon installation of the app. Remember, an Android APK file is nothing but a compressed file that contains Java bytecode that needs to be compiled the rest of the way on the device to be run. This is very different from how things were done on versions of Android prior to 5.0. Under versions prior to 5.0, Android used the Dalvik VM in which upon running an app the app was compiled to machine code, this of course added time to the execution or opening of the app. Every time you launched an app the app’s APK file needed to be read, compiled, and executed whereas under 5.0 and ART, the app’s binary or APK file is already compiled at the time of installation saving a lot of CPU time and battery life every time you launch an app. This should also open the door for better optimization of the machine code because you have more time to compile it than during the half second before opening it under Android 4.4 and earlier. This of course should benefit devices that may not have the latest and greatest hardware in it because it reduces the CPU time needed to run apps. So you can see that having Android 5.0 Lollipop even on older devices can help increase the lifespan of the device in question.

Speaking about the Galaxy S4 and Galaxy Note 3. Both devices have quad-core CPUs and at the very least 2 GBs of RAM. The hardware is no slouch. This is modern hardware by anyone’s standard. If anything, 5.0 Lollipop would benefit these two devices a great deal and may even bring new life to the devices and allow people to keep the devices longer. The S4 is only two years old and the Note 3 is only a year old. Not old hardware if you ask me. So why isn’t Samsung and AT&T upgrading these devices to 5.0 Lollipop? It comes back to what I talked about in the second paragraph of this post, they don’t want to. They would much rather sell you a new device instead of putting the effort into updating the device. I call for the idea that if they no longer want to support the device with newer versions of Android they should be forced to unlock the bootloaders like in the case of the AT&T and Verizon Galaxy S4 and Note 3 and subsequent Samsung devices sold by the carriers. That way if the user wants to take the time into upgrading the device themselves by installing one of the any number of third-party Android ROMs they should be able to do so without issue and not have to worry about a locked down bootloader.

The Apple Hardware Way

In the case of the Apple iPhone devices, Apple maintains control over their hardware. They don’t just control the hardware but also the software as well. This has allowed Apple to marry the software and hardware together in ways no Android device maker can ever hope to do. Some might say that that’s the reason why Apple devices run so well, the software is hyper-optimized for the hardware on which it’s running. The current version of iOS, version 8.x, is still supported on devices dating back to the iPhone 4s which at this time is nearly four years old. There’s rumors that iOS 9 will be still be supported on the iPhone 4s which at the time of iOS 9 the device will be nearly five years old. That’s an amazing track record when it comes to supporting older hardware. This is similar to how you can install Windows 7 on six year old hardware and still have it run decently.

Changing To The iPhone

I’ve had my iPhone 6 Plus for a little over a month now. So far I’ve loved every moment of it. The operating system is smooth, it runs well, and I can’t make it lag. Even with several apps open and multitasking the iPhone 6 Plus doesn’t skip a beat. The battery life is amazing on the device. Even when under heavy load the iPhone’s battery life outshines that of my previous Android devices by a wide country mile. Even the apps seem more polished on the iPhone than on Android. My iPhone experience has been nothing short of amazing, far better than Android in so many different ways.

In a lot of ways, I just want my phone to work. When I need to make a phone call, I need it to work. When I need to send a text message, I need it to work. When I need to get directions because I’m lost, I need it to work. I don’t want to worry about whether or not I have the battery life to be able to do what I need to do. Though Android also did work in those cases there were many times when I’d find my battery close to being dead and I didn’t even touch the device. There were many times when I had my Note 3 in my pocket and had not touched it for three hours and the battery life was already down 15% or more. And yes, I was connected to WiFi so there shouldn’t have been any need to use LTE to send or receive data. So the obvious question is… What drained my battery so badly?

I hate to say this but in a lot of ways, Apple was right when it comes to multitasking on mobile devices. Apps should not be able to run in the background indefinitely chewing up battery life, the OS should have the ability to tell an app to go to sleep. Android doesn’t have this ability, apps can (and do) run indefinitely in the background and more often than not can drain your battery dry. I’m looking at you Facebook, you’re the worst offender of them all! Mobile devices by their very nature are power limited devices, they need to have strong power management capabilities built into the core operating system. This is what Apple iOS has, it can tell an app that it’s time is up and it needs to go to sleep.

Apple vs. Android

People call Apple iOS the most restrictive operating system in which Android claims that they are the most open platform. Sure, Android does allow for a lot of customization but because of that customization it can result in a very fragmented system in which not everything fits together nicely. iOS may very well be a restrictive platform but everything just works. Asking Siri to do something results in it just working. I can tell Siri to set timers, alarms, calendar events, and reminders all without even unlocking my phone. I can even ask Siri for sports scores or even a weather report. I wasn’t able to do any of that on Android, or at least it wasn’t nearly as easy to do as it is on iOS with Siri.

As for the restrictions, I’ve not run into one situation in which Apple iOS 8 has prevented me from doing something I’ve wanted to do on my device. Now this may be different because I’m running iOS 8 and past versions of iOS were far more restrictive than iOS 8 is. Version 8 has really opened the iOS platform up and removed a lot of the roadblocks that were in the system. Like I said before, I’ve not run into any restrictions that prevented me from doing what I wanted to do. Even the most important app that I use, Lastpass, the app that stores my saved passwords integrates right into Safari on my iPhone and allows me to fill login forms with relative ease. This would not have been possible without the platform improvements in iOS 8 which lifted a lot of the restrictions on what apps can and can’t do on the platform. With iOS 8 Apple has managed to walk the fine line of user restrictions to maintain system integrity while still allowing the user to do what they need to do.