vseloved

10 ms·

61.
by vseloved 13y ago
I'm also teaching an OS class, and IMHO using some new shiny thing is not the right way to approach it, because the students will be put in an ideal imaginary world, and neither will face the real-world practice, nor understand how it
62.
by vseloved 13y ago
The better name would be Wolfram standard library
63.
Videos from European Common Lisp Meeting 2013 (1st part)(youtube.com)
4 points by vseloved 13y ago|0 comments
64.
by vseloved 13y ago
http://grammarly.com
65.
by vseloved 13y ago
looks just like (funcall #'funcall ... ;)
66.
by vseloved 13y ago
Lisp-2 is much saner. What it adds is just funcall, and it's not such a big deal in practice, because most of the times in the situations of higher-order function you would use apply, reduce or map, which likewise should be used in Lis
67.
Livecoding in Common Lisp(youtube.com)
1 points by vseloved 13y ago|0 comments
68.
GTK3+ Tutorial for Lisp(crategus.com)
4 points by vseloved 13y ago|1 comments
69.
Lisp Hackers: Marc Battyani(lisp-univ-etc.blogspot.com)
6 points by vseloved 13y ago|0 comments
70.
by vseloved 14y ago
Currently, I develop in Clozure and SBCL alongside, and it's true that SBCL compilation speed (and memory consumption) can be prohibitive at times, but in return it may give up to 3-4 times execution speed increase. So it's a real trade-off
71.
Lisp Hackers: Vladimir Sedach(lisp-univ-etc.blogspot.com)
100 points by vseloved 14y ago|26 comments
72.
by vseloved 14y ago
I don't think, that the question "Which Lisp should I use: Clojure or Common Lisp?" is quite correct. As they are really so different in very basic concepts: mutable vs immutable, OO vs non-OO, bootstrapped vs JVM-based, and the list can go
73.
by vseloved 14y ago
The question should you program in Emacs Lisp or Common Lisp is meaningless. If you program for Emacs, you use Emacs Lisp, otherwise — Common Lisp. It would be very hard for you to do it the other way. I, actually, wonder how much knowledge
74.
by vseloved 14y ago
I would agree with you, if the notion of Lisp was actually well-understood. But, unfortunately, I observe the contrary very often. That's exactly why I've wrote this rant. For example, just a day ago in the previous Lisp discussion on HN (
75.
by vseloved 14y ago
Here's a more detailed answer: http://lisp-univ-etc.blogspot.com/2013/01/common-lisp-is-jus... I also agree, that Racket is not Scheme, it's a new language. But I stand, that Common Lisp is still a Lisp. Lisp 1.5 would be BCPL or B :) (Wh
76.
Common Lisp is just Lisp(lisp-univ-etc.blogspot.com)
3 points by vseloved 14y ago|8 comments
77.
by vseloved 14y ago
Let's translate it to C: C99 is C. C++0x is C++. C++ is C. Clang is C99. Do all the lines seem correct?
78.
by vseloved 14y ago
There are more reasons to use Lisp actually: the biggest one of which is, probably, that many programs become much simpler in it. But, actually, such argument is meaningless. The only meaningful argument would be to compare the pros and con
79.
by vseloved 14y ago
Common Lisp. Everything else is so much Lisp as php is perl or C++ is C.
80.
by vseloved 14y ago
Well, Common Lisp is Lisp, Racket is Scheme, they are different. This perpetual confusion is just useless. Let's call things by their names. You don't call C++ C or php perl, right?
81.
Lisp Hackers: John Fremlin(lisp-univ-etc.blogspot.com)
5 points by vseloved 14y ago|0 comments
82.
by vseloved 14y ago
Gosh, if you had an extensible reader, you could do so much more... Oh wait, why don't we try it: http://lisp-univ-etc.blogspot.com/2013/01/real-list-comprehe... ;)
83.
by vseloved 14y ago
Actually, here Haskell is just like any other language: i.e. you can use the described properties to define similar operations in any language. It's not Haskell, that allows to define them, but the abstract properties of this class of objec
84.
by vseloved 14y ago
One more essential meatspace activity is knowledge transfer. It may not be the most productive thing to sit with someone at a computer and show them, how you do certain stuff, discussing different issues, that arise in the process - but def
85.
by vseloved 14y ago
then, here's an old classic for you: https://groups.google.com/forum/?fromgroups#!msg/comp.lang.l... ;)
86.
Lisp Hackers: Faré Rideau on Lisp, cybernetics, ITA and Google(lisp-univ-etc.blogspot.com)
2 points by vseloved 14y ago|0 comments
87.
by vseloved 14y ago
Finally, someone has the guts to say, that failed logins should tell the user, what is wrong: username or password
88.
Lisp Hackers: Luke Gorrie's interview and video
3 points by vseloved 14y ago|0 comments
89.
Lisp Hackers: Juan José García Ripoll(lisp-univ-etc.blogspot.com)
1 points by vseloved 14y ago|0 comments
90.
Lisp Hackers: Christophe Rhodes(lisp-univ-etc.blogspot.com)
5 points by vseloved 15y ago|0 comments

More ›