u/JohnMatthiasWabwire

I wanted to know what Computer Science students thought about this article by Ed Zitron on the A.I. Bubble.

I also wanted to let you all know that the bubble will burst soon, the economic collapse will be legendary and you will all be very successful in your careers. Do not fear the Ponzi Scheme Salesman, it ends badly for them every single time.

Your work is critical and you cannot be replaced. I love you all and wish you all the good luck in your future endeavors.

Which of the two Shells do you prefer?

Do you like Nushell's Pipelines and Error Messages?

Do you enjoy Fish Shell's Command Completions and VGA Color?

Alternatively - Do you prefer TCL as a Command Language instead?

Nushell: https://www.nushell.sh/

Fish Shell: https://fishshell.com/

TCL Language: http://www.tcl-lang.org/

I was wondering what your opinion of the Slang Shader Language was in the context of Graphics Programming. Have you used it? How is the developer experience? Do you like the tooling?

In my initial study of Computer Science, I always believed that a Command Language like ShellScript, and a Compiled Language, were the only two types of Programming Languages that I would ever need. I also always thought that a Standards Body was a hindrance to Programming Language Development. I have since become a Polyglot and can program in any Programming Language. It inspired me to try as many Programming Languages as humanly possible. In that effort, I learned the value of embedding a Scripting Language in a Program and discovered which Scripting Languages were the "easiest" to embed. I thought I despised Python, Ruby, Tcl, Perl, and Lua. I actually despised the fact that they are used for writing Programs and not Scripting. When Scripting Languages are embedded into Programs, they can be extremely useful. Scripting Languages are also excellent Command Languages, and they have replaced ShellScript, NuShell and Fish Shell in my workflow, entirely.

I have learned that Standards Bodies are actually critical to Programming Language Development. They ensure that Compilers are compliant and that a Programming Language can be implemented by any individual or group. That lack of a Standard for Golang, Dart (ECMA Standard has not been updated), Rust, C3, Odin, Zig, Carbon, Jule, Crystal, and Chapel, is actually a hindrance, that allows the Language Teams to continue the adding features and evolving of those languages, without a Specification.

This has taught me to love Fortran, Pascal, Modula-2, Ada, FreeBASIC, Forth and C. I have the Standards and Specifications to implement those Programming Languages from scratch, if necessary. I don't have to ask the Rust Core Team to slow down on feature development because Fortran is Standardized. It allows me to ignore the evolution of unspecified Programming Languages.

These are valuable lessons that I think we can all learn from. That is why I am sharing my experience here with you.

EDIT: I understand that new Programming Languages need to evolve quickly and will stabilize at some point in the future. My main point was that Standardized Languages don't have that requirement. C++ is the obvious exception to all of this.

Post Scriptum: 100,000 lines or more of code in a Dynamically Typed Program, is scary to me. A Statically Typed Scripting Language would be less of a problem, but that is just my opinion. I know I cannot actually ask the Rust Language Team to slow down on feature development. I was just making a point.