Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×

Comment Re:On the other hand (Score 2, Interesting) 267

Agree. I am not a landlord but my mother-in-law is. And one of her tenants have been living there for 40 years. FFS I am 55, so she lived there when I was in middle school. As soon as that woman dies I am going to be saddled with... no I am going to sell the bloody place and get rid of the problem ASAP. Jesus, no.

The other floor that she rented out was occupied by a crazy nutjob who could not hold a job that had a fastass hubbie who stayed there forever and she carted beer up for him. When she finally got tossed (for threatening my MIL) the had to carry him out on a stretcher. The sad thing is that they now live in a better place. Probably pay more though.

The problem is that this house is in a small village an my idiot MIL never had a lease contract, they just did things with handshakes back then. Or something like that, I can never figure.

Comment Re: CRAPPLE! (Score 1) 34

This has not changed. An old standing habit of mine has always been recommending people to trim the CPU budget and spend it on extra RAM when asking advice for buying a computer

Always served me well. The machine under my desk is an 10 year old second hand Xeon but it has 128 GB on board. It still kicks butt as a workstation and VM host.

My older Laptop has 32GB. I have a rather useful i7 3770K that I put 32G in back in 2009 when 8G was upper class and 4G the common choice. Works great till this day

More RAM makes a computer last much much longer and the slight investment costs less in the end

Comment Re:GC-based attacks (Score 1) 56

The Erlang/Elixir VM, BEAM, has a garbage collector does exactly this. Erlang/Elixir is written in such a way that there are many concurrent processes with NO SHARED MEMORY between them. All interprocess comms is done by message passing and the processes cannot build pointer for variables that point to a address in another process's memory.

This means if a process dies the GC can throw out the entire heap for the process in one go, because there are no pointer references that point between the different per-process heaps. The memory graph that the GC has to deal with consists of a much smaller amount of larger chunks with basically no links. The Erlang GC is VERY efficient, as in realtime efficient because of this.

Slashdot Top Deals

Somebody ought to cross ball point pens with coat hangers so that the pens will multiply instead of disappear.

Working...