4 ms·
>If you use a safe programming language which doesn't piss over memory (I.e. Haskell, Python, Ruby, Lisp etc) you won't need to reboot. This is a man who's nev
by heretohelp 14y ago
>If you use a safe programming language which doesn't piss over memory (I.e. Haskell, Python, Ruby, Lisp etc) you won't need to reboot.
This is a man who's never used Xmonad (which is written in Haskell) for an extended period of time before. If you use it for a long enough time, it gets slower and slower until workspace changes start taking whole seconds.
Eventually you say fuck it and reboot...
...'cept you can't do that without a filesystem with a "base state" to reboot from.
GG
- gouranga 14y agoAs someone who's had an sbcl process running for just over a year on one box, I disagree. xmonad is probably just a turd.
- AlisdairO 14y agoSo what, in the future you're relying on everyone to magically start coding well?
- snprbob86 14y agoDon't we already expect that from kernel contributors? :-P
- heretohelp 14y agoSo we're going to expect this from the entirety of userspace?
- gouranga 14y agoNo userspace can be wrapped quite nicely: In fact we don't really need processes, just suitable environments set up for execution of code. For example, stop a lisp definition calling eval: (defun no-eval-wrapper (form) (let ((eval nil)) (form))) I've not tried this btw and it'll probably only work with scheme dialects.
- deleted 14y ago[deleted]
- yoklov 14y agoI've had this happen before with xmonad. It turned out I had a memory leak in my configuration file :(