New
#30
ghost82
sassafrasAnd this keeps giving me the feeling about us, users, beig converted in eternal beta testers. All is ending on patches, build updates, cumulative whatevers and what not's.If one wants a stable version of Windows 10 then the Insider program is not for you.
right ,
I wouldn't leave a test build as my only OS or without user data /file folder/media file back ups or a system image , either way test builds can go south at any time ( so can any Windows OS and other OS in general ) and over the last year or so we've had some Insider builds with serious issues while the previous build was mostly fine you never know how the next flight is going to be ( or what the next update may break on any OS ) .:)
IOW if you aren't prepared just stay with a normally activated Windows 10 or something else and leave the test driving to us ! ☻☻
Sent from Windows 10 Pro Insider Preview Evaluation Copy . Build 14257 rs1-1601131-1800
Last edited by blutos cousin; 07 Feb 2016 at 16:00.
Copyright laws are different in different countries. In the US, you cannot copy an entire article wholesale without permission, regardless of whether you credit it or not. The US has something called Fair Use, which allows you to legally use an except, but not the whole thing.
I understand that other countries have different laws, but you cannot give such advice to people in a forum where everyone is from a different country.
When a program is destined to use on payroll, accounting, inventory or billing you can't implement a sloppy bunch of work with errors in it. A good testing plan to uncover errors should be followed with no shortcuts. If the business has changed I would be shocked that some companies I know about would put up with it, especially when they're sending out millions of bills every month or banking information.
[QUOTE=BunnyJ;560759]Core things are painstakingly tested and bug free. But lots still have bugs.
Just out of curiosity.. what is your programming/IT experience??[/QUO
32.5 years in large data centers. My experience includes front end processors, implementing VTAM in a large nation wide company network (Subarea, CDRM and CDRSC are a few terms that should convince you), data center security using IBM's medium size computer, automating mainframes with scripts that automated IPLs and Shutdowns along with NJE node monitoring and automatic replies to operator commands like changing forms in a Xerox printer (don't need form changes in a Xerox mainframe printers), installing mainframes and their associated system OS, maintained Xerox large laser printers and their internal forms that had to be coded (some were networked from world headquarters in Morristown, NJ to a factory datacenters, implemented hardware and software to add server's to mainframes, consolidate data centers from other parts of the country into very large one, installed fiber ring to the POP (lot of water in those underground pipes under the streets), installed and maintained Cisco routers, wired a huge building with twisted pair wire and patch panels after moving away from IBM's coax, learned Cobol and assembler, worked with programmers on extended testing of changes before cutover, Represent data center in change control meetings, Knew how to program DDM1000 and multiplexers(muxes) that can breakout DS3s to T1 levels, created a T1 patch panel that another company patented and I am tired of typing this stuff but there is more computer related I did that I was very good at in my lifetime that enabled me to keep a job in that field for over 32 years like networking 350 servers in the same building with 8 IBM JES complexes or implementing bulk data transfer networks. I traveled a lot, sometimes shipping a scope ahead of me) and was stuck in Newark, NJ due to cancelled flights so I paid my dues. I know you were doubting me with your question. I am not an insider on this web site but I like most of the comments and learn from people.