bogdan_r
What is the battery life?
EarthIsHome
If you like quartz watches that expose their circuitry, you'll definitely enjoy some of Accutron's watches: https://www.hodinkee.com/articles/introducing-accutron-314
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
Topfi
Accutrons and tuning fork watches are amazing. They have an incredibly unique sound/hum due to the tuning fork oscillating at 360 hz and the most smooth glide you'll ever see in a watch. Recommend a ESA 9162 or ESA 9164 over a pure Accutron for beginners though, a bit more resilient and far more affordable, though they don't have the exposed dial.
7373737373
I learned the term for such mechanical watches is https://en.wikipedia.org/wiki/Skeleton_watch
simonjgreen
Swatch make some delightful and affordable skeleton watches
alpenbazi
Interesting concept. Bigger screen less casing would be nice, but very good concept
comrade1234
Yeah the watch command is pretty sweet. sudo watch sensors
davydm
Very cool. Keep on keepin on.
chuckmoritzgg
[dead]
Y_Y
On that point, I see an awful lot of code that uses dotslash as if it was necessary for files in the current directory.
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.)
PhilippGille
One issue is when the path is not interpreted by the shell but by a program which plays by different rules.
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!
Bleibeidl
I'm pretty sure most people use it to make clear it's a relative path. It takes mental load off the one reading the code. That's why I pretty much always use it, not only when executing things.
aidos
./<tab> completes nicely. Ambiguity is removed. There’s no chance of accidentally running the wrong executable.
So I think you and I differ on this one, but none of this is a hill I care to die on.
amonith
I use it for autocomplete... e.g ./f<tab> and enter. If I don't do it the terminal literally hangs for a split second and gives me a lot useless suggestions. I rarely type full words.
teddyh
Similarly, many people needlessly append a slash to every directory name.
mjw1007
It makes tab completion work.
jagged-chisel
At the start of a line? So you want to run a script or executable in the current directory. PATH doesn’t contain . and ./ is necessary.
As an argument in a line? My shell offers completion from the current directory without ./ just fine.
lynx97
For executables, it is actually necessary to prepend ./ iff . is not in $PATH. And . is usually not in $PATH for security reasons.
Display HS096T01H13 almost fits inside F91-W (1mm too wide) but have much smaller bezel.