Live data from Hacker News

Mechanical Watch

ciechanow.ski

61–70 of 425 posts

Re: Mechanical Watch

#62

There'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…

I have an automatic mechanical watch - a Seiko 5. It loses about 5 minutes a day. It might only need an adjustment to calibrate it, but that would require a watchmaker. I think the last one in town just went out of business, and even if he hadn't, the cost of his labor would be greater than the cost of the watch.

Re: Mechanical Watch

#63

I 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…

We need a ciechanow.ski explainer for how ciechanow.sky explainers are built

Re: Mechanical Watch

#64
post #28

I 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.

My late Uncle Vic taught me how to repair clocks and pocket watches when I was young. I let it go, and returned to re-learning it with this book. I still dream of completing my first, from scratch, pocket watch.

Re: Mechanical Watch

#65
post #4

This 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.

Came here to write the same - that was amazing...

Re: Mechanical Watch

#66
post #4

This 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…

He has one on the ICE actually, though I don't have the link handy.

Re: Mechanical Watch

#67
post #4

This 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?

According to his Twitter, he just uses bare canvas and WebGL. [1] What a legend. You can inspect the page and read the source js, it is unminified.

[1] https://twitter.com/BCiechanowski/status/1484013009219375105...

Re: Mechanical Watch

#68
post #4

This 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.

I think that the person(s) that created the interactive visuals would find this to be a helpful comment. Radically impressive is a fitting description. I don’t think I’ve ever seen and interacted with anything like it, although I imagine people working with CAD software get to see and mess around with this kind of stuff pretty frequently.

Re: Mechanical Watch

#69

Earlier 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…

That's simply not a very well followed (and thus discoverable) standard. Especially for hand crafted code, minifying functions and variable names only obfuscates what is written and minifying whitespace often only has minimal benifits.

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

#70

Earlier 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…

It's hard to guess that extra assets exist on the server if they aren't being pulled down by the site itself.

Seems better just to have premassaged source available in a repo somewhere, or called out on the page itself for a downloaded archive.

Post reply on HN