Original Microsoft OpenSource Windows parts

Here you can discuss ReactOS related topics.

Moderator: Moderator Team

Post Reply
theuserbl
Posts: 136
Joined: Wed Mar 23, 2005 3:49 pm

Original Microsoft OpenSource Windows parts

Post by theuserbl »

At first
๐Ÿ€๐Ÿท๐Ÿ–๐Ÿฅณ๐ŸŽŠ๐Ÿพ๐Ÿฅ‚ ๐“—๐“ช๐“น๐“น๐”‚ ๐“๐“ฎ๐”€ ๐“จ๐“ฎ๐“ช๐“ป 2020 ๐Ÿ€๐Ÿท๐Ÿ–๐Ÿฅณ๐ŸŽŠ๐Ÿพ๐Ÿฅ‚

I think, it would be interesting, to have a central place, to publish all OpenSource Windows parts, which are comming from Microsoft or which Microsoft using in Windows or plan to use in Windows.
The difference to Samba, WINE, ReactOS, MinGW, etc is, that this are parts, which don't plan to be compatible to Windows, they are (parts of) Windows - or will be in the future.


Kernel
Windows Driver Framework. As OSR said, a part of the Win10 kernel.
https://www.osr.com/blog/2015/03/18/win ... ow-github/
https://github.com/Microsoft/Windows-Driver-Frameworks


Libraries
C++ standard library for Visual C++. And in Visual C++ Windows is written
https://github.com/microsoft/STL


.net
.net including compiler, runtime, WinForms, WPF, etc
https://github.com/dotnet/runtime
https://github.com/dotnet/roslyn
https://github.com/dotnet/winforms
https://github.com/dotnet/wpf

And WinForm including the control icons
[ external image ], [ external image ], [ external image ], [ external image ], [ external image ], [ external image ], [ external image ], [ external image ], [ external image ], [ external image ], [ external image ], [ external image ], [ external image ], [ external image ], etc

PowerShell, which replaces Microsofts cmd.exe
https://github.com/PowerShell/PowerShell


Fonts
The OpenSource Fonts of Microsft
https://github.com/microsoft/fonts
https://github.com/Microsoft/Selawik
https://github.com/Microsoft/Cascadia-Code


Browser
The new Edge is based on the Chromium-engine. And on that engine will be existing a lot of Windows applications, like UWP
https://github.com/chromium/chromium


Applications
Programs, which comes with Windows
https://github.com/microsoft/calculator
https://github.com/microsoft/terminal


Do you know more Original OpenSource Windows-parts?

Greetings
theuserbl

Thanatophobia
Posts: 38
Joined: Tue Oct 16, 2018 1:28 pm

Re: Original Microsoft OpenSource Windows parts

Post by Thanatophobia »

The Windows 3.x file manager is open-sourced, too: https://github.com/Microsoft/winfile

Interesting list.

theuserbl
Posts: 136
Joined: Wed Mar 23, 2005 3:49 pm

Re: Original Microsoft OpenSource Windows parts

Post by theuserbl »

@Thanatophobia: Yes you are right. The Win 3.x filemanager of the past is OpenSource, too.

And it seems, that there existing two OpenSource programs, which will be part of the future of Windows. But currently it isn't.

1) MSIX
https://docs.microsoft.com/windows/msix/overview
And on GitHub msix-packaging, MSIX-Toolkit, MSIX-PackageSupportFramework, MSIX-Labs and AppConsult-MSIXDevWorkshop

The MSIX will replace the *.msi package formats.
The plan is, to install easily programs and using it. And if you later deinstall it, there will be no rest of it in the registry or on other parts of the computer. But in contrast to the UWP-Apps you can additinal download plugins for the Apps and it will be part of the Apps. If you deinstall them, the PlugIns will be deinstalled, too. Also it will be possible to save configuration settings for the Apps, etc.
And for all, you don't need the Microsoft web store.

2) CLang
There existing some clues, that Microsoft plans to replace Visual C++ (the compiler with which is Windows compiled) with LLVM/CLang.
The clues are And if Microsoft know, that Windows could be a little bit faster and smaller, by simply changing the compiler, who belives, that they would stay on its Visual C++? They already replaces its Trident/EdgeHTML-engine with the chrome-engine. Its only a question of time, when Microsoft replace its Visual C++ with LLVM/CLang.

