I would perhaps call this “build.ts” instead. Calling it “make.ts” implies Makefile-like behavior, e.g. multiple targets, dependencies, conditional builds, etc.
I know they’re just being through but the “go test” part is a bit “Pray, Mr Babbage”… Test code is just code. I know of no language where tests are sandboxed in any meaningful way.
Right, I should have said there are conventions and libraries you can use to limit the scope of tests but that requires intention and diligence. But fundamentally , “go tests” could run anything a normal go program can.
This certainly looks impressive but it’s a bit misleading to say it works on “almost any phone” when it doesn’t work on iPhone (which only allows mobile Safari)
Neat! Unfortunately the search/informational dialog blocks almost half the screen on mobile (iOS Safari). It also gets really slow when you zoom way out (e.g. when navigating to another state)
It is a bit better. The overlay is much smaller, but it would be still nice to be able to dismiss or minimize it so it’s not blocking 1/4 of the screen all the time.
It’s still get a bit clunky when you zoom out far but it’s better than before.
reply