Would you leak it's source code?

Fair point. But leaking source code of newer Windows' versions, would help Wine greatly.

Why the fuck would anyone want to read through a massive clusterfuck of shitty code?

They wouldn't be able to use the leaked code anyway, or they'd get sued.

s/leak/delete/g

Try wiki.osdev.org/Tutorials

my lifestyle is worth securing, i'm looking to upgrade

no, that would probably create huge legal problems and cause more damage to the project than help

With all the cia work on win10 theyed kill you for your silence

But they don't need to use it. If devs just see how it works internally...

It wouldn't matter if I did. The Windows codebase is chock full of only used by Windows libraries and tools. It would take an outsider decades to learn and use the Windows codebase without internal resources. More importantly even if by some magic you managed to, it would still be near impossible to build. The entire codebase relies on our proprietary tools and build system. It relies hard on these things or else no build.

It wouldn't help as much as you think. It'd be useful, but see above for how long it would take to be make operational.

Microsoft fired its internal Windows testing team and now they're essentially crowd sourcing it via insider program and telemetry.

I'm surprised Microsoft hasn't open sourced more code to outsource coding itself.

Didn't reactOS get fucked over with internal auditions regarding the use of win2k code to avoid bein sued

Can you at least reveal here how many LOC Windows 10 (or 7/8/8.1) has?

Depends on what you mean. Windows (like most OSs) has a shit load of components. The core OS itself is by no means brief.

Core OS.

there isn't much mystery to how this stuff works internally, there are many reverse engineering tools to figure that out, it just is time consuming work, that if you ask me is not very rewarding because all you're doing is duplicating msft's work solely because they intentionally are shitheads about licensing and get off on forcing people to do stuff like that

leaking the source code would not really reduce this work by much, people would still need to completely rewrite everything to avoid infringing, and any time they saved by having a reference, they would then lose again by having to take extra steps to make it appear as if they had never read the leaked code

every man has his price, yours just happens to be low

>every man has his price, yours just happens to be low
Woah

>every man has his price, yours just happens to be low
you know what
i dont care if you hurt your elbow
there
i said it

Without question.
Then I'll have fun having M$ sperg about having their privacy "violated" because apparently "nothing to hide" suddenly doesn't apply to them anymore.

I would start contributing to the reactOS project.

>W10 source code gets leaked
>people start working on a complete refurbished open source Windows based OS
>a thousand fixed bugs and a lot of removed useless crap later, it works just like W7, but can look like W10 if you want it to
>they call it Ventanas OS
>Microsoft copies everything to their new version of Windows
>people still pay for it

stop being autistic
nobody cares about your fanfic

make it easier for linux community to reverse engineer important applications

God, you people sure love sperging out "zomg autist!!!111" at every opportunity, don't you?
What a miserable, pathetic existence.

Attached: 1501418388983.png (1920x1080, 1.75M)

>Patch bug
>Company that relies on bug now crashes and bridge they design crumples.
This is a true thing that can happen, ponder this for a moment, there are engineering companies that use Excel for their calculations and rely on well known inaccuracies.

>i dont care if you hurt your elbow

Attached: 1498424780186.png (352x106, 5K)

Em... No. I'd better change proprietary EULA to GNU GPL (or LGPL) license, and share source code.

GNU+Linux

>it's

I have a very hard time believing any one person at Microsoft has access to the entire source code precisely for this reason.

You can access all the source code, it's not gated, but good luck understanding it.

>proving me right
oh no

No, but I'd scrape as much of the core components and kernel of every version since XP as I could fit on my 64GB keychain flash drive and then send it to the React OS devs so they can rewrite it from scratch as open source software.

Attached: 50a.jpg (600x760, 55K)

Shit. I didn't even notice it.

Isn't that leaking?

Technically yes, but not really. A leak often implies that it's given to a large number of people or to the general public. This would be between me and the React OS devs. The source would never be given to the general public, never be compiled, and never redistributed in anything else. Just studied and reimplemented by neckbeards.

This is actually illegal under US law, as I understand it.

This is theft of a trade secret and is very illegal. Leaking it to everyone is less illegal because "everyone has it, so it's not a trade secret anymore" is apparently an argument that stands up in court.

It's not a lack of insider knowledge that keeps them from doing so now...

No it isn't. You're allowed to reverse engineer and rewrite software. If it's 100% your work that's inspired by a proprietary product, then that company can't do shit. Microsoft isn't going after React OS because they damn well know that not a single line of their code is in there, and the UI is just a generic grey boxy 90s UI that has been ripped off a million times over. React OS actually ran into legal trouble when they did use real Windows source code from the old NT leak, and they halted the project to audit everything. That's why development has only recently picked back up.

I'd argue that it's different with Microsoft since they're nearly a monopoly and they're harming US citizens by spying on them. Only good would come from their source code being leaked and forked.

Hell no I would use it for my own benefit

