<ELLIOTTCABLE>
alexgordon: what's wrong with "ruby's" approach?
<ELLIOTTCABLE>
ooc
<alexgordon>
ELLIOTTCABLE: it sucks
<ELLIOTTCABLE>
devyn: cucumber-y, you mean?
<alexgordon>
I meant rails
<ELLIOTTCABLE>
alexgordon: so, ActiveRecord's?
<ELLIOTTCABLE>
why? that's probably the single most popular part of rails. People *really* like that approach to building and maintaining models in large projects.
<alexgordon>
yah
<ELLIOTTCABLE>
no strong opinions on my part, just want insight.
<alexgordon>
ELLIOTTCABLE: *shrugs* it's ok most of the time but I dislike putting SQL in a string and passing parameters
<alexgordon>
if you're writing a language designed for web programming then something like LINQ is a really good investment
<ELLIOTTCABLE>
LINQ?
<alexgordon>
ELLIOTTCABLE: in C#
<alexgordon>
language integrated query
Sgeo has quit [Read error: Connection reset by peer]
<purr>
¯\(º_o)/¯
alexgordon has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
alexgordon has joined #elliottcable
<Cheery>
anyone happens to know, where I could find discussion about finalizers in GC?
<Cheery>
should GC close file handles or manage resources other than memory?
<Cheery>
the cost of finalizers could be bad
<Cheery>
or is it?
<Cheery>
why this question is relevant at this point, is the finally: -statement
<Cheery>
I'm considering whether to bring it, or not, and how.
<Cheery>
observing that if it is brought, it forces GC to walk through the stack if a greenlet is collected
<Cheery>
and evaluate, on the gc cycle, the pieces of that stack.
<Cheery>
finally statement is neither 'final' in python either
<Cheery>
I can always shut down the computer, take that python.
<Cheery>
other kinds of python resource management basically fails..
<Cheery>
I've seen this happen quite often.
<Cheery>
if it drops to the gc, the __del__ never runs.
<Cheery>
I would attribute that to python though..
<Cheery>
it is possible to implement a deterministically running finalizer with weak key dictionary
<Cheery>
hmm..
<Cheery>
is it?
<Cheery>
weak value dictionary rather
<Cheery>
the finalizer is bound to the value dictionary.. then we have finalizers and the values.
<Cheery>
when it is detected that the finalizer is no longer in the dictionary, run it.
<Cheery>
weak key/value dictionaries present similar problems
<ELLIOTTCABLE>
get a goddamn znc or something you anus
<ELLIOTTCABLE>
that article raises an interesting point to me.
<ELLIOTTCABLE>
garbage collection is a specific case of a general problem of resource-management.
<ELLIOTTCABLE>
so if garbage collection is "simulating a machine with infinite memory", can we generalize that to "simulating a machine with infinite resources"?