Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Other security for Windows, Mac, Linux
NoVirusThanks OSArmor
Message
<blockquote data-quote="ForgottenSeer 58943" data-source="post: 699925"><p>There was some saying Win10 should have been the one that dropped backwards compatibility and enforce a new way of doing things. But alas, it won't happen largely because of the problems involved in implementing this for corporate environments. Can you imagine the cost of say migrating a firm with 1,500 PC's per location to an entirely new environment not backwards compatible? Ouch!</p><p></p><p>Some say Windows should have established two distinct paths. One for 'average Joe', more secured and completely NOT backwards compatibility. A unique development path for a secured OS, and a second one continuing down the path they are on with Windows 7/8/10. I probably would have made the switch to the new development path one personally and left the old stuff behind.</p></blockquote><p></p>
[QUOTE="ForgottenSeer 58943, post: 699925"] There was some saying Win10 should have been the one that dropped backwards compatibility and enforce a new way of doing things. But alas, it won't happen largely because of the problems involved in implementing this for corporate environments. Can you imagine the cost of say migrating a firm with 1,500 PC's per location to an entirely new environment not backwards compatible? Ouch! Some say Windows should have established two distinct paths. One for 'average Joe', more secured and completely NOT backwards compatibility. A unique development path for a secured OS, and a second one continuing down the path they are on with Windows 7/8/10. I probably would have made the switch to the new development path one personally and left the old stuff behind. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