>You're allowed to reverse engineer and rewrite software
In the US? Unless the laws have changed since 2008 or so, you aren't. You can have one person reverse engineer and someone else write a reimplementation (this is called "clean-room reverse engineering"), but the same person doing both ("dirty-room") is illegal.
The great ReactOS clusterfuck of 2006 was because someone dirty-room reverse engineered part of XP. As far as I know they never actually copy-pasted any leaked source code.

So.. what's about?

I would delete it.

Attached: 1523924955644.png (554x400, 66K)

So why doesn't it get leaked? Are pajeets that trustworthy?

copyright issues, moron

Probably just a handful of people have access to the whole source code (if even anyone does without going through the different departments and requesting it). The way windows is built is by progressively integrating binaries to the files structure, not by compiling the whole source code in one go.

yes
then I would modify it and remove all bloat and spyware then basically torrent it as an illegal version which will eventually be full of trojans and it will be very hard to find a clean versio

No, because check outs are gated and scoped. A full pull of some components require manager approval in real time.

>tell microsoft that you have source code
>ask them to pay you to stay silent
>fbi kicks your door in literally an hour later
>get arrested and charged with extortion and 50 other things
>lose to microsoft's trillion dollar lawyers
>go to prison

Excellent idea.

yes, so it can finally die to vulnerabilities and shame

Even if I would, no one would touch it. You don't fuck around with a multi billion dollar company like that.
For indication, the W2000 source code is readily available, but even ReactOS devs, arguably the people that need that the most deny looking at it because you don't want a lawsuit with a company as big as MS.
Also, you'd need some time and space to store the 300+ GB codebase. Just sayin.

Attached: 1494939297544.jpg (1280x720, 149K)

>300+ GB codebase
>implying terabyte hard drives are expensive now

I'd like to think we're close to the day Microsoft finally stop relying on security through obscurity and become open source. Imagine a fully supported 2018 proofed flavour of Windows XP? Bliss

t. Brainlet

Pretty sure my ass did after my last visit to Taco Bell.

Wrong and wrong it's not leaked because 1) we are paid well, 2) even if it was, what good would it served. Ask yourself if you are employed and working, what good is leaking information from the hand that feeds you. That's why when layoffs come the codebase is locked down and people are taken offsite and escorted off by security.

> leak it is source code
> it is

fuck, are you useless

>FBI working with microsoft
>implying they wont just offer you a better deal for all those easy backdoors that even microsoft won't know about
TOP KEK

then explain why both the old win2k and windows 10 leak were only partial copies

they're one of the biggest gov agencies, they already have access to the source code you stupid retarded fuck

Probably because they were a vendor who had an incomplete copy, or they just didn't have the whole thing. Cloning the whole OS also used to be a much bigger PITA. As it is currently I've got the "whole" Windows repository on my machine. Hardly worth talking about. Again even if you got it, to quote a Win2k engineer on the leak, yeah good luck building it.

That's entirely their fault though

so do you actually build the whole OS yourself? or when developers get the code, it comes with some parts already pre-compiled?

What why? What if you get owned or robbed?

imagine actually believing this
you've been spending far too much time on Jow Forums

very

Your post hints that you don't know what governs your every day actions, so you don't know what you are talking about, at all.

Attached: 1509496331477.png (657x527, 126K)

huh? every big player (governments and other big corporations) get the source code. do you think russia or the US military would run binaries without having a fucking clue what's in them?
>Through the Shared Source Initiative Microsoft licenses product source code to qualified customers, enterprises, governments, and partners for debugging and reference purposes.
>Government Security Program
>All governmental requests (whether from local, state, provincial, or national governments or agencies) for access to Microsoft product source code must be directed to the Government Security Program Team. They can be contacted at [email protected].

they also made a non botnet version and gave its source to chinese government

I thought it was sort of funny because that's how I think they would react too, actually.

You AMD tards are all mentally ill, stop projecting.

eurogamer.net/articles/2011-02-21-the-boy-who-stole-half-life-2-article

deserved for being a myg0t shitter

Do you think the source code is one long ass Notepad file?
Most people working on it stick to their own component

I've been trying to convince a couple of Jews I know who work for MS to do exactly that, but they're Jews so all they ever wanna talk about is how they can't afford expensive houses in Seattle on their MS salaries and how moving out to suburbs isn't worth paying half the housing cost because "that's where all the racists live."

>Do you think the source code is one long ass Notepad file?
not , but maybe

Then they would have a long ass time uploading it.

Most big projects don't actually build each module. It'd be a tremendous waste of CPU and time. Yes you can build the whole Windows OS last I heard was it took a standard dev box about a 24-30 hours. Most folks just build small components and use an existing binary cache we have that gets built every night.

amazing dude

Attached: 1480265542930.jpg (719x662, 37K)

to make a decent user friendly os

sans botnet as well

How locked down is it? Do you think anyone has taken it home on a flash drive just to store for themselves?

Yes, you should. Then maybe somebody can undue all the shitty design decisions made by the criminals at microsoft.