While usually not on display, the quartz movements of Grand Seikos are beautifully finished:
* https://i.imgur.com/sJXfmg1.jpeg
* https://i.imgur.com/BucSW15.jpeg
You only need to prepend dotslash to a filename in order of disambiguate invocations of executables in the the current directory (and not a subdirectory).
This is because bare commands will be looked up in $PATH, rather than among executable files in $PWD.
It strikes me as weird copycat (without understanding) programming to just have it wherever you're referring to a local file. In fact I prefer to invoke `bash foo.sh` rather than `mv foo.sh foo; chmod +x foo.sh; ./foo.sh`. (This assumes that I don't need to rely on something special in the shebang line.) This also lets you use tab-completion as normal, as well as adding flags for bash like -x.
(I know you could use it for clarity when an argument could look like a string or a file, but I don't think that's usuaully the purpose.)
As an argument in a line? My shell offers completion from the current directory without ./ just fine.
So I think you and I differ on this one, but none of this is a hill I care to die on.
For example in Go:
$ cd /path/to/go/repo
$ go run cmd/myapp
package cmd/myapp is not in std (/usr/local/go/src/cmd/myapp)
$ go run ./cmd/myapp
Hello, World!
And then people don't want to think about when your path is for the shell and when it's a CLI param and how the CLI treats it, and just use the version that always works.Similarly, package installers can use this to disambiguate between "install the local file with this exact name" and "look up a file on the index for the named package".
IMO the take away from command-line interfaces is compact, precise and minimal design. In a transitional shell prompt like #~$, each character has its meaning. Merely copying these symbols to a watch face is the exact opposite spirit of command like interfaces.
My favorite prompt is >: as a callback to the Swan computer in the TV show Lost (not sure if it's also used in early Apple computers).
e.g. https://hackaday.io/project/194683-plasma-toroid-sky-guided-...
Naturally it does mean you can't have a ground pour, so the PCB needs to be designed to look nice with it.
Really? It looks like it would be uncomfortable to wear with those screws on the back sitting proud of the surface. Why aren't they countersunk?
Or were you referring only to the electronics?
Very cool
I do want to dig into how much a battery can be obviated here, there's one watch called the Pulse-o-matic that uses an automatic movement (that is, self-winding) to power an LCD display and associate 'tronics. I am charmed by the idea of wind up electronics now that we have microchips with deep sleep modes and ePaper displays that only need a blip to update.
https://theprintablewatch.com/collections/digital-watch-part...
https://www.hamiltonwatch.com/en-us/h52585339-pulsomatic.htm...
seems useful on it. can you run
watch -n '.\t'
on it? /jk as that would make it a dedicated watch watch
davydm•7h ago