HNHacker News
TopNewBestAskShowJobs

flavio81

2,368 karma · joined May 18, 2017

"Informatics" engineer (a combination of SE + CE + CS).
submissionscomments
flavio81··on My experience with NixOS
RMS dislike of CL was purely due to personal factors: He felt cheated by the Lisp machine industry.
flavio81··on Ask HN: What is the best way to learn Lisp in 2020?
> There's even a show_expr method that prints it as an S-expression.

Yes.

However, the 99.9999% of Julia code out there isn't in s-expressions. Every Julia programmer doesn't use s-expressions. They use Julia syntax.

Thus, the task of writing Macros in Julia is harder than doing the same thing in Lisp.

>So I'm seeing nothing that would be problematic if it had just gone with a Lisp syntax.

They should've gone with a Lisp syntax, IMO. Beginners, who haven't passed through the chore of learning C-like syntax, find s-expressions as easy as any other kind of syntax.

flavio81··on Ask HN: What is the best way to learn Lisp in 2020?
Python doesn't really have anonymous functions (unless they are 1-line functions, which, in python, means they can't do much.)

This pretty much disqualifies it as a functional programming language.

Additionally, Guido and the community in general discourage functional programming. While the Common Lisp community already has a lot of libraries for FP, like FSET and others.

flavio81··on Ask HN: What is the best way to learn Lisp in 2020?
>Common lisp by comparison, feels arcane, outdated and non lispy.

Only if your knowledge of Common Lisp is at the level of "armchair specialist".

flavio81··on Ask HN: What is the best way to learn Lisp in 2020?
>Yeah and the original cons cells had proper equality defined on them, which common lisp doesn't have.

Substantiate your claims.

flavio81··on Ask HN: What is the best way to learn Lisp in 2020?
> Clojure is much closer to math

I didn't know that having leaky abstractions on top of the horrible Java standard lib was "being closer to math"

flavio81··on Lisp Comes of Age (1980)
>those written in Python just seem much nicer

>The AIMA/PAIP code in Common Lisp, for instance, are ugly as hell

perhaps it just means you are familiar with python, not lisp.

I have 3 years of experience with both and let me tell you, there is nothing elegant in Python: there's nothing elegant in having to deal with one-line lambdas, global interpreter lock, 30x-50x longer execution times than Lisp, distinction between statements vs expressions, mutability everywhere, a flaccid OOP system, no interactive development features, and horribly written libraries.

flavio81··on Lisp Comes of Age (1980)
>Lisp-2 is typically Common Lisp.

However Common Lisp is a lisp-n, it has at least 5 namespaces: functions, symbols, keywords, classes, signals, packages...

flavio81··on Lisp Comes of Age (1980)
>The problem with "you can roll your own language constructs" is that, er, everybody wants to roll their own language constructs

What are methods and classes in a language like Java? Those are "roll your own constructs" as well.

In lisp code you can define your own functions and macros, yet the end still looks like lisp code.

flavio81··on Lisp Comes of Age (1980)
This. Well said.
flavio81··on Lisp Comes of Age (1980)
>I wouldn't say it's a broken idea. It's just an idea that doesn't scale. Working in a dynamic codebase - especially a Lisp one - basically means you have to be familiar with how everything you're using works.

That's FUD. Just make your code modular. Lisp gives you tools: namespaces, and systems.

>You can at least count on functions not having side-effects.

The great majority of functions in Lisp don't mutate data.

flavio81··on Lisp Comes of Age (1980)
>and a lack of any compile time checking is what keeps me from even bothering to look at it.

Common Lisp more than compensates due to some key features:

1. any bug can be corrected at runtime without having to stop the program

2. the type system is completely strong, not weak

3. it actually has a pretty nice type system.

4. the conditions-restart exception handling system is world-class

flavio81··on Time safety is more important than memory safety
Last time I checked, Pascal has generics and exception handling.
flavio81··on Why Discord is switching from Go to Rust
>Go is what would have happened if Bell Labs wrote Java

