curi

31 ms·

301.
by curi 19y ago
A theory can be verified by a mass of facts, but it becomes a proven theory, not a fact. This is a ridiculously bad description of how science and fallibility work.
302.
by curi 19y ago
lol. did you read them?
303.
by curi 19y ago
How come people who want a high signal to noise ratio, downmod a short, helpful comment which lets someone know not write "thanks" 6 times? In other words, I was asking someone to improve the signal to noise ratio. As far as getting downmod
304.
by curi 19y ago
This is interesting. No one gives any reason I'm wrong about what I said. I don't quite see the purpose of downmodding a post that's already on the bottom and greyed out. But I guess no one is going to explain their reasons.
305.
by curi 19y ago
Wow. <3
306.
by curi 19y ago
You don't have to say "thanks" 6 times.
307.
by curi 19y ago
I think you may have mixed people up, I've been arguing against infix, so I'm not continuing to ignore that ;p I believe I posted a comment pointing out that lots of people aren't completely sure, offhand, if && or == has higher pre
308.
by curi 19y ago
you could just rename the operators to lt and gt, so there is no visual cue either way. you could also change the argument order, but that's probably not a good idea :)
309.
by curi 19y ago
Some of the design choices [pg's] made are just bad, too. Well, name one, and give a reason.
310.
by curi 19y ago
lisp can do side effects. as i demonstrated. what's the problem?
311.
by curi 19y ago
but how can it be a reason people dislike lisp when C and Java programmers put their function calls in prefix order, too? the vast majority of programmers do function calls that way, and prefer it. and infix function calls in general is obv
312.
by curi 19y ago
cool. which of the basic arithmetic operators have difference precedence in which languages? what i am used to is * and / first, then + and -.
313.
by curi 19y ago
so you really advocate tokens in the order: x foo y over foo x y ? well, right or wrong, you are definitely deviating from the mainstream. that is, C and java coders will agree with me that prefix, and unlimited arguments, is better. the on
314.
by curi 19y ago
I agree throwing in a lot of variables with names can make code easier to read. You can also achieve the same effect by making one-line functions that just call a few other functions. It's quite possible that the prevalent style of writin
315.
by curi 19y ago
I said you can make a mechanism to define new infix operators, but it's not very good. Then you quoted so as to imply I didn't know that, and said that actually some languages have it.
316.
by curi 19y ago
read before you post
317.
by curi 19y ago
you're saying lisp is harder to understand b/c it's higher level and has more abstraction away from the way computers really work and away from assembly language (which are easy to understand, or something)? you don't need to know what your
318.
by curi 19y ago
regarding state, see the other example above. then post saying you meant infix math, not state. edit: and state is not only used to avoid nesting. that is just common . i do it myself in ruby. too much chaining stuff is confusing in ruby
319.
by curi 19y ago
not only that, 2 of the 3 sets of paren were not needed, the order of operations already would have gotten it right
320.
by curi 19y ago
infix and whether to call functions like foo(x y) or (foo x y) are separate issues. if infix is C's advantage, that is pretty silly. because first of all there is only a limited number of infix operators, and when you make your own construc
321.
by curi 19y ago
nothing about s-expressions is bad for using state and little nesting. something about C/etc is bad for nesting heavily. Edit: example. both lisp-style versions are nicer. if C has advantages, it isn't in making state work better. (de
322.
by curi 19y ago
BTW, tell me which of these makes more sense: (+ 3 4 (- 1 (/ 3 4)) (* (- 9 2) 8 3)) +(3 4 -(1 /(3 4)) *(-(9 2) 8 3)) why oh why would you want a function to be in the same grouping (set of paren) with arguments to another function, instead
323.
by curi 19y ago
the reason people put so much state and local variables in their program is that non-lisp languages get hard to read if you nest a lot, so they have to. and that is basically what i mean about lisp being objectively easier to read: the nota
324.
by curi 19y ago
in lisp you write trees. in other languages, you write weird things that get turned into trees, seemingly by magic. other languages seem easier to understand, to most people. this is because they have a lot of experience with all that mag
325.
by curi 19y ago
you're just contributing to the time spent talking about Arc instead of coding. the kind of people who were going to get anything done, know how to ignore pointless discussion.
326.
by curi 19y ago
Who are you talking about when you say "we"? I like Steve Jobs. As well as Woz.
327.
by curi 19y ago
boring. don't read.
328.
by curi 19y ago
500.times {puts "I will not throw paper airplanes in class"}
329.
by curi 19y ago
+1: I see what you did there.
330.
by curi 19y ago
<3

More ›