5 ms·
What goes around, comes around. Stealing code is on Microsoft records, as a simple "Microsoft admits stealing code" search shows. One can only wonder how much c
by dejaime 7y ago
What goes around, comes around. Stealing code is on Microsoft records, as a simple "Microsoft admits stealing code" search shows. One can only wonder how much code the company stole that did not come to public knowledge.
https://www.computerworld.com/article/2522017/microsoft-admits-plurk-code-was-stolen.html https://www.computerworld.com/article/2522017/microsoft-admi...
- RachelF 7y agoAlso many of the .wav files in Windows 98SE were edited with a pirated version of Sony's Soundforge, the metadata in the media files contained the Soundforge cracker's name.
- citrusui 7y agoAs far as I could research, I only found articles about Windows XP. Close enough. https://www.tomshardware.co.uk/pirated-software-used-to-create-help-content-in-microsofts-windows-xp,news-14167.html https://www.tomshardware.co.uk/pirated-software-used-to-crea...
- whereistimbo 7y agoThese .wav files might be made by person who works under Microsoft contract, not necessarily directly employed by Microsoft.
- wildfire 7y agoWhich, of course, makes it perfectly acceptable?
- gattilorenz 7y agoNo, but if Microsoft asked for wav files, and a contractor delivered them, is Microsoft at fault if the contractor used a pirated editing software?
- jacobush 7y agoLiable? I hope so. And then they can pass the buck on.
- gattilorenz 7y agoWhy would Microsoft be liable? Do you check if your butcher has illegally bought his knife? Should you be liable, if so?
- jacobush 7y agoHmm... you may be right. But on the other hand, is the steak licensed and copyrighted?
- gattilorenz 7y agoIt's not, but metaphors and analogies only go so far :)
- darkpuma 7y agoThat sort of shit is relevant only to lawyers. A salaried sound designer could have lied to Microsoft just as easily. The nature of the offense isn't actually being changed in any practical sense between the two scenarios.