Re:Go: Severe memory problems on 32bit Linux
by eternalban on Thursday April 05, 2012 @11:04PM
(#3805805)
Von Neumann architecture falsely lead us to the path with the singular notion of "memory". We need to distinguish at the hardware architecture level between "working memory" and "persistent memory".
I doodle all the time when working. Pristine set of diagrams emerges from the chaos. I wish my computer would play along with this regime ..
Re:Go: Severe memory problems on 32bit Linux
by eternalban on Friday April 06, 2012 @12:24AM
(#3805993)
I haven't mentioned downvotes to date, but the down votes on this is puzzling. Would the down voters care to comment as to why the comment is deemed down vote worthy? (I would think those who work/grok on memory managers do get the point.)
Re:Go: Severe memory problems on 32bit Linux
by kevingadd on Friday April 06, 2012 @04:10AM
(#3806385)
I didn't downvote it, but it mostly read like rambling nonsense to me, so that might be why. Maybe write it so it's clear to people who don't work on memory managers all day?
Re:Go: Severe memory problems on 32bit Linux
by scott_s on Friday April 06, 2012 @08:06AM
(#3806806)
I've worked on memory allocators, and I can't make sense of it.
Re:Go: Severe memory problems on 32bit Linux
by FeepingCreature on Saturday April 07, 2012 @01:41PM
(#3811484)
I think the idea is to differentiate between mutable and immutable data, ie. "worked on" and "final". I don't know what that would give you with regards to GC though.
"Resist complaining about being downmodded. It never does any good, and it makes boring reading." http://ycombinator.com/newsguidelines.html
Re:Go: Severe memory problems on 32bit Linux
by scott_s on Thursday April 05, 2012 @11:46PM
(#3805895)
Brief HN discussion on that paper: http://news.ycombinator.com/item?id=586858
(Precise GCs are possible in C-like languages, but trickier to implement. Here's a recent paper on one: http://www.cs.utah.edu/~regehr/papers/ismm15-rafkind.pdf)