fogus

79 ms·

811.
The future of Lisp(blog.8thlight.com)
64 points by fogus 15y ago|49 comments
812.
Collapsing Communities(prog21.dadgum.com)
2 points by fogus 15y ago|0 comments
813.
Interesting first-person account of making core memory(groups.yahoo.com)
2 points by fogus 15y ago|0 comments
814.
Logic programming on the JVM and Javascript(is-research.de)
3 points by fogus 15y ago|1 comments
815.
Functional programming trivia(blog.yuvimasory.com)
2 points by fogus 15y ago|0 comments
816.
Ask HN: Why punish popularity?
26 points by fogus 15y ago|4 comments
817.
Teaching strategies that work - but for what?(washingtonpost.com)
1 points by fogus 15y ago|0 comments
818.
Happy 30th birthday IBM Personal Computer(www-03.ibm.com)
1 points by fogus 15y ago|0 comments
819.
by fogus 15y ago
There's nothing to it but to do it. Seriously, there are many developers who have lives, kids, sick relatives, etc. who are able to accomplish the equivalent of this list and more. It will take a very long time to get through this list, bu
820.
America's Geekiest Cities(realestate.yahoo.com)
1 points by fogus 15y ago|0 comments
821.
How to Level Up as a Developer(jasonrudolph.com)
386 points by fogus 15y ago|109 comments
822.
MonaOS: the OO hobby OS with a GUI, Scheme, browser, and more(monaos.org)
59 points by fogus 15y ago|11 comments
823.
Revolutions That Weren’t(dadhacker.com)
3 points by fogus 15y ago|0 comments
824.
by fogus 15y ago
I'd tend to give Turing-completeness a bit more credit where it's due Turing completeness is a fun topic for conversation, but it doesn't stand up to practical application. That is, every language has a point of diminishing
825.
What’s Wrong with Learning Haskell(willowbend.cx)
17 points by fogus 15y ago|2 comments
826.
Functional thinking: Immutability(ibm.com)
1 points by fogus 15y ago|0 comments
827.
Five reasons why you should rejoice about Kotlin(beust.com)
1 points by fogus 15y ago|0 comments
828.
Software exoskeletons(johndcook.com)
9 points by fogus 15y ago|0 comments
829.
by fogus 15y ago
What would you expect to be different? Your post says the important point: it's Clojure. For some an additonal point is that it's not JavaScript. There is nothing deeper than that.
830.
by fogus 15y ago
possible with the above alternatives and Armed Bear Common Lisp? Yes it is. I wish being possible was all that it took for it to be done. In the absence of ClojureScript I would love to write my web client code in Common Li
831.
by fogus 15y ago
I only mentioned Node because the parent post did, but as for the reason it was chosen for the target of the first round is because it's definitely got the polish as far as libs, installation experience, etc. go.
832.
by fogus 15y ago
Bear in mind that the wording is very careful. We took great pains to say things like "not currently implemented." ;-)
833.
by fogus 15y ago
All of the core syntax is not currently there, but you're right that ClojureScript only interops with js and not Java. For a more detailed differences list see https://github.com/clojure/clojurescript/wiki/Differences-fr...
834.
by fogus 15y ago
Atoms are available now. Agents might come soon. Refs and Vars are questionable.
835.
by fogus 15y ago
Web framework? Do you mean Google Closure? If so, bear in mind that the compilation phase will remove unused code, so you're not forced to carry any of it with you if you never use it in your code. As for Node, you do not need it I suppo
836.
by fogus 15y ago
Node.js is the pragmatic choice for ClojureScript command line apps. One of Clojure's weaknesses was that the JVM was not a great choice for these types of scripts. ClojureScript + Node.js effectively solves this problem.
837.
Beautiful Assembly (LuaJIT)(article.gmane.org)
7 points by fogus 15y ago|2 comments
838.
Beginning Factor – Introduction(elasticdog.com)
2 points by fogus 15y ago|1 comments
839.
OOP in Bash(lab.madscience.nl)
108 points by fogus 15y ago|13 comments
840.
The End of Free Will(dilbert.com)
5 points by fogus 15y ago|0 comments

More ›