flavio81

7 ms·

1.
by flavio81 9mo ago
>Coalton strives to implement Haskell or ML-adjacent semantics (in the type system, for example) with Lisp syntax. "With" here meaning that it is both implemented in and written with Lisp syntax. Not exactly. Coalton brings ML-
2.
by flavio81 1y ago
>No multithreading, I/O locks under GNUs/eww, glacial slow All this would not happen if RMS had chosen Common Lisp to implement it...
3.
by flavio81 1y ago
>It’s really interesting reading about LISP machines but no-one’s building a new one There have been two open source Lisp Machine OS created in the last 15 or 10 years. However a big part of the power of the Symbolics/LMI machines w
4.
by flavio81 1y ago
>SmallJS is file based, not image based, so you can develop in your favorite IDE This project is nice, however if we don't have a specific, client-side IDE for interactive development, 70% of the power of Smalltalk is gone (one of t
5.
by flavio81 1y ago
One could easily implement an Emacs (SLIME) plugin to "macroexpand" the (pseudo) expresion to real (concrete) Lisp code, and even to try again until the implementation satisfies you. Then it becomes a concrete Lisp implementation
6.
by flavio81 1y ago
>I want C++ do exactly and only what the programmer specifies Good luck with that.
7.
by flavio81 1y ago
Add Common Lisp to the list. And even Scala has fast compile times today.
8.
by flavio81 1y ago
>Lisp killer features were GC, good data representation, first class functions. Lisp's killer feature is procedural macros that are extremely easy to write and debug. Lua doesn't have such a thing, that's why Fennel was cr
9.
by flavio81 1y ago
>To whoever down-voted me, please do explain how HMRs are comparable to Erlang's true hot code swapping or even Lisp's live redefinition. based
10.
by flavio81 1y ago
Exactly. A post full of bollocks.
11.
by flavio81 1y ago
>As one of the authors of the Unix Haters Handbook One day, one remote day, mankind will attain Reason and will award you a Nobel Prize for speaking out loud against retrograde computing. I salute you, hero, veteran.
12.
by flavio81 1y ago
Correct. The Unix philosophy is based on hagiography.
13.
by flavio81 2y ago
>Easy to prove, can you think of an engineer that adds negative value? Yes, i have many examples. Two of them I personally fired. One of them, I should have fired much early. I let this engineer basically add negative value by trying to
14.
by flavio81 2y ago
>When did IEEE become host to clickbait nonsense? This whole take feels like an editorial by a junior engineer going off vibes. Exactly. I think i'll never click on an IEEE Spectrum article again. IEEE has jumped the shark.
15.
by flavio81 2y ago
So, you think productivity or even quality can be measured in "amount of lines of code produced". Which is completely wrong.
16.
by flavio81 2y ago
100% based. Indeed this is one of the hard problems for a manager.
17.
by flavio81 2y ago
+1, it is my go-to language whenever I have no idea how complex the task will get
18.
by flavio81 2y ago
You´d be surprised. In the 1980s, complete workstations were written in Lisp down to the lowest level code. With garbage collection of course. Operating system written in Lisp, application software written in Lisp, etc. Symbolics Lisp Machi
19.
by flavio81 2y ago
>The concept of compile-time programming having the same appearance as runtime programming is very cool in my opinion. You mean, something that Lisp does since the early 1980s?
20.
by flavio81 2y ago
>That means that a field called "date" can be either a string, integer days since the epoch or a Java Date, and (because this codebase isn't great) there's no way of knowing without tracing the call stack. But this is
21.
by flavio81 2y ago
>How did they adapt to dynamic types? You mean dynamic typing, I understand. Clojure (and Common Lisp) is strongly typed, so if you expect type A and you give a value of type B, an error will be raised. On Common Lisp, which is an intera
22.
by flavio81 2y ago
> runs on the JVM, access to any Java or Python library within Clojure without wrappers If you already like Common Lisp, ABCL (Armed Bear Common Lisp) is a mature fully ANSI Common Lisp-compliant implementation, that runs on the JVM and
23.
by flavio81 6y ago
> Clojure uses Leiningen which runs on top of Maven to automatically retrieve libraries, it works very well. In the same way, Common Lisp uses Quicklisp, which runs on top of ASDF to automatically retrieve and compile libraries. It works
24.
by flavio81 6y ago
>Otherwise, Clojure is an excellent language which both modernises Lisp syntax significantly and implements a very well thought out standard library for doing functional programming. There are many great features, but the standout ones a
25.
by flavio81 6y ago
>I do this all the time with Clojure at work. I will have my application running (web app) with two repls in emacs. One is connected to the ClojureScript repl and one to the Clojure repl. I am able to make changes to both front end code
26.
by flavio81 6y ago
See my reply above: https://news.ycombinator.com/item?id=25451321
27.
by flavio81 6y ago
See my reply: https://news.ycombinator.com/item?id=25451321
28.
by flavio81 6y ago
What i'm talking is about the following: - Able to easily modify (and recompile) a function while your code is running - Able to redefine a class and then change existing instances so they use the new class definition - Able to sabe th
29.
by flavio81 6y ago
Yes, "Why do you want to learn Lisp?" is a good question. If the author wants to use Lisp because he/she thinks metaprogramming is interesting, or has read about the benefits of interactive programming, Common Lisp is the ch
30.
by flavio81 6y ago
Yes, "Why do you want to learn Lisp?" is a good question. If the author wants to use Lisp because he/she thinks metaprogramming is interesting, or has read about interact

More ›