This is not a "We promise to deliver X if you pay us money" situation, this is a "We'd like to make X but don't have enough money. If you give us money we'll do our best to give you something in return".
The only way COBOL might die a natural death is if the biggest companies in the world all fold, without any of their IT assets being sold at liquidation. Given that the value of those assets is easily in the hundreds of millions of dollars for large companies, it's a bit unlikely. COBOL will out live anybody reading (or writing) this comment.
Those studies proving we're willing to hurt others for gain don't disprove that we may be MORE willing to hurt ourselves, as the previous studies didn't offer the choice of WHO to hurt.
What's a 5 year old screwing around with training for a one-in-a-million sports career? If the kid likes doing something, you can (and I think, should) encourage him, not force him into doing what you like.
The kid apparently has either a talent for computers or for learning. Either way, it's a waste to train him for an MCP exam when the kid could be learning something actually valuable in the future. I have no idea whether an MCP exam is easy or difficult, but it'll damn sure be useless by the time he is old enough to get benefits from such certification. Having the kid get an MCP certification is about the parents' bragging rights rather than actually teaching the kid something valuable.
Yes. This. Spend 24 hours a day, 7 days a week for 365 days concentrating on being a better person, nothing else. Do not try to keep in touch with your old self. Do not try to work on your education, knowledge or skills. Do not try to improve anything about yourself except whatever "being a better person" entails. Force yourself to enjoy yourself for 8.760 concecutive hours without interruption./sarcasm
I typically do some programming on vacations too. Because I enjoy doing it. If you're not going to have an internet connection (or rather; any outside help), I'd try to focus on things for which you can get a complete manual in paper. I think a language like C would be ideal; relatively small syntax and standard library. Probably any "old" language would do in your situation. "Generic" IT books would also be great. If you got the complete "Art of computer programming" series, you'd probably be the only human who will have read it completely and will have learned a lot of useful things.
Yes. It's the same button as the "extremists" button. The "child abuse" button is also appropriate, considering these people affect your childrens' future freedom.
You are being pendantic and you know it (or atleast I sincerely hope you do).
If the goal of the exercise was to write an image file format parser, then you have cheated. If the goal of the exercise was to create a game and you just used third party code to load game assets, it's not cheating. And if the goal of the exercise is to write an OS kernel, you should probably re-code parts of the POSIX API (or invent your own API).
If your common sense doesn't tell you where to draw the line, your teacher probably will.
p.s. FWIW, I have written a PNG library for a programming language which previously had none. So yes; there is use in being able to do so. The purpose of education is not to make you highly efficient in one specific programming language (as much as Microsoft and it's ilk might want it to), but to make you able to solve problems on your own.
It's not cheating if you're a professional programmer paid to produce software. It IS cheating if you're a student who is supposed to be demonstrating their ability to create working code on their own.
"Drunk History" disproves both A and B. Comedy Central again indirectly provides better information than the channels dedicated to providing information.
I don't remember seeing one on the net, but I've stopped doing COBOL about 5 years ago.
Besides, the language is besides the point. It's the mentality of the developers.
Basically do every good thing you were taught but practically never do, like checking every possible error, validating every input, keep-it-simple, etc. Then add mature procedures, methodologies and tooling. If you're doing ingenious things in your code, you're probably making it harder to maintain. Code should look like it doesn't solve any problem at all; it should look like any idiot could have made it.
This research used open source from Github as a base.
I used to be a COBOL, PL/1 and Java programmer within a single 80.000+-employee company for over a decade, so I have some insight in the quality aspects of both languages.
If you compare the quality of COBOL code on Github it's generally very low, because most of it is small, half-finished projects made for fun. In a professional environment, COBOL quality is generally very high; much higher than Java code.
None of this has anything to do with the language, rather the Java was running on a desktop, where 99.9% uptime and a projected maintenance lifespan of ~10 years was good enough. The COBOL was running on a mainframe where 99.995% was the bare minimum uptime and there were no projected lifespans; it should be maintained forever.
Heck, even aging PL/1 code on a mainframe is typically of much higher quality than modern Java code on a desktop.
The language is completely irrelevant. If NASA made their in-flight software using Brainfuck, it would probably be rated as an incredibly stable and secure language as well.
In particular links that compare the same resolution. The two videos in TFA went from 480p30 to 720p60 and quite frankly... I didn't see much difference apart from the resolution.
If you posted it several years ago and isn't still highly popular, chances are it'll be in the back of the queue. If it's not at all popular, chances are it's not even in the queue at all. Why waste system resources on old videos nobody watches?
Slashdot Mirror
But is this a contract?
This is not a "We promise to deliver X if you pay us money" situation, this is a "We'd like to make X but don't have enough money. If you give us money we'll do our best to give you something in return".
The only way COBOL might die a natural death is if the biggest companies in the world all fold, without any of their IT assets being sold at liquidation.
Given that the value of those assets is easily in the hundreds of millions of dollars for large companies, it's a bit unlikely.
COBOL will out live anybody reading (or writing) this comment.
Or, perhaps the best option of all:
4. The project team reinstates offline single-player mode.
Those studies proving we're willing to hurt others for gain don't disprove that we may be MORE willing to hurt ourselves, as the previous studies didn't offer the choice of WHO to hurt.
What's a 5 year old screwing around with training for a one-in-a-million sports career?
If the kid likes doing something, you can (and I think, should) encourage him, not force him into doing what you like.
Perhaps learn non-MS-specific, generic computer skills that'll still be useful to the kid in ten years time.
The kid apparently has either a talent for computers or for learning.
Either way, it's a waste to train him for an MCP exam when the kid could be learning something actually valuable in the future.
I have no idea whether an MCP exam is easy or difficult, but it'll damn sure be useless by the time he is old enough to get benefits from such certification.
Having the kid get an MCP certification is about the parents' bragging rights rather than actually teaching the kid something valuable.
Yes. This. /sarcasm
Spend 24 hours a day, 7 days a week for 365 days concentrating on being a better person, nothing else.
Do not try to keep in touch with your old self. Do not try to work on your education, knowledge or skills.
Do not try to improve anything about yourself except whatever "being a better person" entails.
Force yourself to enjoy yourself for 8.760 concecutive hours without interruption.
I typically do some programming on vacations too. Because I enjoy doing it.
If you're not going to have an internet connection (or rather; any outside help), I'd try to focus on things for which you can get a complete manual in paper.
I think a language like C would be ideal; relatively small syntax and standard library. Probably any "old" language would do in your situation.
"Generic" IT books would also be great. If you got the complete "Art of computer programming" series, you'd probably be the only human who will have read it completely and will have learned a lot of useful things.
Yes. It's the same button as the "extremists" button.
The "child abuse" button is also appropriate, considering these people affect your childrens' future freedom.
US Education Chief Should Know About PLATO and the History of Online CS Educatio
Does online CS education also include lessons on how to make database columns wide enough to contain article titles?
(Or comment subjects)
I too prefer to own what I buy.
You are being pendantic and you know it (or atleast I sincerely hope you do).
If the goal of the exercise was to write an image file format parser, then you have cheated.
If the goal of the exercise was to create a game and you just used third party code to load game assets, it's not cheating.
And if the goal of the exercise is to write an OS kernel, you should probably re-code parts of the POSIX API (or invent your own API).
If your common sense doesn't tell you where to draw the line, your teacher probably will.
p.s. FWIW, I have written a PNG library for a programming language which previously had none. So yes; there is use in being able to do so. The purpose of education is not to make you highly efficient in one specific programming language (as much as Microsoft and it's ilk might want it to), but to make you able to solve problems on your own.
Who do you think would be dead first? Sociopathic criminals or the nice people who oppose them?
It's not cheating if you're a professional programmer paid to produce software.
It IS cheating if you're a student who is supposed to be demonstrating their ability to create working code on their own.
Men-hating feminazis is not some random term
No, but anyone using it is helpfully signposting the fact that they're a pathetic fucking idiot.
This in sharp contrast to people using "pathetic fucking idiot" to describe people they don't like.
I think "-1: Post disagrees with my already-settled worldview" is entirely valid in this case.
"Drunk History" disproves both A and B.
Comedy Central again indirectly provides better information than the channels dedicated to providing information.
Regardless, it should be pretty obvious that survival of the Anaconda is a secondary concern.
If by "formerly" you mean "long gone".
I don't remember seeing one on the net, but I've stopped doing COBOL about 5 years ago.
Besides, the language is besides the point. It's the mentality of the developers.
Basically do every good thing you were taught but practically never do, like checking every possible error, validating every input, keep-it-simple, etc. Then add mature procedures, methodologies and tooling. If you're doing ingenious things in your code, you're probably making it harder to maintain. Code should look like it doesn't solve any problem at all; it should look like any idiot could have made it.
This research used open source from Github as a base.
I used to be a COBOL, PL/1 and Java programmer within a single 80.000+-employee company for over a decade, so I have some insight in the quality aspects of both languages.
If you compare the quality of COBOL code on Github it's generally very low, because most of it is small, half-finished projects made for fun.
In a professional environment, COBOL quality is generally very high; much higher than Java code.
None of this has anything to do with the language, rather the Java was running on a desktop, where 99.9% uptime and a projected maintenance lifespan of ~10 years was good enough. The COBOL was running on a mainframe where 99.995% was the bare minimum uptime and there were no projected lifespans; it should be maintained forever.
Heck, even aging PL/1 code on a mainframe is typically of much higher quality than modern Java code on a desktop.
The language is completely irrelevant. If NASA made their in-flight software using Brainfuck, it would probably be rated as an incredibly stable and secure language as well.
They may end up in a sort of limbo, with nobody left to actually sue for copyright infringement.
If nobody can sue, it's effectively public domain.
In particular links that compare the same resolution.
The two videos in TFA went from 480p30 to 720p60 and quite frankly... I didn't see much difference apart from the resolution.
If you posted it several years ago and isn't still highly popular, chances are it'll be in the back of the queue.
If it's not at all popular, chances are it's not even in the queue at all.
Why waste system resources on old videos nobody watches?
+5 Funny, +5 Informative, +5 Insightful and +5 Flamebait.
Thanks, I won't have to read the rest of the comments now.