Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: NixOS/nixos-homepage
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 9b74127851cc
Choose a base ref
...
head repository: NixOS/nixos-homepage
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 4c35487081a6
Choose a head ref
  • 1 commit
  • 1 file changed
  • 1 contributor

Commits on Nov 10, 2020

  1. next benefit

    garbas committed Nov 10, 2020
    Copy the full SHA
    4c35487 View commit details
Showing with 17 additions and 4 deletions.
  1. +17 −4 overview.tt
21 changes: 17 additions & 4 deletions overview.tt
Original file line number Diff line number Diff line change
@@ -96,26 +96,39 @@
</div>
</div>

<!--
<div>
[% PROCESS svg path="site-styles/assets/gfx-overview-looking.svg" %]
<div>
<h2>
You can only fix, what you see is broken.
Either it works or fails always in the same way.
</h2>
<p>
With Nix there are two results: the code either works or fails always
in the same way. This gives you the power to reproduce (or avoid) any
in the same way. This gives you the power to reproduce (and avoid) any
build related bugs.
</p>
</ Nix gives you the power to adjust any part of the build environment in a transparent way. </p>
<ul>
<li>reproducibility</li>
<li>transparent source binary model</li>
<li>nix language</li>
</ul>
<div>
<p>
Build instructions are written in Nix language, which allows you to
extend or change existing build instruction in any way you wish. This
makes Nix a power build tool that can be used in both simple and
complex project.
</p>
<p>
Building and running tests locally or in your CI would always result
in the same failure or guarantee success. This is because environment
is always shared wherever your run it with Nix.
</p>
</div>
</div>
</div>

<!--
<div>
[% PROCESS svg path="site-styles/assets/gfx-overview-gears.svg" %]
<div>