flavio81

27 ms·

91.
by flavio81 7y ago
>C has not evolved Well, it has, in a way: see the latest C standard and compare it with the Kerninghan&Ritchie edition.
92.
by flavio81 7y ago
>The language hasn't evolved for the same reason a transistor hasn't evolved: because it didn't need to. That's what you think. Transistors have evolved a lot, as have programming languages.
93.
by flavio81 7y ago
>One of the design criteria for Go was to push programmers away from being architecture astronauts whose abstraction heavy style results in having no idea how much work you are hiding in all of the layers. So they chose to create a langu
94.
by flavio81 7y ago
>but Go definitely reflects its time, the 2000s more like the 60s, with a primitive type system, no metaprogramming, no interactive development, etc.
95.
by flavio81 7y ago
>Yet UNIX pipes are strings and amazingly popular. It is still outdated design, right from the 60s. Already in the 70s we had better, interchangeable data structures, like s-expressions for example.
96.
by flavio81 7y ago
>Lispers need to stop thinking that they are the only ones who can do "macros" and "DSLs". The evidence is clearly on the contrarian side. We know that one can do "macros" in many other languages including o
97.
by flavio81 7y ago
>turn spheres inside out with no tearing during execution. Magic. What does "turn spheres inside out" mean? >with no tearing Is this painful?
98.
by flavio81 7y ago
> a fine pragmatic hybrid language which perfectly combined FP and OOP Ah, so Common Lisp then?
99.
by flavio81 7y ago
Hi _bxg1, Cycorp? Do you need more Lisp developers? I'm trying to switch jobs.
100.
by flavio81 7y ago
>I'm not sure there's really much of anything that it owes to C. Rust's default behavior of ignoring integer overflows when not in debug mode -to put an example-, put it very close to C.
101.
by flavio81 7y ago
>SBCL beats CPython by a country mile in every performance comparison I’ve seen. This. Lisp at least 10x faster in the worst case; it can be made to run even faster...
102.
by flavio81 7y ago
>Do Common Lisp implementations have a "core" that multiple inheritance and multiple dispatch can be desugared to? Yes, that's the Meta Object Protocol. It isn't on the standard, yet most Lisp implementation have it,
103.
by flavio81 7y ago
Sadly, there hasn't been too much progress in the last 20 years -- the best are still the Lisp variants (Common Lisp, Scheme, Racket, Clojure) and the ML variants (Standard ML, OCaml, F#, Haskell). You get ultimate flexibility and mall
104.
by flavio81 7y ago
>as the desperate need to get something safer than C/C++ without compromising performance and interoperability Object Pascal D ATS Common Lisp Ada even Fortran!! the list can go on and on
105.
by flavio81 7y ago
> I thought most of the "modernization" in lisp was done in descendant languages One core feature of any Lisp dialect is that you can extend the language using Lisp. Thus, you don't need to "change" the language
106.
by flavio81 7y ago
>Nobody builds anything important with it The core of grammarly, a major, popular product today, is a Common Lisp program.
107.
by flavio81 7y ago
>there are a number of implementations with none of them gaining a majority share SBCL has the majority share. But it doesn't matter, since ANSI Common Lisp is a standard and my code runs on many CL implementations with no changes.
108.
by flavio81 7y ago
>Lisp has a so called "no turning back point", true lispers cannot bear other dialects after experiencing it. I can relate to that feeling.
109.
by flavio81 7y ago
>I can't imagine anyone has ever tried to do engineering at scale (people wise) and did not find the value in static typing. >why so few large projects have been written in a LISP or LISP descendant The major dialect of Lisp, Com
110.
by flavio81 7y ago
>Not even MIT teaches lisp anymore. That's their loss.
111.
by flavio81 7y ago
The easiest to read codebases I've found were all written in Common Lisp, like the clsql lib for example.
112.
by flavio81 7y ago
>I'm working on a language with a focus on simplicity and "only one way to do it": If I wanted a language with "only one way to do it", i'd use Brainfuck. Which, btw, is very easy to learn, well documented,
113.
by flavio81 7y ago
>but this doesnt mean it is a typed language Custom data types can be defined Data types can be checked, Functions can be dispatched on the data type of the input parameters (see CLOS), Variable types can be declared. ... so, Lisp isn&#x
114.
by flavio81 7y ago
>What can you do in a few lines of Lisp that can't be done similarly in Python or Javascript? To pick just an example: Anybody can create a Brainfuck (programming language) interpreter in a few lines of Python or Js code. With Commo
115.
by flavio81 7y ago
>But even this article doesn't get the problem. It's not "there are too many parens" but more that everything in LISP looks the same when you're new, it's a jumble of parens. Your brain isn't getting di
116.
by flavio81 7y ago
> But Lisp is just a big pile of cleverness. That is an opinion that is not grounded on actual usage. In practice we have many libraries that have a source code that is very easy to understand, no doubt thanks to Lisp expressive power.
117.
by flavio81 7y ago
>This works, but it's a plist and thus O[n] for lookup. I assumed the questioner wanted an O[1] data structure; thus a hash table is the better answer. (Granted it makes little difference when n is small.) There was a test on some C
118.
by flavio81 7y ago
>AFAIK, CCL is dying now CCL is the 2nd most downloaded Lisp implementation, so it can't be called "dying." You'll find that new lisp projects are almost invariably tested on CCL too.
119.
by flavio81 7y ago
>there hasn't been a free/cheap compiler and IDE for a PC for a very long time One of the first Common Lisp implementations (80s), Kyoto Common Lisp (KCL), was also free. One of the highest performing Common Lisp implementation
120.
by flavio81 7y ago
* typo: ClojureScript is a subset It is also a success, on the other hand. It's a good alternative to Javascript. We also have a subset of Common Lisp that can be statically compiled to javascript: Parenscript. And a subset of CL tha

More ›