Definitely helped me to understand how clocks work. And it’s fun to watch it.
Mechanical Watch
61–70 of 425 posts
Re: Mechanical Watch
#62There's something magical about mechanical watches. Maybe it's just knowing that you have this perpetually winding machine on your hand (in the case of "automatic" mechanical watches). Also knowing that the thing will last forever, take care of it and it will probably outlive you. Can't say that about an Apple Watch. If you want a good mechanical watch that won't break the bank I suggest picking up a Seiko SKX (thoug…
Re: Mechanical Watch
#63I was curious how he did those visualizations so I looked at the source code. Turns out he codes everything by hand in WebGL [1]. Absolutely impressive stuff. Source code is non-minified so you can have a look and understand everything as well. [1]: https://ciechanow.ski/js/watch.js
He does it "the right way™". Use the platform. Don't use any framework or generic library. Go straight to the point and code what you need, when you need it. Don't minify or bundle anything, and let the people who are learning and courious a straightforward way to connect the dots, without forcing them into a github repository with 90% of the code unrelated to the thing and existing just to glue 1000 pieces written b…
Re: Mechanical Watch
#64I started with Greg Daniel's masterpiece: Watchmaking. https://www.amazon.com/Watchmaking-George-Daniels/dp/0856677...
I was about to post the same book. Pretty much a must have if you get into watchmaking.
Re: Mechanical Watch
#65This may not be the most valuable comment, but my goodness, the quality of this writeup and it's interactive descriptions of complex mechanical components AND their interactions is radically impressive. The treatment of complex topics in deeply visual and partially interactive ways, for me at least, is a remarkably helpful way to learn.
Re: Mechanical Watch
#66This may not be the most valuable comment, but my goodness, the quality of this writeup and it's interactive descriptions of complex mechanical components AND their interactions is radically impressive. The treatment of complex topics in deeply visual and partially interactive ways, for me at least, is a remarkably helpful way to learn.
1000%. Sent this to my dad, and can't wait to talk this weekend. When I was a kid we would tinker around with watches in the basement but, alas, I had different interests and never really got around to truly understanding these mechanisms. I don't really know web development beyond setting up basic pages, but how the CAD was integrated into this is wonderful and I'd love to see more posts going through things like hu…
Re: Mechanical Watch
#67This may not be the most valuable comment, but my goodness, the quality of this writeup and it's interactive descriptions of complex mechanical components AND their interactions is radically impressive. The treatment of complex topics in deeply visual and partially interactive ways, for me at least, is a remarkably helpful way to learn.
Does anyone know the tooling used to create these?
[1] https://twitter.com/BCiechanowski/status/1484013009219375105...
Re: Mechanical Watch
#68This may not be the most valuable comment, but my goodness, the quality of this writeup and it's interactive descriptions of complex mechanical components AND their interactions is radically impressive. The treatment of complex topics in deeply visual and partially interactive ways, for me at least, is a remarkably helpful way to learn.
Re: Mechanical Watch
#69Earlier quoted context omitted.
He does it "the right way™". Use the platform. Don't use any framework or generic library. Go straight to the point and code what you need, when you need it. Don't minify or bundle anything, and let the people who are learning and courious a straightforward way to connect the dots, without forcing them into a github repository with 90% of the code unrelated to the thing and existing just to glue 1000 pieces written b…
I mostly agree with you, but I don’t mind minification when appropriate, as it can serve a functional purpose with tangible end-user-friendly benefits (less downloaded over the network = faster response times). But if you want to be friendly to the tinkerers, you could always host both the *.js and *.min.js versions, and have the webpage just pull the latter - anyone who wants the unminified source can remove the “mi…
In practice this seems to be a lost cause, and links to alternatively hosted source code is more common. Sadly this makes is simple to introduce subtle, harmful differences between the source and what is hosted.
Re: Mechanical Watch
#70Earlier quoted context omitted.
He does it "the right way™". Use the platform. Don't use any framework or generic library. Go straight to the point and code what you need, when you need it. Don't minify or bundle anything, and let the people who are learning and courious a straightforward way to connect the dots, without forcing them into a github repository with 90% of the code unrelated to the thing and existing just to glue 1000 pieces written b…
I mostly agree with you, but I don’t mind minification when appropriate, as it can serve a functional purpose with tangible end-user-friendly benefits (less downloaded over the network = faster response times). But if you want to be friendly to the tinkerers, you could always host both the *.js and *.min.js versions, and have the webpage just pull the latter - anyone who wants the unminified source can remove the “mi…
Seems better just to have premassaged source available in a repo somewhere, or called out on the page itself for a downloaded archive.