178 karma · joined November 8, 2011
Once you sacrifice the registers, assembly just becomes a non-portable programming language without any libraries. Unless you build it out with macros and capitalize on it being a programmable programming language, but then why not go with Forth or some kind of Lisp?
What does no-register assembly gain you that higher level languages don't already offer?
Redmonk looks flawed too. I would expect GitHub to create a major sampling bias in favor of smaller, throwaway projects, and in fact, a quick search(1) on GitHub appears to show 2.2 million projects smaller than a kilobyte that have never gotten a single star. Should those be counted? Do they really reflect anything meaningful about the language's rank?
In my opinion, the only meaningful measure of a programming language worth quantifying from the net are StackOverFlow tags: they can be counted and read and provide a real reflection of the language's community without giving any special preference to language, license, or context.
Everything else is hopelessly subjective: whether or not the language maps well to a particular problem, whether it maps well to the way you like to program, and whether it fits into the ecosystem in which you plan to deploy it. You can't measure those with google searches.
(1) https://github.com/search?utf8=%E2%9C%93&q=size%3A%3C1+stars...
Think about that: Skylab was bigger and was launched in a single day by a Saturn V. It also only cost $2.2 billion vs $150 billion for the ISS. If we had stuck with Saturn V's and the Skylab solution, we could have around 50 space stations right now--as opposed to just one. Or better yet, we could have colonies on Mars, and deep space manned missions (remember...the ship in 2001 A Space Odyssey wasn't supposed to be science fiction), and many more super-sized space telescopes, and who knows what else.
Anyway, I look at what we've done with NASA for the past 40 years compared to what we could have done and I can't help but feel like we squandered an incredible opportunity.
If the python developers were any normal business, they would have abandoned Python 3 and returned back to developing what their customers obviously prefer; the problem here is that the python developers essentially concluded that because users get python for free, they aren't customers at all and the python developers can do whatever they want and their users will eventually be forced to fall into line.
Except they won't...
Python users are refusing to migrate to Python 3 as a community. It's a shame that the python developers have decided to try to show their customers who is boss because it won't work--the developers will lose. Many people will continue with 2.7 forever and fork the language in 2020 like Perl 5 day. The rest, like me, have dumped python and moved on to greener pastures.
The true mission of the ISS was to serve as a jobs program for the shuttle.
The Apollo missions accomplished infinitely more--including launching Skylab--than the shuttle and ISS ever could have accomplished.
I really wish they would beef up this portion of the book.
Goto is definitely still out there.
In any case, I know the early history of Smalltalk too. All I'm saying is that your original point was flawed: the ultimate goal of programming languages is to be useful tools; otherwise, they are merely art.
Experimentation during the development of a programming language is an obvious part of inventing them--as experimentation and prototyping is with any tool--but experimentation is not their ultimate goal.
No. Usefulness does matter because, at the end of the day, programming languages are tools, and a useless programming language has no more value than a hammer that breaks if you hit it on anything.
It's nice that there are research languages out there that explore new ideas, but Smalltalk 80--the prototype for all modern Smalltalks--was designed and released to be useful day-to-day, and the Smalltalk distributions out there now--Pharo and Squeak--really look like they want to attract users.
What confuses newcomers is the computer science vocabulary that everyone insists on using when teaching objects. I am a big fan of object oriented programming, but the vocabulary and terrible metaphors of introductory books reads like punishment.
The only language that has done a worse job explaining a simple concept is Lisp with macros. My God! It's like they're trying to keep Macro's a secret.
Having said that, Ruby is the superior language to Python once you get going, in my opinion, because of what it steals from Smalltalk.
I personally quit reading the series somewhere around book 6 or 7, but it wasn't inability that kept him going...it was sales.
GRR Martin, on the other hand, I firmly believe lost track of his story. I don't think he would ever have made any more headway on it had it not been for the HBO miniseries and all the help and fan-made reference pages that cropped up as a result. I predicted for years that the story had stalled and would never see anymore progress during the mid 2000's.
In any case, there was definitely a network that was being used by a lot of people by 1988.