11 ms·
Steve Yegge Grades His Own Predictions
- budu3 11y agoIt's good to see that Steve is back publicly blogging.
- presidentender 11y agoLet's not count our chickens.
- bcoates 11y agoThis is more of a one swallow does not a summer make situation
- presidentender 11y agoYes, but a bird in the hand is worth two in the bush.
- JustSomeNobody 11y agoBack? Doesn't look like it. I mean, one post, right? Or am I just not seeing any more?
- Frozenlock 11y ago> "I had high hopes for Clojure for a while, but they're fairly user-hostile, even if they think (and loudly assert) that they aren't." Is that a prevalent opinion? I'm often in #clojure/#clojurescript and found the community quite helpful.
- albemuth 11y agoI took that to mean the language and tooling were hostile, not the community.
- pbiggar 11y agoWould love to hear more about this. AFAICT (from using it every day for 4 years), it's all pretty awesome (except startup time, but that doesn't matter much because REPL).
- dantiberian 11y agoThe Clojure community is great, but Clojure/Core has historically not been interested in lowering the barrier to entry with Clojure. I think this is part of what Steve is referring to.
- calibraxis 11y agoYegge's previous critique: https://news.ycombinator.com/item?id=2466731 https://news.ycombinator.com/item?id=2466731
- Frozenlock 11y agoThank you very much!
- tensor 11y agoFrankly, I'm quite happy clojure has not turned into a "yes" platform as he suggests. I also find Yegge's approach of insulting anyone who doesn't agree with him to be very off putting and not constructive. What I took away from it is that if you disagree with him, you are going to fail and be labelled hostile in his mind.
- jsmeaton 11y agoLook for the post on the mailing list beginning with "I think that one's called "Perl". " That's where the real meat of his argument seems to be. > Unfortunately I've conflated saying Yes to features vs. saying yes to users. Saying yes to features is clearly a way to get a kitchen sink a la C++ or Perl. I didn't see any instances of him insulting people, though he was hostile in the same way he accused the clojure community of being hostile. But the points he made seemed sound to me. Saying "no" to users can seem hostile to the person you're saying no to. You need users, or you die. So say yes and survive.
- tensor 11y agoSuggesting that clojure is dying or going to die is some serious hyperbole. The community is growing steadily every year and is being adopted by industry players. Maybe not quite as fast as languages like scala that cater more to what users are familiar with, but that's not a bad thing necessarily. Speaking of scala, you could also use it as an example of what happens when you say yes too much. In fact, to me, that's scala's major weakness. Sure, users can use it like a better java, but you aren't gaining as much from doing that as you would if you actually adopted a more functional style of programming. This is exactly what clojure encourages. I wouldn't count promoting this philosophy as any more hostile than any other opinionated language. It certainly sounds like Clojure is not for Yegge, but that's not a valid reason to call the community hostile and claim that it's a dying language. Especially so because it's the complete opposite of what is true. The community is very helpful and welcoming to newcomers and the usage is growing, not declining.
- lackbeard 11y agoRegarding #1: he did mention, offhand, that folks might use json instead of xml, which is basically what happened.
- dochtman 11y agoOn number 9: "Apple's laptop sales will exceed those of HP/Compaq, IBM, Dell and Gateway combined by 2010" So, the prediction mentions "laptop sales", but in his grading, he talks about "Apple Macs only have 13% market share", which I would assume means unit market share? Given the profit share vs market share dichotomy seen in smartphones in particular, I'm left wondering if he isn't a bit too harsh on himself here. It seems likely to me that sales-based market share would substantially exeed unit market share for Apple Macs; surely Asymco or some other smart analyst has run the numbers on this?
- jsprogrammer 11y agoI guess it depends on your sales metric: number of people now with access to the technology vs. amount of $ padding added to Apple shareholders' bottom line. Number of people is much more relevant and interesting.
- phonon 11y agoHe should definitely give himself more credit...in the US at least, Apple laptop revenue exceeds that of all Windows laptops combined. http://betanews.com/2015/08/12/yikes-apple-laptop-revenue-share-exceeds-windows-pcs/ http://betanews.com/2015/08/12/yikes-apple-laptop-revenue-sh...
- math0ne 11y agoWhy isn't this guy a professional writer, hes so good at it!
- bgun 11y agoI hear programming pays better.
- jfb 11y agoHe also might simply prefer writing programs to writing blog posts.
- fixermark 11y agoProfessional software engineer at Google pays better, in a probability-of-income-per-dollar sense.
- Tloewald 11y agoThe number of writers who make more than a senior Google engineer would be very, very small.
- wvenable 11y ago> NoSQL data stores in their various incarnations apparently have equalled or slightly surpassed RDBMS as of 2014-2015 Wait, what is this based on? Hacker News postings? There is no way that NoSQL has surpassed RDBMS even among startups.
- ranman 11y agoI think it's more that they're considered and deployed at the same scale as RDBMS--obviously oracle still has a pretty strong hold on the database world: http://db-engines.com/en/ranking http://db-engines.com/en/ranking
- davidw 11y agoOne thing that ranking does not quite take into account is SQLite on Android and iPhone. That's got to count for something, as that's a pretty massive deployment.
- baq 11y agosqlite, per itself, isn't a RDBMS replacement, it's a fopen() replacement.
- wvenable 11y agoAccording that stat counting the top 10, NoSQL databases account for 12% popularity. Given that this is talking about website mentions, job offers, twitter mentions and not actual installs that number isn't indicative of much success. 10% is actually pretty impressive but not equalled or slightly surpassed.
- NhanH 11y agoWhat exactly is multi-threaded programming in this context?
- debacle 11y agoProgramming that explicitly creates and manages threads.
- grayrest 11y agoI interpret it as shared state concurrency. That is, multiple threads sharing the same address space performing reads and writes on shared data: atomics, mutexes, etc. From the update I understand that he's considering things like Actors, Communicating Sequential Processes (goroutines), and data partitioning divide+conquer (MapReduce) approaches as different even if they happen to be implemented on different threads sharing the memory space. I'm not sure on the relative prevalence but I can say that I've read relatively little about what he's calling multi-threaded programming. Mostly just a handful of lock-free data structures from the C++ guys and Rust's take on how they can do it while avoiding data races due to the type system. The alternatives, on the other hand, have been on HN pretty much continuously since HN started up.
- GFK_of_xmaspast 11y agoc++11 added a ton of support for that kind of stuff tho, with language-level atomics, mutexes, etcetcetc.
- wvenable 11y agoAnd this is in direct contrast to how much hype there was for programmers to use multi-threaded programming due to leveling off of single-core performance and the prevalence of multi-core systems.
- dbaupp 11y agoI'm not sure about this, e.g. concurrent data structures are a form of shared state concurrency and "worker pools" may or may not use shared state, it seems orthogonal.
- 11y ago
- throwawayaway 11y agohe predicted ruby's massive success relative to python over some of that time stretch in another article. he predicted everyone would be writing code in the browser instead of emacs & co and i don't think that has come true.
- omouse 11y agoI started using cloud9 IDE for a few free/open source projects and I have to say, it's awesome. I have 3-4 computers that I work off of and it's a god-send to be able to just fire up a browser and continue where I left off without worrying about managing the environment setup for each machine. I liked using PyCharm and WebStorm and I love emacs and I've been using Atom lately, but the convenience of an always running virtual machine with a pretty good text editor is hard to beat.
- ivan_burazin 11y agoThanks awesome! Although I am the founder of a competitor called Codeanywhere, but super synced that your into a CloudIDE!
- omouse 11y agoI think I tried using Codeanywhere and it didn't quite work for some reason, it may have been when I tried using the Android app? Is Codeanywhere free/open source? That's one reason I prefer Cloud9 though I like the 2-factor auth for private/proprietary repos...
- ivan_burazin 11y agoI could be the Android App as there are some issues with some devices. Codeanywhere the Web App is Free to use but not Open source (yet). We also offer 2FA to our users :)
- lgas 11y agoRuby's massive success relative to python? The August 2015 Tiobe index lists python up to 5th from 7th a year ago, and ruby holding steady at 13th across both years. I know tiobe isn't necessarily an ideal source, but this fits my intuition better than your suggestion. Can you elaborate on your perception of the two?
- temuze 11y agoDan Luu's original post: http://danluu.com/yegge-predictions/ http://danluu.com/yegge-predictions/
- mykphyre 11y agoThanks for posting this. Context is always welcome :)
- pbiggar 11y agoI think he's being overly harsh on himself. As he said in the original rant "the predictions themselves don't matter! Most of them are probably wrong. The point of the exercise is the exercise itself, not in what results" Imagine someone in 1850 making the prediction that "by 1950, everyone will have a horse". Though they say "horse", they really mean "everyone will be able to afford their own personal transport", as a reflection on the changing socioeconmic something something. And they would be right. Sure the horse is mechanical, isn't shaped like a horse, and consumes petrol, but your prediction is correct, even though you didn't know exactly how it would play out. The same is the of Yegge's XML DB prediction. If he was saying that XML is going to be amazing, then he's wrong. If he's saying the RDBMSes have problems, then he's right. And actually he's saying "RDBMSes suck, so something will replace them, and XML is big enough that it will be XML". So that looks like a 50% score to me. With Apple, he's basically saying "apple is shiny, and shiny will win". That prediction has been 100% correct. The fact that iPads disrupted the laptop model means he's more correct than if they had just sold more Macbooks. 100% score here, IMO.
- tinco 11y agoXML databases actually got to be amazing, if that was his prediction he would have been totally right. The fact is that they just got amazing a little bit too late. No one is going to consider an XML database because XML got a bad reputation (and rightly so). But XML database technology actually has nothing to do with XML. The idea is that you store nested data nodes. Imagine you have a mongodb collection, and in it you have documents, and each of those documents would also be a mongodb collection in which you could insert more documents. You can build full graphs like that, and if you allow references to nodes those graphs can be cyclic too. Pretty powerful right? Now you might say yeah of course, but that's got to be crazy slow! And at the time Yegge made his prediction you would have been right. But then academics came into the scene, they developed data structures and algorithms that allow you to store these recursively nested documents in column stores (think SQL table with 2 columns, a primary key and a piece of data) in such a genius way that you can make whatever query you can think of (recursive, joins, whatever) and execute them almost as fast as any indexed search query. That magic happens, and is implemented for example in MonetDB/XQuery which sadly got abandoned a few years ago. I still think if a crazy person sets off to go build a database company (crazy people like that seem to be quite popular in SV these days) they could make a lot of money forking MonetDB/XQuery, and search-replaceing every instance of X with J and every instance of XML with JSON. Crazier still, you can even let MonetDB/XQuery results be formatted as json, even before MongoDB became popular I think.
- abc_lisper 11y agoSteve, if you are reading this, please know that we miss your writing. It would be awesome if you could write now.
- david927 11y agoFrom 2007: ... I'm sure someone will let me know, probably by tying a nice note to a nice red brick and hurling it through my window. You should see the email I get sometimes. I think you can estimate the maturity of a culture by how easy it is to commit heresy. There is simply no excuse for how people reacted to his writing. It reflects poorly on all of us. Maybe Alan Kay is right that we (the IT industry) are a pop culture, complete with our own sort of Kanye West.
- kristopolous 11y agoYou mean full of undeservedly famous and ignored genius?
- dack 11y agoYeah, it pains me to even read this kind of thing, because it makes me remember the feeling of reading one of his new articles (which was, maybe even _irrationally_ excited). I don't feel that way about any other blogger, past or present. It must be the combination of interesting and unique ideas with a really entertaining writing style that got me. Maybe it even had something to do with the years he was writing (I was in high-school & college at the time). I don't really think Yegge is going to get back into it (and I don't blame him), I just hope to find someone else with similar qualities.
- swah 11y agoI felt mostly the same, and also can't explain. I also felt like he was a window into the kind of companies I wish I could have worked in (in their "golden years").
- w23j 11y agoThe long form writing combined with an entertaining style and real experience to back up his stories made his stuff pretty unique in my opinion. Certainly among the best articles I have read on the net. I think it was in a Stackoverflow podcast where he said that the hateful feedback he got was the main reason he stopped writing. It sad that we as a community did not get more of that content because of anonymous haters on the internet. (Pretty similar to Joel Spolsky actually. Both in quality of content and hateful feedback in return.)
- PaulHoule 11y agoManagement refuses to believe Error Prone == Evil far more than programmers.
- jbreinlinger 11y agoI really wish more people would revisit predictions to see how good they were. Not enough of this. Great job.
- mykphyre 11y agoI know exactly what you mean. Most predictions are cast into the wind and only the ones that are correct are recognized later. Nate Silver talks about this in his book "The Signal and The Noise"; I highly recommend it.
- m0v_eax 11y agoHe is way off about XML.. It is bloated and tedious to work with. For most scenarios, there are immensely better alternatives. For the record, I was heavily involved with XML years ago and helped create a popular light weight xml-based cms.
- adevine 11y agoI think he's saying his main point, though, is that storing objects in a RDBMS using OR-mapping is a pain in the ass and there will be better ways to do it. With the advent of NoSql DBs, and the number of DBs that store their data in JSON, I think this is largely correct. Back in 2004, XML was largely shorthand for "serialized object". He was wrong about the serialization format, but right about the overall idea.
- panzagl 11y agoPeople who hate XML never had to deal with variable-length bit field formats...
- Marazan 11y agoHe's hard on himself over the smartphone start, the orignal iphone had sales numbers that were a rounding error.
- pavlov 11y agoQuite true. The iPhone didn't really take off until late 2008 when iPhone 3G, the global launch and the App Store happened. In the first two months, iPhone sales were slacking so much that Apple suddenly dropped the price by $200 after just two months on the market: http://www.nytimes.com/2007/09/07/technology/07apple.html?_r=0 http://www.nytimes.com/2007/09/07/technology/07apple.html?_r...
- ghaff 11y agoI strongly suspect that the vast majority of people--even here--"remember" a number of Apple's biggest wins as being inevitable from Day One. In fact, as you say, the iPhone didn't become a must have smartphone until 3G/3GS timeframes. Similarly, until the 4th gen iPod with the click wheel, the iPod was pretty much just another reasonably well-regarded, albeit pricey, MP3 player.
- abritinthebay 11y agoI think that anyone that doesn't remember the iPhone as being a wild crazy success was just not paying attention - and the numbers back that up. The 3GS was when it exploded but it was already a big success by that point. What people have to remember is the success of the iPhone is practically unprecedented in terms of adoption. It's incredibly rare to come out and dominate an industry like that when you're a new entrant into the space. Even if the iPhone had continued it's July-September sales curve it would have been a success. It just got even more-so when the other versions came out.
- ghaff 11y agoI think we're quibbling over terminology. As you say, it was the 3GS that "exploded." (And it's when I personally upgraded from a Treo 650.) I agree that, to a significantly greater degree than the iPod, the iPhone was from Day 1 obviously a big deal even if it wasn't clear that most competitors really needed to get busy working on their gravestones.
- idlewords 11y agoSubstance aside, this is an excellent example of how people will give themselves partial credit even for unequivocally wrong predictions. The temptation to double down on your original hunch can be irresistible.
- wzdd 11y agoRight -- all the predictions that mention specific percentages, or include specific dates, are wrong. The ones which are actually correct are the vague ones ("A new internet community-hangout will appear", "Someone will make a lot of money by hosting open-source web applications"). This is why fortune tellers don't mention dates. The whole point, which Steve himself covers eloquently in his original post, is not to score the predictions but to talk about the ideas. And if you look at intent behind each prediction, some of those "partially-correct" ones are actually completely wrong. I mean look at these lines on the prediction about the mobile market being at least five years out: "But the carriers don't know what the hell they're doing, and the content and distribution models aren't worked out yet, and won't be for a long time. A lot of players need to get their collective acts together for the mobile market to take off, and it just hasn't been happening. [...] Don't get me wrong: it will happen someday. But I think it's not going to be any time soon. Betcha!" Then Apple told the carriers what they were doing, and figured out "content and distribution models", and this all happened within three years, and the reason it happened so quickly is because Apple didn't rely on any of the large set of third parties and vested interests which Yegge thought someone was going to have to motivate in order to make progress. That prediction was apparently 60% correct. It's doublethink.
- Jun8 11y agoFor his 10th prediction: Using the Chebyshev inequality (https://en.wikipedia.org/wiki/Chebyshev%27s_inequality https://en.wikipedia.org/wiki/Chebyshev%27s_inequality) and assuming Yegge means being two sigmas away from mean programming talent to be "average" (k=2) we see that the probability for this to happen in 0.75 for any distribution. So most of us are average.
- krosaen 11y agoWould love to hear more about the assertion that clojure is user hostile. He last elaborated in 2012 here: https://plus.google.com/110981030061712822816/posts/KaSKeg4vQtz https://plus.google.com/110981030061712822816/posts/KaSKeg4v... which basically boiled down to an impression drawn from a conference where a speaker warned against using macros. I fully accept Yegge doesn't dig clojure, and perhaps he owes nobody any further explanation, but given his previous visibility as a champion of lisp and all the cool stuff happening in clojure / clojurescript, it just doesn't add up; his critiques are incomplete in that they fail to acknowledge the positives in the language.
- cgrand-net 11y agoAh! So it's my fault…
- lazyant 11y ago2- Google App Engine and Heroku are not Open Source, can't think of an Open Source PaaS or one that is Open Source and made somebody a lot of money,
- sciurus 11y agoThey aren't open source, but people run lots of open source software on them.
- jacques_chester 11y agoCloud Foundry. The major contributors are Pivotal and IBM. Pivotal is on track for $100 million in revenue this year, the fastest growing revenue for any open source product in history. Ever. In any category. Disclaimer: I work in Pivotal Labs, another division in Pivotal.
- jsmeaton 11y agoI thought that github met his exact prediction. They took an open source product (git), hosted it as a webapp, and got people to pay for it (github enterprise).
- cpeterso 11y agoHe should stated at the beginning (or title!) of the post when he originally made these predictions. You have to read to the very end to see the footer "(Published Nov 10th, 2004)".
- jrochkind1 11y ago> There was also some discussion on HN about whether I thought NBL was JavaScript. Yes indeed I did, and said so on stage at OSCON NBL?
- edmccard 11y ago>NBL? Next Big Language
- DKnoll 11y ago7) The mobile/wireless/handheld market is still at least 5 years out. Nope, it was 3 years out. iPhone came out in 2007. Pretty easy to calculate this one. Score: 0.6 Well, when he made the prediction the smartphone market was already there, it just didn't appeal to consumers. The year of his prediction the Treo 650 was released which I would argue was the first fully-fledged smartphone (that I know of, anyway) similar to those we use today. There were also earlier models of the Treo lacking mobile data. Kyocera made some similar devices as well.
- sampo 11y ago> Treo 650 was released which I would argue was the first fully-fledged smartphone Or Nokia Commumicators from 1996 onwards. https://en.wikipedia.org/wiki/Nokia_Communicator https://en.wikipedia.org/wiki/Nokia_Communicator
- ac29 11y ago> Apple Macs only have 13% market share as of late 2014 Can anyone find a source for this claim? The 2 I found [1][2] claim OS X has about an 8% market share, which is about 40% lower than his claim. [1] https://en.wikipedia.org/wiki/Usage_share_of_operating_systems#Desktop_and_laptop_computers https://en.wikipedia.org/wiki/Usage_share_of_operating_syste... [2] http://appleinsider.com/articles/15/07/09/new-idc-numbers-show-mac-sales-up-161-percent-in-june-quarter http://appleinsider.com/articles/15/07/09/new-idc-numbers-sh...
- yellowapple 11y agoI think he would've gotten a better score on the Lisp prediction if he didn't specify Lisp and instead went after Lisp-like features. Metaprogramming and homoiconicity are becoming increasingly popular, as are machine learning techniques.
- dwd 11y agoGiven this was 2004 you have to give him full points for his prediction on PG - "He has an impressive resume, and he appears to be only just getting started."
- kibwen 11y agoMacro systems are becoming increasingly popular (e.g. Rust and Sweet.js), but arguably neither of those languages is homoiconic in the Lisp sense (though see also Dave Herman's "Homoiconicity isn't the point" http://calculist.org/blog/2012/04/17/homoiconicity-isnt-the-point/ http://calculist.org/blog/2012/04/17/homoiconicity-isnt-the-... ).
- yellowapple 11y agoBy homoiconicity, I was referring to Julia and Elixir, both of which are cited as being homoiconic (even though some purists disagree). Also, I think "Homoiconicity isn't the point" misses the point. Homoiconicity isn't about syntax - indeed, Lisp isn't technically confined to s-expressions, and was originally designed for M-expressions before folks realized that s-expressions were much easier to implement - but rather about the ability to represent a program as ordinary data and to manipulate it as such. Yeah, I can do all sorts of metaprogramming in, say, Ruby or Perl, but you won't be able to go very far before you end up passing strings into `eval`; this is because they're not homoiconic (at least in their current forms). Meanwhile, the ability of languages like Elixir to actually modify a program's syntax tree directly - a.k.a. homoiconicity - makes metaprogramming much easier. The two concepts go hand in hand. S-expressions happen to be very convenient for defining tree-like structures, like - for example - Lisp programs. They're not strictly required, however.
- incepted 11y ago> 4) Java's "market share" on the JVM will drop below 50% by 2010. Definitely hasn't hit 50%. However, Scala has really tremendous adoption Yeah, not really [1]. [1] http://www.indeed.com/jobtrends?q=scala%2C+java&l= http://www.indeed.com/jobtrends?q=scala%2C+java&l=
- Double_Cast 11y ago> I had high hopes for Clojure for a while, but they're fairly user-hostile, even if they think (and loudly assert) that they aren't. I'm curious as to what this means. In what way is clojure hostile? Is there some reason I should avoid it?
- brianobush 11y agoAny good next ten year predictions? Steve, or anyone else?
- personomas 11y ago> But even I don't use Lisp anymore, other than the occasional Emacs hacking. What do you use? Why don't use Lisp anymore?
- wtbob 11y agoPersonally, I'm still trying to use Lisp every chance I get. My window manager is stumpwm (Common Lisp) and my editor is emacs (elisp). Racket definitely has some very cool ideas, but I just don't like Lisp-1s and I do like the industrial strength of CL. The early-to-mid 2000s were an exciting time for Lisp. Practical Common Lisp (http://gigamonkeys.com/book/ http://gigamonkeys.com/book/) was coming out; Paul Graham was writing about how Lisp was a secret weapon; reddit was based on it. It seemed like the stars had finally aligned. But then…nothing happened. Ruby captured a huge amount of the hype cycle, Python captured a huge amount of the pragmatists, and…nothing happened. The Common Lisp community kept on churning out incredible code, building a better mousetrap and waiting for the world to beat a path to its door and…nothing happened. It really is dispiriting to reflect on.
- kriro 11y agoI think just the fact that Carmack (and Carmack Jr.) is interested in Racket deserves a bump from 0.0 to 0.1 for the Lisp prediction. VR has the potential to become a big and interesting market and one of the leading tech guys in that field is fascinated by a Lisp. He might just make it work. [note: I've never used Lisp for anything just an obvervation]
- Guthur 11y agoHe is not the first to look at Lisp, and I would surprised if he is the last. Lisp has some really compelling properties as means of expressing a program. Unfortunately there is a severe impedance mismatch between Lisp and the Algol inspired languages of today's mainstream. Overcoming the mismatch is not difficult but takes effort and so few are willing to expel any real effort; Carmack is certainly not the sort to shy away from some effort. I would recommend trying out Racket or Common Lisp if you can. Common Lisp really need Emacs so if you are not familiar with the editor I would recommend the former.
- why-el 11y agoCan you elaborate further on the efforts needed to close up the mismatch? Perhaps something concrete to work on today? ;)
- Guthur 11y agoThe immediate mismatch is the alien nature of the parenthesis delimited s-expressions. My advice is that if you find yourself editing text as opposed to the structure of the s-exp or balancing parenthesis manually you are doing it wrong; Emacs has modes like paredit and smartparens to do it. The next "culture shock", though I think this has lessened now due to other languages catching up, is the concept of closures, functions as values, and higher order functions. Lisps also tend to be dynamically type so if that is not familiar to you then it will take some getting used to. There are other high level concepts such has syntax abstractions (macros) but that can wait. And Common Lisp has CLOS which is a different take, compared to the likes of C++ and Java, on Object Oriented programming. As for what to do first; I am not really sure, depends on whether it's Racket or Common Lisp and a lot on what interests you. If you like doing small algorithmic problems such as the Euler Project then start there. For Common Lisp there is Practical Common Lisp which is always a good primer. http://www.gigamonkeys.com/book/ http://www.gigamonkeys.com/book/ And Learn Lisp the Hard Way (I am not familiar with it though) http://learnlispthehardway.org/ http://learnlispthehardway.org/ For a Common Lisp implementation I would recommend SBCL if on Linux (your package manager should have it) and CCL on Windows or MacOS. SBCL: http://www.sbcl.org/ http://www.sbcl.org/ CCL: http://ccl.clozure.com/ http://ccl.clozure.com/ Also use quicklisp for grabbing Common Lisp projects, it's alot easier than doing it manually. https://www.quicklisp.org/beta/ https://www.quicklisp.org/beta/ This might also be useful: http://eudoxia.me/article/common-lisp-sotu-2015/#specific-problems http://eudoxia.me/article/common-lisp-sotu-2015/#specific-pr... Someone else will have to give info on the Racket ecosystem I am not familiar with that.
- alexdowad 11y agoI don't care about whether Steve's "score" is 50% or 70% or 80% or something else. The fact that he was able to come up with these 10 predictions back in 2004 shows he has a whole lot of vision. Steve, what are your next 10 predictions? Obviously, you're at least 10 years ahead of me...