|
Post by Admin_Vistamike on Jul 26, 2014 13:19:24 GMT
Computerworld - 'As talk of the next Windows begins to build and some details of what most are calling for now either Windows 9 or Threshold come into focus, it's worthwhile to take a moment to remember Windows 8. Because Microsoft will want everyone to forget it. And we will.' Wankers>>>>> LOL!
|
|
|
Post by GuiltySpark on Jul 26, 2014 13:28:25 GMT
Computerworld - 'As talk of the next Windows begins to build and some details of what most are calling for now either Windows 9 or Threshold come into focus, it's worthwhile to take a moment to remember Windows 8. Because Microsoft will want everyone to forget it. And we will.' Wankers>>>>> LOL! LOL is correct The trouble is Win 9 and Win 8/8.x is basically the same process that MS went through with Vista and Win 7 so you can expect Win 9 to last about 5 yrs after its official release before MS claims no more service packs.
|
|
|
Post by warlock on Jul 26, 2014 13:34:05 GMT
No problem here.
|
|
|
Post by irvsp on Jul 27, 2014 0:15:02 GMT
Computerworld - 'As talk of the next Windows begins to build and some details of what most are calling for now either Windows 9 or Threshold come into focus, it's worthwhile to take a moment to remember Windows 8. Because Microsoft will want everyone to forget it. And we will.' Wankers>>>>> LOL! I thought W8 used common code base for PC's, Touch PC's, Tablets, and Phones? Well, not all it seems? See www.engadget.com/2012/06/20/windows-phone-8-and-windows-8-share-lots-of-code-nt-kernel/ for instance. Moving to unified code isn't that big a deal if the above it true. This is a support statement, one set of source code to worry about. If MS wants YOU to move to W8, you can bet it will cost too, and more than moving to W8 probably. Wonder if there will be h/w on your end required to be changed or replaced? Every release from MS seems to 'lose' some printers and video cards. Not really MS's fault, but he h/w vendor's support issue is more like it if the h/w requires changes.
|
|