Viewing profile — flavio81

>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 wi…

>No multithreading, I/O locks under GNUs/eww, glacial slow All this would not happen if RMS had chosen Common Lisp to implement it...

>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 b…

>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 developm…

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 yo…

>I want C++ do exactly and only what the programmer specifies Good luck with that.

Add Common Lisp to the list. And even Scala has fast compile times today.

>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 h…

>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

Exactly. A post full of bollocks.

>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 com…

Correct. The Unix philosophy is based on hagiography.

>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…

>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 Spectru…

So, you think productivity or even quality can be measured in "amount of lines of code produced". Which is completely wrong.

100% based. Indeed this is one of the hard problems for a manager.

+1, it is my go-to language whenever I have no idea how complex the task will get

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, app…

>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?

>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 withou…

>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…

> 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…

> 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 …

>Otherwise, Clojure is an excellent language which both modernises Lisp syntax significantly and implements a very well thought out standard library for doing functional programmin…

>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 Clojur…