timmay3141
Programmer
I'm asking mostly out of curiosity. Does anyone know?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
What language was Windows written in?
- Thread starter timmay3141
- Start date
- Status
Actually, I think that this is one of those situation where the onus is on you to demonstrate that bits of Windows are written in VB, not for me to demonstrate that they are not.
However, just for starters consider the following: firstly, at no point has any version of VB ever compiled to a standalone application. It requires a number of runtime libraries, that themselves require Windows and the Windows API. The existence of the VB5 and VB6 runtime libraries. Secondly, up until version 6, VB has ben obstinately single-threaded - not exactly useful in putting together a multitaking OS. Thirdly, current useful versions of Windows are 32-bit, but developement of the 32-bit Windows platform predates the existence of any 32-bit version of VB. Fourthly, the (current) iterations of the Windows OS expose themselves as a set of API calls (yes, there are COM wrapper above some of these, but these tend to be additional services layered on top of the actual OS); VB cannot create anything apart from COM libraries, so it would be difficult for parts of the OS to be written in it.
It is true that there are some tools written or partially written in VB, but they are not part of the OS. Delete them and Windows will not grind to a halt.
However, just for starters consider the following: firstly, at no point has any version of VB ever compiled to a standalone application. It requires a number of runtime libraries, that themselves require Windows and the Windows API. The existence of the VB5 and VB6 runtime libraries. Secondly, up until version 6, VB has ben obstinately single-threaded - not exactly useful in putting together a multitaking OS. Thirdly, current useful versions of Windows are 32-bit, but developement of the 32-bit Windows platform predates the existence of any 32-bit version of VB. Fourthly, the (current) iterations of the Windows OS expose themselves as a set of API calls (yes, there are COM wrapper above some of these, but these tend to be additional services layered on top of the actual OS); VB cannot create anything apart from COM libraries, so it would be difficult for parts of the OS to be written in it.
It is true that there are some tools written or partially written in VB, but they are not part of the OS. Delete them and Windows will not grind to a halt.
- Status
Similar threads
- Locked
- Question