you've just seen the windows source code post your expression

File: 1486499065911.gif (1022KB, 200x142px) Image search: [Google]

1022KB, 200x142px

>>58893211

File: 1486094679672.jpg (18KB, 628x600px) Image search: [Google]

18KB, 628x600px

>>58893211

File: 1486504723177.jpg (32KB, 960x300px) Image search: [Google]

32KB, 960x300px

>>58893211

File: 14793613254df02.jpg (139KB, 1920x1080px) Image search: [Google]

139KB, 1920x1080px

>>58893211
yes

File: 1442277093472.jpg (48KB, 400x400px) Image search: [Google]

48KB, 400x400px

>>58893211

File: fueled by despair.png (704KB, 1280x720px) Image search: [Google]

704KB, 1280x720px

>>58893211
mainly cause i got no clue whats going on.

File: 1462033991057.jpg (70KB, 1024x577px) Image search: [Google]

70KB, 1024x577px

>>58893211

File: 1475632897570.png (40KB, 734x580px) Image search: [Google]

40KB, 734x580px

>>58893211

I'm a filthy tech illiterate who is just here for the consumer technology.

What's so special about the Windows source code? Why can't you just take an application/OS/whatever and un-compile it to get the source code? If one input has one output when code is being compiled, should you be able to go in the reverse direction and use the output to get the input?

File: 1480641680147.jpg (586KB, 1024x1008px) Image search: [Google]

586KB, 1024x1008px

>>58893211

>>58893357
Code obfuscation

File: Kotori-chan.jpg (515KB, 2017x1935px) Image search: [Google]

515KB, 2017x1935px

>>58893211
Nice!
>>58893357
That's called reverse engineering, it's a thing.

But you cannot just copy them exactly, since you would get lawsuits that can leave you broke and die from hunger, like a hobo (rms).

File: 1480381425751.webm (2MB, 776x650px) Image search: [Google]

2MB, 776x650px

>>58893357
windows source code is PROPRIETARY. that means it is a SECRET and NOT PUBLICLY AVAILABLE for you to STUDY or MODIFY.

>>58893357
It's like making a cake, you can't bring back the eggs, milk, etc. Every time you want cake you need the recipe (source code). Although you can get the instruction code (assembly) by a process.

File: 1480391886274.gif (942KB, 253x216px) Image search: [Google]

942KB, 253x216px

>>58893211

>>58893439
I guess what I'm asking is why is it like baking a cake instead of like say making water (you can put hydrogen and oxygen together to get water, or break up water to get hydrogen and oxygen).

>>58893413
Are we being raided again? I miss the old /g/, all you new fags are ruining it.

File: tunak2.png (99KB, 265x318px) Image search: [Google]

99KB, 265x318px

>>58893211
>reaction image dump: the thread
>>58893357
please just leave

File: images.jpg (5KB, 348x145px) Image search: [Google]

5KB, 348x145px

>>58893476

windows

source code

is PROPRIETARY.

that means it is a SECRET

and NOT PUBLICLY AVAILABLE

for you to STUDY or MODIFY.

File: chillin with qt birb gf.jpg (65KB, 480x640px) Image search: [Google]

65KB, 480x640px

>>58893487
Then just make a timemachine.

>>58893497
No shit it's illegal, so is piracy but most people do that. I'm wondering about the technical aspect of it.n

>>58893476
It's more like taking in a bunch of numbers as input and multiplying them to get an output.

You can work backwards from the output to get an input, but it's not going to be the same input as before.

Also, compilation strips out a bunch of useful things (like variable names) that exist to make the source code readable by humans.

File: 1476668724846.gif (434KB, 196x181px) Image search: [Google]

434KB, 196x181px

>>58893211

File: hankhill.png (179KB, 640x480px) Image search: [Google]

179KB, 640x480px

I bet it looks like crazy spaghetti code. I can't believe Windows still uses the clusterfuck of a mechanic known as the registry

>>58893410
but microsoft provides symbol files and debug (checked) builds freely

