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.
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
e.g. https://hackaday.io/project/194683-plasma-toroid-sky-guided-...
I’ve been wanting a larger watch than most companies make. I’d like a traditional digital watch. Since I can’t find what I want, I’ve been thinking about building my own. I want to go to about 60mm for the case (across my wrist).
I purchased a Casio G-Shock GA-010 last week but its size is smaller than I anticipated. It’s 52mm.
I’ve also been drafting a document about how I’m using a digital watch to increase my productivity while limiting distractions.
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...
Edit: huh, someone has apparently done it! https://www.reddit.com/r/termux/comments/nl0rex/termux_on_we...
seems useful on it. can you run
watch -n '.\t'
on it? /jk as that would make it a dedicated watch watch
Very cool
What I particularly liked was that these clocks did not actually tell you the time unless you hooked them up to your notebook's RS232 port and telneted in. We don't even have serial ports now, particularly on laptops, but I had to telnet into them to update them when the clocks changed to/from GMT/BST.
Up the road from these expensive clocks was a college that had a horology course. People on it would spend their three years making these absurd timepieces that were all about the mechanism and it was almost a point of pride for the students to have just an hour hand rather than something actually useful.
I feel that this watch concept needs a few more iterations to make it stylishly useless. For example, if the strap was like one of those ribbon cables we used to use to connect disk drives to the motherboard in early PCs, with an adaptor so the ribbon cable is either a watch strap, plugged into the watch, or a connector to a break out box that connects to a PC via USB, with this being the sole means of adjusting the watch or setting what mode it is in.
Regarding the screen and the terminal styling, this doesn't quite work for me as 'time' is what I type into the terminal to time something and 'date' is what I type in to get the date. I therefore see the terminal styling as a bit over the top. What I would like to see is an OG font from the 8 bit days, with blinking cursor, in old school LCD, think of the one character high screens that the last of the typewriters had.
Regarding changing the mode, some dip switches could come in handy. I think that there is fun to be had and that everyone would want to critique whatever gets made, as, ultimately, a CASIO is far better for the task in hand, plus you can also get calculator watches by them that get 90% of the aesthetic for a bargain price. But that is not the point though, much like the horology students, it is all about creating a timepiece and the challenges that involves, notably keeping the time accurate.
A for effort, and A for posting your work for armchair experts like me to critique!
imho a watch is useless if you cant just look at it and see the time.
> I had never done any PCB design before and downloaded KiCAD with no idea how it worked.
I saw similar lines among many people who designed great things, take a note, companies, just because an engineer doesn’t have 10y of experience in XYZ doesn’t mean they won’t do great in the job.
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.)