3 ms·

Some years ago someone that worked at Microsoft told me he didn't think any individual engineer who already works on Windows could ever get Windows building by

• varispeed 4y ago
  That just shows their bias. If the code is complete, it's only a matter of time to figure out how to build it. May not take hours, but determined engineer should be able to figure it out.
  • jedberg 4y ago
    I think you're being naive. Microsoft has spent 1000s of engineering years on their build system. You aren't going to just replicate that in a week.
    • great_psy 4y ago
      You’re also not trying to get a full CICD pipeline complete with unit/integration tests, crypto signatures, ability to flip features on and off with a click , monitoring of the cicd pipeline, scaled so 1000s of engineers can work at once etc
    • VHRanger 4y ago
      As a user said below, you wouldn't need cross platform support, incremental builds, tests to run, etc. Just getting the code to compile, link, baking in assets, etc. For a single architecture is a much more reasonable goal. I'd imagine it'd be on the scale of 1-3months for an engineer to get working full time, but large error bars around this figure
      • rvnx 4y ago
        Plus it already has been done before with Windows XP, without even any documentation and there is a guide on the internet on how to build Windows Server 2003. This was done (if I remember right) when governments and big customers had access to the Windows source-code.
    • int_19h 4y ago
      Microsoft uses Azure DevOps for products as large as Visual Studio.