A disturbing new trend?
-
PIEBALDconsult wrote:
When I first learned BASIC in the '80s, the only structure available was the array,
Then C introduced the
struct. Then C++ decidedstructshould have methods, and called it aclassand added all sorts of other artifacts (inheritance, polymorphism, and encapsulation.) Then came along relational databases, and we were introduced in C# to a newfangled way of working with structures, theDataTable,DataViewandDataSet, but those caused impedence mismatches so a new artifact was born, the ORM. Then the jar-heads decided to inflict themselves on the process because this was all too complicated and created JSON, a string "structure" that took us back to the BASIC 80's of untyped data and structure encoded in the string itself. Simultaneously, the "kids" (who were not even a glimmer in the eyes of their parents in the 80's) decided that relational databases were bad and gave us NoSQL, which, guess what, uses JSON, is document oriented and requires client-side callbacks to "join" data across documents. And this is called progress. MarcImperative to Functional Programming Succinctly Higher Order Programming
-
PIEBALDconsult wrote:
When I first learned BASIC in the '80s, the only structure available was the array,
Then C introduced the
struct. Then C++ decidedstructshould have methods, and called it aclassand added all sorts of other artifacts (inheritance, polymorphism, and encapsulation.) Then came along relational databases, and we were introduced in C# to a newfangled way of working with structures, theDataTable,DataViewandDataSet, but those caused impedence mismatches so a new artifact was born, the ORM. Then the jar-heads decided to inflict themselves on the process because this was all too complicated and created JSON, a string "structure" that took us back to the BASIC 80's of untyped data and structure encoded in the string itself. Simultaneously, the "kids" (who were not even a glimmer in the eyes of their parents in the 80's) decided that relational databases were bad and gave us NoSQL, which, guess what, uses JSON, is document oriented and requires client-side callbacks to "join" data across documents. And this is called progress. MarcImperative to Functional Programming Succinctly Higher Order Programming
I am reminded of the quote, "Those who cannot remember the past are condemned to repeat it" - George Santayana.
-
I'll match your HP-67 and raise you an HP-35. (Bargain price $397 [3 weeks before HP-21 came out at $180 RRP])
Good choices! I had the -21, too, or maybe it was the -25 (I forget), but the -67 hurt the most financially when I was making $5/hr. Now I have and use a HP-12C and -15C, and for some reason keep a -48G around; I've never quite mastered that one.
Will Rogers never met me.
-
I'd heard of COBOL.NET, but since I last touched COBOL almost 30 years ago I though I'd do a quick search. I found this:
program-id. Program1 as "ConsoleHelloWorld.Program1".
data division.
working-storage section.
procedure division.
display "Hello World"
goback.
end program Program1.X|
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
You can use COBOL to write restful webservices these days... http://azac.pl/cobol-on-wheelchair/[^]
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
-
COBOL's a pleasure compared to RPG !!! (IBM AS/400 for example)
I've never "played" with RPG (unless we're talking Doom!), but I've had my time with AS400 "screen scrapes".
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
-
You can use COBOL to write restful webservices these days... http://azac.pl/cobol-on-wheelchair/[^]
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
You can probably go from Land's End to John O'Groats on a unicycle, but should you! :)
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
-
PIEBALDconsult wrote:
When I first learned BASIC in the '80s, the only structure available was the array,
When I first learned BASIC in the '70s, the only arrays we had were 1 dimensional, 20 DATA 12, 22, 15, 'X' . . . 120 READ A, B, C, $D 130 GOTO 9999 . . . 9999 LPRINT A, B, C, $D 10000 END
Will Rogers never met me.
When I were a lad, y'know we flipped them switches by 'and. You 'ad it good, we 'ad to turn the handle on t' side 'n t' only electric we 'ad was when we got struck by lightning.
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
-
COBOL's a pleasure compared to RPG !!! (IBM AS/400 for example)
-
PIEBALDconsult wrote:
When I first learned BASIC in the '80s, the only structure available was the array,
Then C introduced the
struct. Then C++ decidedstructshould have methods, and called it aclassand added all sorts of other artifacts (inheritance, polymorphism, and encapsulation.) Then came along relational databases, and we were introduced in C# to a newfangled way of working with structures, theDataTable,DataViewandDataSet, but those caused impedence mismatches so a new artifact was born, the ORM. Then the jar-heads decided to inflict themselves on the process because this was all too complicated and created JSON, a string "structure" that took us back to the BASIC 80's of untyped data and structure encoded in the string itself. Simultaneously, the "kids" (who were not even a glimmer in the eyes of their parents in the 80's) decided that relational databases were bad and gave us NoSQL, which, guess what, uses JSON, is document oriented and requires client-side callbacks to "join" data across documents. And this is called progress. MarcImperative to Functional Programming Succinctly Higher Order Programming
"Then the jar-heads decided to..." This is the first I've heard of the involvement of the U.S. Marines in programming lore, and I must say, I'm skeptical. Weren't they too busy in the Halls of Montezuma and the Shores of Tripoli to be flipping bits and decoding bytes and such?
-
You can probably go from Land's End to John O'Groats on a unicycle, but should you! :)
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
Depends on how important the charity you're sponsoring is to you. Apparently it can be done in less than 9 days in a wheelchair, so you'd only have to take one week of work off. :laugh:
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
-
Depends on how important the charity you're sponsoring is to you. Apparently it can be done in less than 9 days in a wheelchair, so you'd only have to take one week of work off. :laugh:
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
Dan, I said
Quote:
You can probably go from Land's End to John O'Groats on a unicycle.
I can't even ride one. Let me know when you're going, I'll chip in some sponsorship!
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
-
Dan, I said
Quote:
You can probably go from Land's End to John O'Groats on a unicycle.
I can't even ride one. Let me know when you're going, I'll chip in some sponsorship!
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
If you can find me a 50k sponsorship I'll learn to ride and start on the 32nd of Nevember. :doh:
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
-
If you can find me a 50k sponsorship I'll learn to ride and start on the 32nd of Nevember. :doh:
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
If I could find a 50k sponsorship I'd learn to ride one myself.
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
-
PIEBALDconsult wrote:
When I first learned BASIC in the '80s, the only structure available was the array,
Then C introduced the
struct. Then C++ decidedstructshould have methods, and called it aclassand added all sorts of other artifacts (inheritance, polymorphism, and encapsulation.) Then came along relational databases, and we were introduced in C# to a newfangled way of working with structures, theDataTable,DataViewandDataSet, but those caused impedence mismatches so a new artifact was born, the ORM. Then the jar-heads decided to inflict themselves on the process because this was all too complicated and created JSON, a string "structure" that took us back to the BASIC 80's of untyped data and structure encoded in the string itself. Simultaneously, the "kids" (who were not even a glimmer in the eyes of their parents in the 80's) decided that relational databases were bad and gave us NoSQL, which, guess what, uses JSON, is document oriented and requires client-side callbacks to "join" data across documents. And this is called progress. MarcImperative to Functional Programming Succinctly Higher Order Programming
-
"Then the jar-heads decided to..." This is the first I've heard of the involvement of the U.S. Marines in programming lore, and I must say, I'm skeptical. Weren't they too busy in the Halls of Montezuma and the Shores of Tripoli to be flipping bits and decoding bytes and such?
B. Clay Shannon wrote:
This is the first I've heard of the involvement of the U.S. Marines in programming lore,
I know, it's a bad pun on my part of Java libraries known as JAR. :) Marc
Imperative to Functional Programming Succinctly Higher Order Programming
-
"Then the jar-heads decided to..." This is the first I've heard of the involvement of the U.S. Marines in programming lore, and I must say, I'm skeptical. Weren't they too busy in the Halls of Montezuma and the Shores of Tripoli to be flipping bits and decoding bytes and such?
B. Clay Shannon wrote:
This is the first I've heard of the involvement of the U.S. Marines in programming lore, and I must say, I'm skeptical. Weren't they too busy in the Halls of Montezuma and the Shores of Tripoli to be flipping bits and decoding bytes and such?
My boss learned to program in the Marines in the early 90's- using Ada no less.
-
"Then the jar-heads decided to..." This is the first I've heard of the involvement of the U.S. Marines in programming lore, and I must say, I'm skeptical. Weren't they too busy in the Halls of Montezuma and the Shores of Tripoli to be flipping bits and decoding bytes and such?
The U.S. Marines are part of the U.S. Navy. The U.S. Navy gave us Admiral Grace Hopper. Admiral Grace Hopper gave us COBOL. :-\
-
Ah, the good old days... I was early enough not to taught that the string is a data type, but that it's an array (which it still is, but no-one bothers to try to get that into their heads any more), and I've twice seen people reinventing the string by creating an array of characters that can be truncated, searched through, etc. And if I had a penny for every vacant stare I've seen when linked lists were mentioned... * * I could probably buy a Mars bar, but I'd rather let everyone's imagination exaggerate it for me
I wanna be a eunuchs developer! Pass me a bread knife!
Mark_Wallace wrote:
it's an array (which it still is, but no-one bothers to try to get that into their heads
Oh, you mean they who do
char[] c = s.ToCharArray()orchar[] c = s.ToArray<char>()? :doh: -
PIEBALDconsult wrote:
When I first learned BASIC in the '80s, the only structure available was the array,
Then C introduced the
struct. Then C++ decidedstructshould have methods, and called it aclassand added all sorts of other artifacts (inheritance, polymorphism, and encapsulation.) Then came along relational databases, and we were introduced in C# to a newfangled way of working with structures, theDataTable,DataViewandDataSet, but those caused impedence mismatches so a new artifact was born, the ORM. Then the jar-heads decided to inflict themselves on the process because this was all too complicated and created JSON, a string "structure" that took us back to the BASIC 80's of untyped data and structure encoded in the string itself. Simultaneously, the "kids" (who were not even a glimmer in the eyes of their parents in the 80's) decided that relational databases were bad and gave us NoSQL, which, guess what, uses JSON, is document oriented and requires client-side callbacks to "join" data across documents. And this is called progress. MarcImperative to Functional Programming Succinctly Higher Order Programming
And don't forget how hard we all worked to get rid of the "Mainframe+dumb terminal" structure and introduce distributed, networked, intelligent workstations instead. Now they push the Cloud: centralized data and processing again, but with your data controlled and protected by the lowest bidder... :doh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
PIEBALDconsult wrote:
When I first learned BASIC in the '80s, the only structure available was the array,
Then C introduced the
struct. Then C++ decidedstructshould have methods, and called it aclassand added all sorts of other artifacts (inheritance, polymorphism, and encapsulation.) Then came along relational databases, and we were introduced in C# to a newfangled way of working with structures, theDataTable,DataViewandDataSet, but those caused impedence mismatches so a new artifact was born, the ORM. Then the jar-heads decided to inflict themselves on the process because this was all too complicated and created JSON, a string "structure" that took us back to the BASIC 80's of untyped data and structure encoded in the string itself. Simultaneously, the "kids" (who were not even a glimmer in the eyes of their parents in the 80's) decided that relational databases were bad and gave us NoSQL, which, guess what, uses JSON, is document oriented and requires client-side callbacks to "join" data across documents. And this is called progress. MarcImperative to Functional Programming Succinctly Higher Order Programming
I never understood why to allow C++ records to use methods, or act like classes. It's confusing. I now that those methods are used as constructors or to assign values. Sometimes, developers need to work with both, structs like "Pure C", and "C++" classes. Usually when they need to interact a Object Oriented Application, or, with large massive data, or with low level O.S. data that is not Object Oriented, or just a legacy library. When I require to use both "struct (s)" and "class (es)", I avoid adding methods to "structs". Just my 2 cents.
