3 ms·

> learn Powershell and Windows concepts instead. And how does one exactly do that? Because I once tried to learn what a "home group" was and to my surprise it

by lottin 9y ago

> learn Powershell and Windows concepts instead. And how does one exactly do that? Because I once tried to learn what a "home group" was and to my surprise it wasn't defined in precise terms anywhere. Not to mention lower-level stuff such as the init system.

com2kid 9y ago
> Not to mention lower-level stuff such as the init system. The init system on Windows is robust enough that 99.999% of users never have to consider it. There is a UI to control what runs at startup, and that suffices for most things. Windows has services of course, and there is a dependency graph built up of how they initialize, and for a huge % of people developing services, this also doesn't matter. Set what dependencies you have, if your service can be loaded on demand or if it has to be always on, and have at it. More complicated services do require work, at which point documentation can be dug into. > Because I once tried to learn what a "home group" was Bing actually provides a great answer box on this. (search term: windows home group) tl;dr a group of PCs on a LAN that share out file folders (video, music, etc) and printers. Each computer can choose what to share. A PW is requested upon joining a home group. The first non-ad result on Google also explains it pretty well. :) A protocol spec is also available: https://msdn.microsoft.com/en-us/library/ff362232.aspx https://msdn.microsoft.com/en-us/library/ff362232.aspx (found by searching home group msdn)
will4274 9y ago
Here's the first Google result for "Windows homegroup" https://support.microsoft.com/en-us/help/17145/windows-homegroup-from-start-to-finish https://support.microsoft.com/en-us/help/17145/windows-homeg... . Microsoft is famous for its meticulous documentation compared to other closed sourced systems and is often even better than open source systems where developers will not document and instead tell you to just read the code.

by lottin 9y ago

com2kid 9y ago

> Not to mention lower-level stuff such as the init system. The init system on Windows is robust enough that 99.999% of users never have to consider it. There is a UI to control what runs at startup, and that suffices for most things. Windows has services of course, and there is a dependency graph built up of how they initialize, and for a huge % of people developing services, this also doesn't matter. Set what dependencies you have, if your service can be loaded on demand or if it has to be always on, and have at it. More complicated services do require work, at which point documentation can be dug into. > Because I once tried to learn what a "home group" was Bing actually provides a great answer box on this. (search term: windows home group) tl;dr a group of PCs on a LAN that share out file folders (video, music, etc) and printers. Each computer can choose what to share. A PW is requested upon joining a home group. The first non-ad result on Google also explains it pretty well. :) A protocol spec is also available: https://msdn.microsoft.com/en-us/library/ff362232.aspx https://msdn.microsoft.com/en-us/library/ff362232.aspx (found by searching home group msdn)

will4274 9y ago

Here's the first Google result for "Windows homegroup" https://support.microsoft.com/en-us/help/17145/windows-homegroup-from-start-to-finish https://support.microsoft.com/en-us/help/17145/windows-homeg... . Microsoft is famous for its meticulous documentation compared to other closed sourced systems and is often even better than open source systems where developers will not document and instead tell you to just read the code.