Greetings
theuserbl

Thanatophobia
Posts: 38
Joined: Tue Oct 16, 2018 1:28 pm

Re: Original Microsoft OpenSource Windows parts

Post by Thanatophobia »

b@theuserbl That all seems pretty interesting. I've heard they plan to port Edge to Linux in a Reddit post, but it's not officially confirmed that would be the case and so it remains proprietary. But the possibility of using MSIX can get UWP compatibility more easily.

Alot of other things Microsoft has made has become open sourced. MS-DOS versions 1.25 and 2.0 have been made open sourced as well under an MIT license: https://github.com/microsoft/ms-dos

PurpleGurl
Posts: 1788
Joined: Fri Aug 07, 2009 5:11 am
Location: USA

Re: Original Microsoft OpenSource Windows parts

Post by PurpleGurl »

I believe this could use a wiki page.

theuserbl
Posts: 136
Joined: Wed Mar 23, 2005 3:49 pm

Re: Original Microsoft OpenSource Windows parts

Post by theuserbl »

CScript.exe
Just realized, that ChakraCore was not only the JavaScript Engine of the old Edge browser (that one without Chromium), it is also the newest version of cscript.exe, but it is there called ch.exe and have not so much options.
You can find the binaries at the Release-side. And Microsoft continuous updating it.
Here examples for it.
The simplest "Hello World"-program:

Code: Select all

WScript.Echo("Hello World!");

User avatar
irony
Posts: 25
Joined: Tue Dec 04, 2018 4:17 pm

Re: Original Microsoft OpenSource Windows parts

Post by irony »

theuserbl wrote: And if Microsoft know, that Windows could be a little bit faster and smaller, by simply changing the compiler, who belives, that they would stay on its Visual C++?
I am wondering, have you actually read the post in the link you showed as a "proof" that clang is better? where actually clang is compared with the modified clang, regarding precompiled headers and impoving C++ compiling time, which is not .....
theuserbl wrote: A lot of people showing benchmarks, that CLang compiles faster, more performant code then Visual C++.
compiling time != more performant code, you ..... you seem to not read even the title or literally have no clue on the topic. or both. the article is on Clang improvement of its precompiled headers (C++ modules) usage and how it improved (or not) clang's C++ compiling time:
it turns out, the problems I mentioned last time had already been more or less solved in Clang. But only for C++ modules, not for precompiled headers. *sigh* I had really mixed feelings when I finally realized that.
the article, where the authour clearly makes a note, that GCC and MSVC are used as a "reference" and not as a "fair comparison":
Note that GCC(v9) and MSVC(v2017) are there more as a reference than a fair comparison. MSVC runs on a different OS and the build may be possibly slightly handicaped by some things taking longer in Cygwin/Windows. GCC comes from its openSUSE package, which AFAICT is built without LTO (unlike the Clang package, where it makes a noticeable difference).
Also, do you really think, the compiler efficiency can be estimated by analyzing the code genereted for snippets like this:

Code: Select all

auto get_hi(std::uint16_t value) -> std::uint8_t {
    std::uint8_t result;
    std::memcpy(&result, reinterpret_cast<char*>(&value) + 1, sizeof(result));
    return result;
}
theuserbl wrote: which lets look the generated code of Visual C++ a lot of more ugly.
expert of the 100500 level, everybody. idiots are the curse for this forum.

MOD Edit: And you are one of them!

User avatar
EmuandCo
Developer
Posts: 4432
Joined: Sun Nov 28, 2004 7:52 pm
Location: Germany, Bavaria, Steinfeld
Contact:

Re: Original Microsoft OpenSource Windows parts

Post by EmuandCo »

You have 6 hours to change the post and remove all curses and name callings. Otherwise I do that for you! We had that discussion more than once by now and I told you next time I make you be quiet. Last time you had friends hoping you would join and help the project. Not sure if that's still the case... ^^

EDIT

More than 6 hours passed. 4 swearings removed, one sidenote added. I am in good mood today. One week per edit = 4 weeks of temp ban.

No toxic behavior is tolerated in here anymore.
ReactOS is still in alpha stage, meaning it is not feature-complete and is recommended only for evaluation and testing purposes.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 1 guest