>>58893535
piracy is such a minor thingand barely any care is given about it

meanwhile Microsoft will hunt you down and bankrupt you forever if you break their copyrights

>>58893536
Thanks.

>>58893357
>can't you uncompile it?
Not exactly. How you would even know which programming language it was originally coded just from the machine code? Hello world in C and in Python would compile to the same thing (not quite, but assume they do for the sake of simplicity). The point being, once you have machine code, you can't in general uncompile it back to source code.

Actually, you can try, and it's quite possible to "uncompile" simple programs if you grant yourself some liberties. But for a massive codebase such as that of Windows', especially given the fact that most of it is said to be complete undecipherable spaghetti, it's unfeasible and not worth it to even try.

File: 055eebe8e7971f755fea7510df1e9757884390c843922a31ed56c5ea216b8c02.jpg (113KB, 750x679px) Image search: [Google]

113KB, 750x679px

>>58893211

https://thepiratebay.org/torrent/3497574/Windows_2000_source_code
I'm getting a gateway error when searching for Windows NT4 but there's some source from that online too

>>58893882
Yeah but the code has changed so much I'm sure that that code isn't very similar to modern Windows anymore
All though I'm sure there's some obscure kernel bug that still hasn't been discovered yet

>>58893933
>the source code has changed in the last 15-20 years
Really?

File: 018[2].gif (2MB, 580x433px) Image search: [Google]

2MB, 580x433px

>>58893211
I actually have seen the windows source code because some of it was leaked in the 2000s.

It was spaghetti city with lots of very cynical comments.

File: 1439775439858.jpg (15KB, 291x275px) Image search: [Google]

15KB, 291x275px

https://github.com/TC1995/NT_4.0_SourceCode/blob/master/nt4/private/ntos/boot/lib/i386/ixpcibus.c

>lines of code

>>58893557
what would you suggest in place of the registry files?

File: 1351515845758.jpg (67KB, 799x627px) Image search: [Google]

67KB, 799x627px

>>58893211

File: 1485970295510.jpg (107KB, 837x697px) Image search: [Google]

107KB, 837x697px

>>58894016
>lines of code
what do you mean?

>>58894201
config files located with it's programs it effects with a folder dedicated to global settings

>>58894540
yeah. the registry itself is ridiculous, with some of the keys being super fucking long and nested.

Then when you uninstall a program and it doesn't remove everything, and keys are scattered all over the place in the registry. there's no sequencing to them, it's just a clusterfuck

>>58893211
Last time code leaked it was pretty decent

File: 1459301946459.png (1MB, 1300x4704px) Image search: [Google]

1MB, 1300x4704px

>>58894685
obligatory

>>58894808
Seems legit I'm sure she had no axes to grind or anything.

>>58893413
I love that episode of Halt and Catch Fire where the dudes are in the garage reverse enginering the IBM BIOS. Shit is dope.

File: 1473550114866.jpg (112KB, 772x817px) Image search: [Google]

112KB, 772x817px

>>58893211

>babies need a translation
read the 0s and 1s faggots

>>58893357
you can, sort of, but there will be no structure, variable names, comments, or anything
it doesn't help much in understanding what the code does

>>58895689
for you. we know exactly what it does.
name one thing it can't be done.
we can even sniff packets.

>>58895779
Actually port DirectX 10/11/12 to Windows XP, checkmate.

File: 1471167972720.jpg (71KB, 500x728px) Image search: [Google]

71KB, 500x728px

>The system that builds windows is a bunch of 30 year old perl scripts from the 1990s. No one knows what they do. They have tried to replace this build system 4 times. The most recent attempt happened while I was working there and was called "Apex". It worked great, solved all the problems, and was totally fantastic, except that it couldn't compile windows. No one could figure out how to get windows to compile on it. This is because no one knows how to compile windows. They eventually shelved Apex because no one could decipher what the flying fuck was going on with the perl scripts.
>They still use the perl scripts.

>>58898999
Perl mustard race!

>>58893439

it's called entropy you mongoloid

