Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why Ruby is an acceptable Lisp (2005)

randomhacks.net

Post reply on HN
Print view View original

1–10 of 115 posts

Re: Why Ruby is an acceptable Lisp (2005)

#3

Post by behnamoh »

steveklabnik wrote: post #2

A classic. Should have (2005) in the title. Previously on HN: https://news.ycombinator.com/item?id=416589 and https://news.ycombinator.com/item?id=825809 And a follow-up: https://news.ycombinator.com/item?id=2279453

I just checked your links and gotta admit, you're right. Although, still I don't see why this has been posted "three" times before!

I think HN should add a URL checker in the submit page.

Re: Why Ruby is an acceptable Lisp (2005)

#4

Post by miller_joe »

behnamoh wrote: post #3
steveklabnik wrote: post #2

A classic. Should have (2005) in the title. Previously on HN: https://news.ycombinator.com/item?id=416589 and https://news.ycombinator.com/item?id=825809 And a follow-up: https://news.ycombinator.com/item?id=2279453

I just checked your links and gotta admit, you're right. Although, still I don't see why this has been posted "three" times before! I think HN should add a URL checker in the submit page.

I missed the original postings so it's nice to see this for the first time. That would be difficult if HN didn't allow reposts. Though I can understand if I had seen it already.

Re: Why Ruby is an acceptable Lisp (2005)

#6

Post by behnamoh »

miller_joe wrote: post #4
behnamoh wrote: post #3

Earlier quoted context omitted.

I just checked your links and gotta admit, you're right. Although, still I don't see why this has been posted "three" times before! I think HN should add a URL checker in the submit page.

I missed the original postings so it's nice to see this for the first time. That would be difficult if HN didn't allow reposts. Though I can understand if I had seen it already.

That's actually a good point.

On a sidenote, I get a weird feeling from HN's simple UI/UX. On one hand, it feels like the old CLI machines that put the focus on "content" - kinda like "do one thing and do it right".

On the other hand, reading all the comments, getting notified for replies on comments, etc. is really hard. In this day and age, one would wonder if HN really hates JS (well, except for the upvote button).

Re: Why Ruby is an acceptable Lisp (2005)

#8

Post by sundarurfriend »

behnamoh wrote: post #6
miller_joe wrote: post #4

Earlier quoted context omitted.

I missed the original postings so it's nice to see this for the first time. That would be difficult if HN didn't allow reposts. Though I can understand if I had seen it already.

That's actually a good point. On a sidenote, I get a weird feeling from HN's simple UI/UX. On one hand, it feels like the old CLI machines that put the focus on "content" - kinda like "do one thing and do it right". On the other hand, reading all the comments, getting notified for replies on comments, etc. is really hard. In this day and age, one would wonder if HN really hates JS (well, except for the upvote button)…

Community building and maintanence is a very tough job, and the simplest of things can end up nudging people towards unproductive behaviour. HN has consistently maintained at least a decent quality audience and community by keeping the UI free of bells and whistles, and thusly being unattractive to certain kinds of low-effort users. At this point, any change would probably count as messing with a good thing, so the thinking is probably "if it ain't broke, don't fix it."

They are however acknowledging some things that are broken and need fixing, and in recent days have been introducing small changes to correct those (eg. the unvote button, ability to fold). I do hear you on the notification for comment replies thing though, I was really surprised when I found that feature wasn't there, and at times end up missing out potentially good conversations because I didn't check for and notice the reply comment until too late.

Re: Why Ruby is an acceptable Lisp (2005)

#10

Post by pdkl95 »

RangerScience wrote: post #9

The poingant guide link (implimentation of the "belongs_to" class function) is a string of redirects. Anyone have a copy of the original?

http://poignant.guide/book/chapter-6.html#section3

edit:

While I love _why's guide, which can be very useful for learning ruby metaprogramming (and ruby in general), the technique presented there is a bit outdated. Modern ruby doesn't require such an "ugly" style because we now have Object#define_singleton_method[1] as a way of defining class level methods. There shouldn't be a need to use #instance_eval to define methods in the metaclass.

[1] https://ruby-doc.org/core-2.2.2/Object.html#method-i-define_...

Post reply on HN