so i did some stumbling about and encountered this:
http://weblog.jamisbuck.org/2006/10/27/mining-activesupport-object-returning
i understand ruby, which is great, because the linked "explanation" of the K combinator really doesn't do it for me.
but ruby's 'returning' is now the coolest thing i've learned all day.
tea bagger is injured protesting government health plans.
okay.... but then:
Brown told the crowd that Gladney is accepting donations toward his medical expenses. Gladney told reporters he was laid off recently and has no health insurance.
heh.
heh heh!
HAR HAR HAR HAR HAR!!!!
i just realized, i have two languishing facebook friend requests that i'm not going to accept. they've been stewing there for months because i don't know how to delete them. that's not the funny part.
this is: one's from avi, the other's from ravi.
har de har de haw har!
i was with you, dude, right up until you talked about scanning a hash table.
that's a mighty poor hash table you've got there if you're doing any sort of scanning.
a couple of weeks ago i decided to give ruby on rails another chance. http://beans.sainttoad.com is the result of that.
at the time, i was seriously impressed at how easy it was to get my app up and running. in one week of part-timing it, i went from 0 experience with rails/ruby to a full, non-trivial deployment (reverse proxy, url-rewriting, url-prefixed deployment, har). at the end of the week i'd whipped up 90% of the features i wanted in my app, a decent (or at least consistent) style, and am now happily using the app with no problems.
except one problem: when i go back to polish off those remaining 10%, i'm left wondering: wtf am i doing this in ruby? i mean, really?
the problem with ruby on rails: ruby. i've been told that ruby makes much more sense if you're japanese. well shucks, i'm not japanese. is that why i think that "" == 0 == [] == true is a stupid idea?
rails makes it incredibly simple to get a useful app up and running with breathtaking speed. but then, in the real world (and not in the world of my tiny-dataset app), you'd go back and refactor and optimize your database access and so forth. that looks to be a pain in rails, where the ORM makes it difficult to do things well. or, perhaps the problem is that the ORM documentation makes it difficult to make the ORM do things well. that's a difference without a distinction.
at work, i use pylons. it's got a lot of the sugar of rails, but it's got a different philosophy: too much magic is bad. rails is all about the magic. in pylons, there's much less magic, and when i need to fix something, because i'm not relying on magic, i know how to fix it. rails? not so much (although i did find and fix a bug in the auth package: but to merge it back? i have to learn git? no thanks).
anyhow: i'm not making any sense. here i am saying rails is great and ruby sucks, then telling you why rails sucks. i've had minor exposure to each and this is the end result:
ruby: i get it, it's like python, only there's the bizarre 0 == true thing, and the block thing which is kinda cool but really a very complicated route to doing simple things, and less emphasis on functional programming, and not enough haskell influence (:D).
rails: super easy to get working. encourages some pretty bad design choices and also encourages beginners to think they know what they're doing, which leads to pretty bad design choices. this is a tough problem for framework designers to address, and i can't say i blame rails for making the choice they made. after two weeks of not using rails, when i went back to look at it, i wondered: wait, why am i using rails? maintenance is maybe not so enjoyable as the thrill of getting the app whipped up. and since maintenance is what app development is all about, maybe i picked a poor framework.
for those of you that read this mess but not slashdot:
How strange,
In your country if you're accused of a crime you consider it a natural right to have access to a free lawyer and access to free legal advice is enshrined in the highest law of the land. The spirit of socialism at its finest! But oddly there's no "socialism" conflict in that area, even from the "libertarians".
But when it comes to the right to some basic level of healthcare, no go. If you're poor you and your children can suffer.
It's an interesting paradox actually, because generally the poor commit more crime. So people are happy to fund legal representation for lower class criminals. But are definitely not happy to help fund a basic level of health care for themselves. Which is somewhat odd as the vast majority of people will be affected by health issues in their life, not criminal courts. And the costs associated with the two are about the same.
A strange but interesting culture.
(Yes I'm aware of the low quality of public defenders - due to a lack of funding more than anything. But it's better than nothing, just like public hospitals)
this really screams YOUR DOIN IT RONG!!
but maybe i just dunno what i'm talking about.
for exactly this reason That form is older than I am, and it still works perfectly.
probably it isn't older than me, but it's really, really old and it works every time.
is it today that i finally get around to playing with google app engine?
maybe -- i've got the day off, and once the tri-tip hits the smoker grates, i have little to do for the next 3 hours.
actually, as of right now, i have little to do for the next 3 hours.
heh.
didn't i say the internet was awesome?
