``Lisp has too many parens''

Said the js developer as he typed ``})();})($);'' to finish his javashit module. ``So clear!'', he asserted satisfied.

why the fuck do you sage OP?

C syntax is the best

>>2
Why are you so angry about this?

>>1
>>2
>>4
wait I don't even know who's anusing who itt

>>5
if you need to ask, your're are an anus. also, optimize your're are quotes.

[>>n | n=2^^x, x=[0..2]]

>>1
Each of these are different symbols.
Imagine a missing parens in "((((((((_))(((#((^%('())))"

>>8
Thanks to prefix notation this can be cleanly solved with an IDE.
Hover over the content of a paren and it highlights the area of it.
I think all Lisp IDEs have this.

>>9
Do you have to hover over 200+ parens each time you open a file with 100+ expressions?

>>9
Just keep typing ) until the outermost paren is highlighted. This is not possible in the js case.

>>11
no, in the js case you'd type } until outermost one is highlighted

>>12
Js, and other ()-languages, requires multiple closing symbols.

>>11,12,13
False, you can early return/goto without braces. Here is example from my slither "AI"
function food(){
if(!foodsearch)return;
if(!unsafeWindow.snake)return;
if(!unsafeWindow.foods)return;
if(unsafeWindow.foods.length<2)return;
var snakeid="s"+unsafeWindow.snake.id;

// var i=(Math.random()*unsafeWindow.foods.length)|0;
/// if(!unsafeWindow.foods[i])return;


var i,best,best,bestdist=1e12,curdist,found=false;
var sn1=unsafeWindow.os[snakeid].xx,sn2=unsafeWindow.os[snakeid].yy,fn1,fn2;

for(i=0;i<unsafeWindow.foods.length;i++){

if(!unsafeWindow.foods[i])continue;
// document.title="HAS_CHANCK"
if(unsafeWindow.foods[i].eaten)continue;
// document.title="HASFOOD"
fn1= unsafeWindow.foods[i].xx;
fn2=unsafeWindow.foods[i].yy;

curdist=dist(sn1,sn2,fn1,fn2);
if(curdist>max_feed_dist){;continue;}

//document.title=curdist
if(curdist<bestdist){bestdist=curdist;best=i;found=true;}
}
//document.title="foodFound"+unsafeWindow.foods[best].xx+":"+unsafeWindow.foods[best].yy;
//var angle= unsafeWindow.foods[best].gfw2;
var xbonus=sn1>fn1?-feed_approach:feed_approach;
var ybonus=sn2>fn2?-feed_approach:feed_approach;
if(!found){forcerandsnake();return;}


document.title="Found:"+best;
unsafeWindow.os[snakeid].xx= unsafeWindow.foods[best].xx+xbonus;
unsafeWindow.os[snakeid].yy= unsafeWindow.foods[best].yy+ybonus;

}

>>14
fuck you FrozenAnus

>>15
Why the anger? its even formatted and cleanly separated parts of code.

javascript is a dialect of lisp

The only really popular dialect that doesn't use the "sea of parens" syntax scheme.
I understand that Lisp syntax is a part of what mainstream lisp is(allowing to prefix stack functions/variables ), by C-syntax is more natural and easier to read. It just takes less mental effort to interpret(directly reading C-syntax) while Lisp requires to properly indent and recover the layers of parens into their mental form(which is more C-like, McCarthy used M-expression as goal but Lispers got lazy and pretended programmers are S-expression parsers in exchange of allowing low-level manipulation of lexical tokens inside code.
Lisp is actually lower-level than C in the parsing hierarchy, as C translates to Lisp-like AST in mainstream compilers. Its like Brainfuck with extra levels of abstraction, you only have the lego pieces you're allowed to work with and these pieces don't combine into performant code:

https://philip.greenspun.com/bboard/q-and-a-fetch-msg?msg_id=0006XQ
``Of course, you can't expect Lisp to do something like that; Lisp can't do things like this. If you want to deal with massive data sets, you have to use C. It is sad but true."

Any sufficiently complicated lisp program contains an ad-hoc, informally-specified, bug-ridden, slow implementation of half of every other language

>>19

informally-specified, bug-ridden, slow

But Lisp is generally slow and dynamically typed.

>>19
How do you measure how ``lisp'' a program is?

>>21
By how much it tries to actually be a different language.

Remember when ((())) was a joke about Lisp syntax, not some /pol/ shit?

>>23
(((John McCarthy)))

>>24
McCarthyism -- the ISM stands for Instruction Set Manual

>>23
it'll never go back to being about lisp

>>26
fucking /pol/ infringing our trademarked memes :(

>>27
Thats more of a cultural appropriation