Brainfuck beware: JavaScript is after you (2012)
patriciopalladino.com
Brainfuck beware: JavaScript is after you (2012)
1–10 of 39 posts
Re: Brainfuck beware: JavaScript is after you (2012)
#2Gotta love this language... It's a wonder we can get any work done with it. But, used with discipline, it's not too bad.
Re: Brainfuck beware: JavaScript is after you (2012)
#3Re: Brainfuck beware: JavaScript is after you (2012)
#4Re: Brainfuck beware: JavaScript is after you (2012)
#5Re: Brainfuck beware: JavaScript is after you (2012)
#6Re: Brainfuck beware: JavaScript is after you (2012)
#7What prevents language designers from avoiding all these lurking bugs with a generic type-conversion operator? E.g. here's how it might look in a Python-like language:
>>> x = 1
>>> y = "2"
>>> print(x + cast(y))
3
>>> print(cast(x) + y)
"12"
>>> print(cast(x) + cast(y))
Exception: ambiguous typeRe: Brainfuck beware: JavaScript is after you (2012)
#8Re: Brainfuck beware: JavaScript is after you (2012)
#9I am not a programmer so this is part curiosity and part criticism. Why do programmers seem to enjoy creating programs that satisfy some syntactical constraint? Is it a fun mental exercise, or or can you just admit that you're showing off on something that really does not matter?
Re: Brainfuck beware: JavaScript is after you (2012)
#10I am not a programmer so this is part curiosity and part criticism. Why do programmers seem to enjoy creating programs that satisfy some syntactical constraint? Is it a fun mental exercise, or or can you just admit that you're showing off on something that really does not matter?