10 ms·
COBOL on Wheelchair
- vezzy-fnord 13y agoOh damn, the aspirations of COBOL on Cogs are now a reality? I call shotgun on "Why You Should Use COBOL on Wheelchair Instead of Ruby on Rails For Your Startup".
- oinksoft 13y agoIntroducing the CRAP (COBOL-RPG-Apache-PL/SQL) stack. Consulting available and a book on the way.
- mscarborough 13y agoIf it is web scale and helps me pivot faster, I'm all for it.
- deleted 13y ago[deleted]
- Roboprog 13y agoLove the logo & name. Whatever the downsides are, I'm guessing memory leaks aren't among them :-) (given that the DATA DIVISION is fixed size, unless there are significant GNU extensions)
- bitwize 13y agoThe logo was done in the font Glass Tty VT220 -- which, fyi, also makes a very nice terminal font for your command line. (In fact, I have yet to see anything that matches it.)
- mcfist 13y ago"The Tao gave birth to machine language. Machine language gave birth to the assembler. The assembler gave birth to the compiler. Now there are ten thousand languages. Each language has its purpose, however humble. Each language expresses the Yin and Yang of software. Each language has its place within the Tao. But do not program in COBOL if you can avoid it." but very nice graphics )
- wglb 13y agoBut do not program in COBOL if you can avoid it This was my motto until i did a year or so consulting in RPG-III.
- antimora 13y agoThough I get the name, I wish it was named something other "on wheelchair". It feels a little degrading. Other than this, it's a nice conceptual work.
- malandrew 13y agoI'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 areas of expertise. Anyways, I leave it to the author to think whether or not this has merit, because it's not really my place to judge since I'm not in a wheelchair myself. TBH I was expecting this to be about someone actually hacking on the cobol that runs their wheelchair.
- lhgaghl 13y ago> 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
- yareally 13y agoIf 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, so we spend more time on making whatever it is and less on the name. Naming things is a hassle, especially when you have no intention on making it a marketable product.
- was_hellbanned 13y agoThis was both humorous and interesting. The people complaining about the wheelchair aspect need to stop and think about their own projections around the word "wheelchair".
- qbrass 13y agoI don't like it because the lack of alliteration makes it a less catchy name. I reckon it's the real reason responsible for Ruby on Rails recognition.
- static_typed 13y agoThe 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.
- vorg 13y agoThe 2 program samples in Cobol and Html shown together made me realize just how verbose Html really is, which makes me think we will still be using Html in 30 yrs time.
- Mikeb85 13y agoRuby will still be used years from now. Rails, probably not, but Ruby is a good language in its domain (scripting, dynamic languages).
- dopamean 13y agoI'm pretty new to Ruby and I'm already sick of people equating Ruby and Rails though I understand how it happens.
- ErikAugust 13y agoI should put up a repo for my "QBASIC Gone Quixotic" project.
- derleth 13y agoI'm waiting for FORTRAN on Steam Engine.
- rhizome31 13y agoNot a microframework, but a friend of mine committed this: http://freecode.com/projects/cgi77 http://freecode.com/projects/cgi77
- marktangotango 13y agoCobol 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.
- wooptoo 13y agoBeats the hell out of DOS on Dope http://dod.codeplex.com http://dod.codeplex.com
- Nimi 13y agoI have to wonder: there are very competent "old technology/mainframe" programmers. They debugged complex programs using very primitive tools when we were all in diapers. Obviously, there are also very mediocre old programmers, but for the sake of this discussion, consider the best practitioners of their generation. How is it that they mostly find themselves stuck in horrible jobs, maintaining legacy software on their old platforms? Surely, for a programmer with experience in assembly and Basic (as an example), becoming proficient in most modern languages shouldn't be a problem. But I strongly suspect that even the minority of the old programmers who bother learning a new language, can't find employment utilizing their new knowledge. Any thoughts?
- memracom 13y agoLots of these guys learned new languages like C aeons ago and have since moved to Java, Scala, Python, etc. The folks who are stuck maintaining legacy COBOL apps are there because they want to be there. The very competent people quickly learn how to use new tools, but can still deep dive and find bugs related to memory leaks and race conditions when it is needed. At the same time, these old guys are likely to demand that everyone around them use TDD so that they don't introduce that kind of bug in the first place. Case in point, Uncle Bob.