Why don't these x100 programmers who proclaim x100 productivity of LISP/Scheme rewrite some open source project in LISP/Scheme and make it better? Shouldn't it demonstrate how superior LISP is?
rewrites are generally not very productive. also, modern meme is 'rewrite it in Rust' because 'it will be secure and bug-free' (which is largely bullshit)
Name:
Anonymous2019-10-29 15:38
LISP makes you a more productive at writing code but that's not what programming is anymore. Modern programming is putting together different packages and libraries and build systems like lego blocks. LISP doesn't help with this--it only makes you more productive if you have to write everything alone like you had to do in the 90s.
Name:
Anonymous2019-10-29 17:36
>>4 Isn't LISP all about creating and manipulating LEGO blocks?
Name:
Anonymous2019-10-30 1:58
>>5 LOGO is all about creating and manipulating turtles all the way down.
Name:
Anonymous2019-10-30 2:44
>>5 Yes, but only ones you made yourself. LISPers are too egotistical to use other people's work, so they gradually went extinct.
Name:
Anonymous2019-10-30 10:30
>>7 Why not create a wrapper or something like macro interface that generates bindings on the fly?
Name:
Anonymous2019-10-30 10:33
>>8 Some languages have tools that converts C headers into native bindings. I think some even handle C++(like Rust https://karroffel.gitlab.io/post/2019-05-15-rust/ ) at macro level(which should be even easier in LISP).
Name:
Anonymous2019-10-30 10:35
The cpp crate allows you to embed C++ code inside of Rust code using the ´cpp!´ macro. It does this by taking all the in-line C++ code and writing it into a separate .cpp file which will be compiled into the resulting object code of the Rust crate.
cbindgen and cpp complement each other nicely. cbindgen can be used to make your data types accessible and the cpp crate makes it easy to create binding functions which use those types.
>>8-10 As usual, the only reason this doesn't exist is because no one took the time to do it. If you think there's enough usefulness left in dusty ol' Lisp, then do it.