File: magician.jpg (3MB, 2448x3264px) Image search: [Google]

3MB, 2448x3264px

>>58893211
>mfw
>>58895779
>comparing decompiled software to packets
stop posting

puking_guy.jpg

>he hasn't looked at the leaked NT4/2k sources yet

>>58893969
>>58893933

No, NT hasn't changed much

File: mpv_[Asenshi] Little Witch Academia - 05[6506D1AB]_00_06_53_01.jpg (97KB, 1280x720px) Image search: [Google]

97KB, 1280x720px

>>58893211

File: 9781941082201.MAIN_.gif (77KB, 746x526px) Image search: [Google]

77KB, 746x526px

>>58893211

>>58893357
Reverse engineering is possible. But reverse engineering an entire fucking operating system to the point where every aspect becomes readable? That's the job of a lifetime. You can write your own OS in a fraction of the time needed to do something like that. Also Microsoft would sue your ass.

The Windows codebase has over 3.5 million files and is over 270 GB in size, because it's in one monolithic lump, including all imports.

git clone takes over 12 hours, checkout takes over 3, and status takes almost 10 minutes. They had to write an experimental remote filesystem driver (now on GitHub) to try to speed that up.

They (infamously) use Systems Hungarian notation variable names.

No one person knows exactly how NTFS works, which is why ReFS is such a clusterfuck.

It's basically true about the build scripts.

A lot of the code is a lot better than you probably think.

Microsoft is incredibly good at backwards compatibility compared to any other OS vendor out there. You wouldn't believe the workarounds, up to and including a whole subsystem for applying binary hotpatches to running code. Have a look at Raymond Chen's blog sometime.

>>58894016
PCI is an atrocious bus to initialize and program on.

File: images[1].png (4KB, 259x90px) Image search: [Google]

4KB, 259x90px

>>58893476
well yea, but pure hydrogen and oxygen are mostly useless for "practical" things humans do.

You can disassemble, i.e., tear apart a program but it's like trying to decipher a conversion by looking at a wave graph. You can get some things with special tools or by recognizing patterns but it's a slow process and ultimately not feasible for something as complex as an operating system.

File: 1484995914055.jpg (48KB, 400x460px) Image search: [Google]

48KB, 400x460px

Can't be worse than Linux source

>>58894638
yea it was part of larger decision of apparently tight coupling the platform. Window shit is never portable so matter what you implement in. Installers were a huge mistake.

>>58899773
>git
you do now about a thing called TFSVC?
developing office and windows is what it was written for. its preddy gud for huge source bases.

>>58899773
They still use hungarian notation? WHY

>>58899773
so basically they're maintaining a 25 year old code base 1000s of people have touched and have issues solving problems no one in the industry faces. Doesn't sound that bad really.

>>58899957
There is literally nothing wrong with Hungarian notation as a style. At the time most of the important parts of Window were being written it did help maintenance and stability because assembly and c are not strongly typed language.
They probably just keep doing it because consistency and readability is more important than "what's in this decade" naming conventions, pajeet.

File: 1485232929453.jpg (84KB, 469x292px) Image search: [Google]

84KB, 469x292px

>>58893211

>>58893438
You will be contacted shortly

that the Windows code base is in a bad shape is a meme
none of you fagtrons have actually seen it
why do you keep spreading information you can't evaluate?

What's the point of this thread?
If you want hideous source code, go for GNU

File: 1483974177006_0.jpg (216KB, 1276x1420px) Image search: [Google]

216KB, 1276x1420px

>>58893211

File: 1446759213583.png (745KB, 828x720px) Image search: [Google]

745KB, 828x720px

>>58893211

File: 1295194125615.jpg (36KB, 318x264px) Image search: [Google]

36KB, 318x264px

>>58893211

>>58899262
How do you know?

>>58899773
>Microsoft lets you git clone the entire source tree

Why hasn't the Windows source code been leaked yet? I'd assume you'd only be able to clone the parts that you're working on.

This is all assuming they permit you to work from home.

>>58903552
There has been windows kernel code leaks for a long time.