And Unix is what happened when Bell Labs wrote an operating system -- something that was born outdated from the start.

Just like Golang.

flavio81··on Femtolisp: A lightweight, robust, scheme-like Lisp implementation
>Any examples?

Common Lisp has been used in scientific computing since decades, so in some sense it's "ready". Also, see CLASP: lisp at the state of the art of computational chemistry.

flavio81··on Femtolisp: A lightweight, robust, scheme-like Lisp implementation
>the main difference between those Lisp based languages and Julia in terms of attracting people is the syntax

Yes, and this is practically the only thing that I find wrong with Julia, besides the lack of the interactivity of CL.

It's like populism -- an inferior syntax choice taken just to attract the Pythonistas.

flavio81··on Lisping at JPL (2002)
You're doing God's work, Ron.
flavio81··on Lisping at JPL (2002)
>Leave out one parenthesis and...you miss Venus?

You won't, since Lisp editors automatically keep parentheses balanced.

flavio81··on Lisping at JPL (2002)
>But everyone writes their own DSL on top of the language because the language is simple

This is a myth perpetuated by people with zero lisp experience.

I've navigated plenty of lisp libraries' codebases and haven't found not a single case of that.

>I've heard this called "the curse of Lisp

An essay written by... a graphic designer with zero Lisp experience.

flavio81··on Lisping at JPL (2002)
>Do you use Lisp at your workplace?

I do.

flavio81··on Lisping at JPL (2002)
Already in the early 80s, Lisp was used to program massively parallel supercomputers.

Lisp stopped being slow a long, long time ago.

flavio81··on Lisping at JPL (2002)
>Not to be pedantic, but since Clojure is a hosted JVM language (as one of a few platforms it's hosted on) and has full interoperability with Java,

Armed Bear Common Lisp is an ANSI Common Lisp, thus can use all CL libs, runs on the JVM, and it can easily call Java libraries. In fact as easy as calling regular lisp functions.

flavio81··on Lisping at JPL (2002)
HP's "RPL" language, Reverse Polish Lisp, was basically that.
flavio81··on Lisping at JPL (2002)
>LISP won't get you anywhere in that sense. Sure you may learn some programming concepts, but the ROI is not worth it.

Do you want your kid to learn actual computer science, or do you want him/her to basically be able to create a cookie cutter mobile app?

flavio81··on Lisping at JPL (2002)
>Pretty sure Logo was originally implemented with a lisp, no?

Logo is a bare-bones Lisp disguised as an educational language.

flavio81··on Lisping at JPL (2002)
>I think there are a lot of great uses of the patterns that come out of s-expressions, for example, but I would still choose Go, Python or JS / TypeScript as my daily driver.

There's no God.

flavio81··on Lisping at JPL (2002)
>I always got a rush from solving problems in LISP but then realized I could much more easily solve the problem in an imperative language

I've good news for you: Lisp is an imperative language.

http://www.gigamonkeys.com/book/loop-for-black-belts.html

flavio81··on Why we’re writing machine learning infrastructure in Go, not Python
Anything is faster than CPython. Even PHP!
flavio81··on Why we’re writing machine learning infrastructure in Go, not Python
>Go is small and conceptually simple, but its ideas and philosophy are pretty different from most mainstream languages.

No, they aren't. They are the same as languages from 40 years ago: We have had channels, coroutines, and good garbage collectors from long, long ago. Plus the syntax is directly borrowed from Algol 68 (from 1968).

Go looks nice because it fills a niche (a high performance garbage collected language that is easier to learn than Java and provides faster compilation times than C++), but there's absolutely nothing different here.

For "pretty different from mainstream" see Forth, Prolog, Erlang, etc.

flavio81··on Why we’re writing machine learning infrastructure in Go, not Python
>If you value simplicity check out the programming language zig.

I value simplicity, that's what i use Brainfuck. Far simpler than Go and Zig.

https://fatiherikli.github.io/brainfuck-visualizer/

← PreviousPage 3 of 34Next →