A self-winding watch needs to be worn for hours each day to not run out of power. A manual-wind watch will be a better choice for a night-only mechanical watch.

You can get a watch winder to keep your automatic wound even if you don't wear it all the time.

I took off my self winding watch at night and it worked fine.

> night-only mechanical watch

I said that I was thinking of only wearing a smartwatch at night, because I really like the gentle alarm in the morning.

What I didn't say was that I use a smartwatch for tracking my sleep patterns.

The 90S5 is basically the very popular 9015 but with a big hole in it. :)

The Miyota 90S5 would work, it is cheap and “open heart”.

RMS?

That used to be the case, but a lot has happened in the last few years. Most of the time you'll be able to move a large Rails application to JRuby without any changes at all, except adding a Warbler config for deployment.

We use JRuby for a one of our backend applications in production, but we develop them with plain MRI Ruby. Only real problem we've run in to was some of our badly performing (badly written) parsing code that ran even worse under JRuby.

Python's Pickle lib had something similar to safe_load(), that they removed because it gave a false sense of security.

If you are accepting pickled objects from a remote and using it ... you are an idiot.

I found the browser a lot better/faster on my 3GS after the update, probably due to Javascript speed improvements, so it's very far from "unusable".

I haven't heard of anyone's Air screen breaking, they can't be that fragile.

(But I have heard of several people destroying them with coffee or beer).

Well I think that if you pour coffee or beer you would destroy any device, Apple or not.

I wonder how these 1980's results relate to object oriented code and other things that have happened since then. Even 25 LOC would be a huge method in Smalltalk-style OO for example.

Other than OO, we also have much better tools for navigating code now. That may have changed how we approach and understand unknown code.

A few of my old colleagues bought the code from our bankrupt employer and made a second attempt at creating a business with it. They did better than the original owners, but not much.

In all other cases I've come into contact with the code just dies. Open sourcing would be nice, but that's obviously not a priority in a bankrupcy.