Live data from Hacker News

COBOL on Wheelchair

azac.pl

21–30 of 43 posts

Re: COBOL on Wheelchair

#21
post #17

I'm usually not one to get offended and and I'm not going to say the author is horrible person like some jerks around here that get offended by non-PC stuff, but it comes across as possibly a tad offensive to use a wheelchair as a jab at Ruby on Rails. I know it's a play on Cobol being old, but a lot of people confined to wheel chairs are young, in the prime of their life and extremely capable in other areas of their…

> offensive to use a wheelchair as a jab at Ruby on Rails Fortress on Freeway, Clojure on clouds.

See also (as noted elsewhere): COBOL on Cogs http://www.coboloncogs.org/INDEX.HTM

And INTERCAL on Interstates http://www.intercaloninterstates.org/

Re: COBOL on Wheelchair

#22
post #19

The fact is COBOL is still used, and useful today, all these decades later. I wonder what the sentiment about Ruby on Fails will be in thirty years time, and I don't think we will still be using it.

Ruby will still be used years from now. Rails, probably not, but Ruby is a good language in its domain (scripting, dynamic languages).

I'm pretty new to Ruby and I'm already sick of people equating Ruby and Rails though I understand how it happens.

Re: COBOL on Wheelchair

#27
Cobol and some of the Basics had a characteristics that made them very desirable for certain use cases. Namely, static memory allocation. Although you can dynamically allocate memory in Cobol, you generaly don't. All storage is statically allocated at program startup. This would be highly desirable if you wanted to allow third parties to execute arbitrary code on your server. That plus no recursive function calls ensures stack and heap safety.

Re: COBOL on Wheelchair

#28
post #16

Earlier quoted context omitted.

> I know it's a play on Cobol being old err... just from reading the title, I assumed it was a play on cobol being disadvantaged, but being old would also imply being disadvantaged physically. metaphorically speaking it makes perfect sense on first read... You seem to be using eval() on human language

If one spent enough time, they could even find "Ruby on Rails" offensive, in some misconstrued way as the word "rails" can be derived as conformist and against free thinking as one is confined to "rails." I don't think it's any of that, but just alluding that spend enough time dissecting anything and someone is bound to find issue with it. I think the overall gist is that we developers are not always marketing people…

I thought on rails was referring to a category of first a person shooters http://www.giantbomb.com/on-rails/3015-169/

Re: COBOL on Wheelchair

#29

I'm usually not one to get offended and and I'm not going to say the author is horrible person like some jerks around here that get offended by non-PC stuff, but it comes across as possibly a tad offensive to use a wheelchair as a jab at Ruby on Rails. I know it's a play on Cobol being old, but a lot of people confined to wheel chairs are young, in the prime of their life and extremely capable in other areas of their…

> it's not really my place to judge since I'm not in a wheelchair myself

Yet you do a sterling job of not letting that hold you back for an instant.

Re: COBOL on Wheelchair

#30
post #26
post #25

Earlier quoted context omitted.

I thought that was PHP's sales pitch. Zing!

Don't be silly. PHP's sales pitch is "at least it's not Perl."

Perl's pitch, meanwhile, has lately been "at least it's not PHP."

I know who's winning that fight, in terms of share, but I'm not sure who I think more deserves to lose it.

Post reply on HN