Stop embedded the static UI content in a massive go file. about scope HOT 4 CLOSED

👎, I think there's a lot of advantages and simplicity to have the entire app available in a single statically-compiled binary without needing an assets directory "nearby". There's no real cost involved, just an extra step at the end of the Javascript build pipeline.

from scope.

Advantages such as?

As we're only going to be distributing scope as a container, serving it off the fs seems equivalent to embedding it (consider the container as the single binary...), without the need for the extra step.

from scope.

Like static typing, it moves a run-time requirement to build-time, and so eliminates a common, frustrating failure: I started the process but the UI isn't loading, because I don't have the assets {in the right place, specified correctly, completely present, ...}. The extra step is really nothing, one very fast bit at the end of a relatively long JS pipeline.

from scope.

Decided to leave this as is; whats more, we're going to leave static.go committed, even thought its automatically generated. This is because it takes too long to build. Circle will build it each time mind you.

from scope.