Kevin Burke
Kevin Burke
In this mode we would ignore the in-memory assets and read assets from disk.
The benchmark says a single run generates 16,000 allocations. That's going to be really slow. Can we do anything to reduce the number of allocations?
We should ensure that the `assetfs` project is compatible with the output from this project.
If we send a signal while safefile is in the middle of writing a file to disk, we end up with `*.tmp` files in the directory which is not good.
https://github.com/kevinburke/go-html-boilerplate/issues/8
We use gzip compression but we should be able to verify at compile time that the string in our file is valid, and remove the error from the method signature.
Reading the docs and attempting simple implementations, I'm still not sure how to use these, since I keep getting panics. I'm going to search Github to see people using these...
to read the current state - bc read does not require elevated permissions, but write does.
I'm a contributor to the Go language and [a consultant](https://burke.services) who spends a lot of time on builds, devops, and deploys. Presumably I should be able to figure out how...
I'm trying to port `x/build/devapp` (which powers dev.golang.org) to App Engine Flex, since the normal App Engine context only supports the (now deprecated) Go 1.6, that project depends on code...