In my graduate adventure at Stanford, the course work was in Pascal, our research was in Ada (83), and I learned C, C++ (using Cfront), Prolog, Smalltalk, Lisp, and some formal specification languages. Assembly languages included DEC 10/20, VAX, Data General Eclipse, Sun IV, Cray I, and Sequent. Hennessy and gang were creating MIPS, and the CISC versus RISC debates were everywhere. My first job after Stanford was programming C and assembly language on IBM's brand new, unannounced RISC/System 6000 with a Unix-like OS. My next job was C programming on OS/2 on a very large office system with a homemade object oriented structure using C macros. The next job was a DARPA distributed system using CORBA where I brought in brand new Java to solve our multi platform GUI problem.
New programming languages are mostly boring; a Frankenstein collection of reused parts, badly stitched together. New frameworks are mostly silly.
Thanks to all of the parsing research in the early 1960s,resulting in LEX and YACC, plus books like the Dragon book, and Cooper's Compiler book, and LLVM, many programmers can invent and implement programming languages. But that does not mean that they SHOULD. Programming language design require aesthetics, which are not taught in Computer Science. Knuth's books are titled The ART of Computer Programming for a reason.