phoe-krk

53 ms·

691.
by phoe-krk 6y ago
Do you have any examples?
692.
Expressing Problems in Their Natural Language [pdf](watrophy.com)
6 points by phoe-krk 6y ago|1 comments
693.
by phoe-krk 6y ago
Preface: What is Lisp, where does it come from, and what is it useful for? This is an expedient account of Lisp by way of real examples geared toward programmers and scientists. The examples showcase real Common Lisp code, and it's no
694.
by phoe-krk 6y ago
I know that many implementations record source location, but the source itself is still on the filesystem, not in memory, therefore making source locations useless if we move the filesystem out of the equation. I also know that many impleme
695.
by phoe-krk 6y ago
> That is, all source code and all objects are stored in memory. Common Lisp usually stores code in form of normal source files that are then possible to load into a clean-slate Lisp image. It's possible to dump images and restore
696.
by phoe-krk 6y ago
I know about Smalltalk, but I didn't know about Java and .NET! Could you point me to utilities for those languages that allowed for features like autocompletions, introspection, live debugging, recompilation, REPLs - standard stuff in
697.
by phoe-krk 6y ago
In theory, a Common Lisp implementation is not required to be image-based. The standard permits a Common Lisp compiler that can e.g. be a batch file compiler that turns files into binaries, and then those can be executed without lots of l
698.
by phoe-krk 6y ago
Swank/Slynk clients are generally preferable to LSP clients when doing Common Lisp. LSP infrastructure in Lisp (notably, the cl-lsp library) is relatively young and not widely used, whereas Slime/Swank is thoroughly battle-tested
699.
by phoe-krk 6y ago
Yes, I use SBCL daily. The fact that SBCL (like most CL implementations) is image-based makes CL the language for interactive and incremental programming and live debugging the program as it runs. (Shameless plug: I wrote a book about the
700.
by phoe-krk 6y ago
https://marketplace.visualstudio.com/items?itemName=rheller....
701.
by phoe-krk 6y ago
https://github.com/sirherrbatka/vellum is maturing and already usable as a data frame library.
702.
by phoe-krk 6y ago
> Fully canonically, :: is 0000:0000:0000:000:0000:0000:0000:0000. Nitpick: missed a single zero in the middle there.
703.
by phoe-krk 6y ago
Minor personal confession, and a minor shameless plug. I really enjoyed the Online Lisp Meeting talks[0] that have happened throughout this year. They show a lot of amazing and recent developments that have been occurring in various parts o
704.
by phoe-krk 6y ago
I can see your point and agree with it: you can connect hardware that speak serial and use it to connect software that speaks VT220. Looking from this point of view, the hardware and software protocols are correctly assigned, everything is
705.
by phoe-krk 6y ago
Yes, sending commands to a device that is not capable of accepting these commands is a bug. Good now? :D
706.
by phoe-krk 6y ago
I'm not saying that it's not a bug - it is, there's no doubt. I'm saying that using antiquated hardware for interfacing with modern systems violates the principle of least astonishment for me.
707.
by phoe-krk 6y ago
Yes, that's another issue that luckily seems to have been fixed in the linked bugticket. Still, using antique hardware for interfacing with modern systems is something that would surprise me if I found it used in the wild. I know that
708.
by phoe-krk 6y ago
Using a real VT220 as a terminal in the 21st century certainly violates the principle of least astonishment. Even backwards compatibility should have its limits.
709.
by phoe-krk 6y ago
From less than three weeks ago, too.
710.
by phoe-krk 6y ago
> It goes beyond kicking someone out of the bar to not allowing someone to open a bar. You can open your bar just fine. Just don't expect someone else to invite people in there for you.
711.
by phoe-krk 6y ago
I must disagree. I see a lot of CAR and CDR calls in code that I see daily. Also, it's a style error to use FIRST and REST when one operates on cons cells, because those imply a different meaning - that one operates on lists. Sure, the
712.
by phoe-krk 6y ago
> Common Lisp's evaluation semantics are a language of it's own practically at this point and are very far removed form most languages. Huh? What do you mean? The separate function namespace? Evaluation rules in CL, strictly sp
713.
by phoe-krk 6y ago
It kinda is. There have been countless debates about Clojure not being a real Lisp, Scheme not being a real Lisp, Janet not being a real Lisp, Lisp not being a real Lisp, and IMO they've only created circle jerks, tons of "my Lisp
714.
by phoe-krk 6y ago
> as in any (real) Lisp While the OP, by "Lisp", means "Common Lisp" - you're aware that following this old meme of "Clojure is not a real Lisp" only causes interpersonal fires and brings no real benefi
715.
by phoe-krk 6y ago
I don't understand the question. Using the same logic, why would a 33 year old C environment still be the high water mark for most practical purposes? Talking about GCC, of course.
716.
by phoe-krk 6y ago
Thanks! I haven't seen elpy before - I'll take a look at it. It seems like exactly the thing I described.
717.
by phoe-krk 6y ago
Thanks! I haven't seen elpy before - I'll take a look at it. It seems like exactly the thing I described.
718.
by phoe-krk 6y ago
Yes, CCL still exists and it still has the Cocoa interface for Mac.
719.
by phoe-krk 6y ago
> What probably Lisp trails in is type inference SBCL type inference is actually getting better and better over time, giving you pretty effective gradual typing. Additionally, a Common Lisp implementation called SICL is in the works, wit
720.
by phoe-krk 6y ago
The alternatives that you mention are still highly subpar when it comes to e.g. the incremental and interactive programming style that is highly common with Lisp. Java fails at it miserably by pretending to be a dynamic language, and I have

More ›