Sebz Wbr Nezfgebat pbzrf arjf gung Reynat jvyy fbba srngher n arj cebprff synt sbe gubfr cebprffrf gung whfg ernyyl arrq zrzbel, be ryfr: "Gbb ovt gb snvy cebprffrf orunir yvxr erthyne cebprffrf hagvy gurl trg gbb ovt naq zrzbel pbatrfgvba bpphef. Vs n zrzbel nyybpngvba reebe vf gevttrerq jura n gbb_ovt_gb_snvy cebprff arrqf zber zrzbel, gura n enaqbz fznyyre cebprff vf xvyyrq, naq gur flfgrz ernggrzcgf zrzbel nyybpngvba sbe gur gbb_ovt_gb_snvy cebprff. Na vagrerfgvat fvghngvba pna bpphe vs gur gbb ovt gb snvy cebprff unf xvyyrq nyy bgure cebprffrf naq fgvyy pnaabg trg rabhtu zrzbel. Va guvf pnfr gur abqr ehaavat gur cebprff gevrf gb zrzbel fgrny sebz bgure abqrf."
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. ×
From Joe Armstrong comes news that Erlang will soon feature a new process flag for those processes that just really need memory, or else: "Too big to fail processes behave like regular processes until they get too big and memory congestion occurs. If a memory allocation error is triggered when a too_big_to_fail process needs more memory, then a random smaller process is killed, and the system reattempts memory allocation for the too_big_to_fail process. An interesting situation can occur if the too big to fail process has killed all other processes and still cannot get enough memory. In this case the node running the process tries to memory steal from other nodes." Read below for your FREE logged-in-reader's-eye view of the special rot-39 version!