Microsoft is reportedly trying to distance itself from Windows 8.
Microsoft's April 2015 "Threshold" Release May Be Windows 9 : Read more
Microsoft's April 2015 "Threshold" Release May Be Windows 9 : Read more
... wrong article?What I would really like to see with Windows 8.2 is an update to explorer.exe so that it will finally have full support for file paths longer than 255 characters in length. This is a very annoying limitation that occurs frequently in deeply nested folders on my computer. I have to use Totalcommander to do the operation I ought to do with Explorer. NTFS itself has support for file paths longer than 10,000 characters I believe.Also, start using "MiB" and "GiB' instead of "MB" and "GB" where applicable. When you are stating a capacity in the base 2 system, use "MiB" or "GiB" and when stating a capacity in the base 10 system, use "MB" or "GB" please! It confuses a lot of users into thinking that their hard drive isn't as big as it should be.Also make the task manager more code efficient, take longer to load than the Windows 7 task manager.
I love how the media works. First off, it's nothing to do with Windows 8. Stop spinning it like "Microsoft has realized they've made a colossal mistake". They aren't "fixing" anything by "rushing" anything to market. Natural....Product......Life cycle. Vista: 2006Win 7: 2009Win 8: 2012Win 9: 2015!!![\quote] That is the same principal as Intel follows with their Tic Toc release model.Only MSFT calls it Flop flip.
Whilst I agree with you on file path length; I suffer the same at times, I couldn't disagree more with using KiB etc.1KB has ALWAYS historically meant 1024 bytes. The only reason anything changed is because Microsoft decided it would represent 1000 bytes in '95, since they probably thought it would be easier for people to understand - because we're all too thick to use numbers that are not rounded for us.Following that, the mighty SI decided to make a new standard which someone thought would be a good idea to make it sound like a 2 year old child created it (kibi/mebi/etc). Slowly linux started adopting it, thankfully it can be changed there, but i'm guessing it wouldn't be so easy to modify Windows.But here we come to the real problem - it's not this stupid adoptation of XiB - it's the fact that microsoft still insist on using base10/decimal in windows when computers don't work like that. So long story short, you can keep your XiB which i'm sure all the kids are jumping on since it's new and trendy - leave it out for those of us who have been using computers for a bit longer though.What I would really like to see with Windows 8.2 is an update to explorer.exe so that it will finally have full support for file paths longer than 255 characters in length. This is a very annoying limitation that occurs frequently in deeply nested folders on my computer. I have to use Totalcommander to do the operation I ought to do with Explorer. NTFS itself has support for file paths longer than 10,000 characters I believe.Also, start using "MiB" and "GiB' instead of "MB" and "GB" where applicable. When you are stating a capacity in the base 2 system, use "MiB" or "GiB" and when stating a capacity in the base 10 system, use "MB" or "GB" please! It confuses a lot of users into thinking that their hard drive isn't as big as it should be.Also make the task manager more code efficient, take longer to load than the Windows 7 task manager.