fogus

72 ms·

751.
OCaml for the Masses(queue.acm.org)
120 points by fogus 15y ago|46 comments
752.
Turing completeness bullshit(shebang.ws)
65 points by fogus 15y ago|44 comments
753.
Merge recursive strategy(codicesoftware.blogspot.com)
2 points by fogus 15y ago|0 comments
754.
An introduction to Objective-C(thinkvitamin.com)
43 points by fogus 15y ago|12 comments
755.
Python on a microcontroller(hackaday.com)
8 points by fogus 15y ago|0 comments
756.
Dangling Else, Yet Again(drdobbs.com)
2 points by fogus 15y ago|0 comments
757.
Scraping web data with R(moderntoolmaking.blogspot.com)
1 points by fogus 15y ago|0 comments
758.
Thoughts on Immutability in D(poita.org)
17 points by fogus 15y ago|3 comments
759.
Extreme Negative Code Documentation(1729.com)
7 points by fogus 15y ago|1 comments
760.
Why is Health Care So Expensive?(blog.sethroberts.net)
6 points by fogus 15y ago|5 comments
761.
Raytracing Myths(c0de517e.blogspot.com)
43 points by fogus 15y ago|9 comments
762.
Git Reference(gitref.org)
142 points by fogus 15y ago|11 comments
763.
Inside the entitlement generation(theglobeandmail.com)
3 points by fogus 15y ago|0 comments
764.
Corporate blogging silos(scripting.com)
1 points by fogus 15y ago|0 comments
765.
Compound complexity(johndcook.com)
3 points by fogus 15y ago|0 comments
766.
Structure of emacs text(tehom-blog.blogspot.com)
1 points by fogus 15y ago|0 comments
767.
by fogus 15y ago
but spend your time reading code, not paper. These things are not mutually exclusive. I agree that you should definitely read code also; good and bad. However, this is a post about one specific thing: great papers. Admonit
768.
by fogus 15y ago
Sorry. My Markdown syntax was bad. There are now links to the articles marked by ↗.
769.
What is this thing you call a "type"?(blogs.msdn.com)
2 points by fogus 15y ago|0 comments
770.
Common Lisp loop macro source (CLisp and SBCL)(viewista.com)
2 points by fogus 15y ago|0 comments
771.
by fogus 15y ago
see what node.js is doing Granted, Node.js is nice and all, but it's hardly innovative. It's built on an old language using ancient async tricks running on a VM built using old performance techniques learned during the developmen
772.
by fogus 15y ago
Tons: https://github.com/jashkenas/coffee-script/wiki/List-of-lang...
773.
by fogus 15y ago
One further point of complication is that they also share the amazing Chris Houser who was the primary programmer on the previous and a key contributor on the new.
774.
Java 7: The Top 8 Features(jaxenter.com)
3 points by fogus 15y ago|0 comments
775.
by fogus 15y ago
due to some OO reason or other Overloading would be that reason.
776.
Making C# More Functional(kodefuguru.com)
2 points by fogus 15y ago|0 comments
777.
by fogus 15y ago
calling many people idiots Yikes! Did I say that? I have to say that this is a very black-or-white reading of the post. However, I apologize if I hurt feelings because I know some brilliant Java programmers and likewise brillia
778.
by fogus 15y ago
better than another? Where did I say that? This post was about complexity curves observed during my experience. I can say I like Scala better than Java, but I wouldn't assert that is indicative of anything that you should believ
779.
Side Effects and Functional Programming(stephanboyer.com)
2 points by fogus 15y ago|0 comments
780.
Why Developers Never Use State Machines(skorks.com)
237 points by fogus 15y ago|92 comments

More ›