Hacker News new | past | comments | ask | show | jobs | submit login

Whew, leaving emacs open for three months? That's intense. I've had uptimes of up to a year, but I knew I was totally wrong to do so and it wasn't in a corporate environment as this sounds to be ;-)



One of Steve Yegge's old rants includes the suggestion that some of his favourite systems are those that have both extensible-while-running and doesn't-crash - one being emacs.

Uptimes of up to a year aren't totally wrong - having to shut down and close everything to manually work around some memory leaks and gradual flakiness or to guard against crashes isn't a great or desirable feature, even if it is extremely common.


I was implicitly referring to routine kernel updates (desirable on most OS - though not all), or other key software updates (especially on OS X or Windows) - rather than forced restarts for stability reasons.


> routine kernel updates

ksplice


Very interesting. Just submitted that to HN as a separate link. A very new technology though.

If you fancy leaving a comment with any insight you have: http://news.ycombinator.com/item?id=385225


BTW, for those interested in finding out how long your emacs has been running, I wrote an emacs uptime package a while back:

http://www.welton.it/freesoftware/files/uptime.el


It seems perfectly reasonable for me to have emacs open for a year. Why do you say it was wrong?


I guess it depends on your operating system, but there are few where it'd be good operational policy to not have key system updates at least a few times a year. They do exist, of course..


But, if you're using one of those systems, the best security practice is to not be on a network, and everyone follows best practices, right? :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: