Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

The myth of recursion

Name: Anonymous 2015-09-17 20:12

I asked my 4 year old niece what are the ingredients in gravy and she answered with, "gravy". It kind of reminded me of programmers who use recursion to solve problems. When you use recursion you are essentially defining a procedure in terms of itself which makes no sense in the real world. Make believe stuff like this is why real scientist and engineers don't take computer scientist seriously.

Name: Anonymous 2015-09-17 20:47

Better get that bitch a copy of Le Guide culinaire.

Name: Anonymous 2015-09-17 21:36

Kawaii. She isn't wrong. Most gravies I've made involved starting from gravy in a can.

Name: Anonymous 2015-09-17 23:28

My other can is a jar.

Name: Anonymous 2015-09-17 23:36

Java in a can.

Name: Anonymous 2015-09-18 0:06

I fukkin love gravy

Name: Anonymous 2015-09-18 2:50

Recursion is a scam.

Name: Anonymous 2016-03-02 2:59

https://www.refheap.com/110663/raw
Which one of you did this?

Name: Anonymous 2016-03-02 3:22

>>8
It was me.

Name: Anonymous 2016-03-02 14:02

>>9
No it was actually me.

Name: Anonymous 2016-03-02 15:38

Recursion is just another form of divide & conquer, or the old "How do you eat an elephant? One bite at a time." Solve a bit of the problem and repeat until it's gone.

Name: Anonymous 2016-03-02 15:46

What if somebody from this board actually reproduced?

Name: Anonymous 2016-03-02 17:19

>>12
/prog/ doesn't have side-effects.

Name: Anonymous 2016-03-02 20:27

>>1
Sometime recursion just makes the shortest and easiest to understand solution. If you want to write thousands of abstract factory beans instead, go for it.

Name: Anonymous 2016-03-02 23:14

recursion is not unlike iteration in reverse

Name: Anonymous 2016-03-03 3:07

Isn't recursion the same as pushing the problem's parameters onto a stack, then popping, splitting and pushing them until you get down to the base case.
The only difference is that recursion uses the implicit execution stack, leaving no way to parallelize the work performed.

Name: Anonymous 2016-03-03 3:08

>>16
You should see Haskell, everything's done using recursion!

Name: Anonymous 2016-03-03 5:39

Recursion is shit.
Lazyness + corecursion is the future.

Name: Anonymous 2016-03-03 5:58

>>18
Still doesn't fix the serial nature of recursion.

Name: Anonymous 2016-03-03 7:00

>>19
But is cool!

Name: Anonymous 2016-03-03 8:08

call/cc is the future of computation. I don't see how anyone could dispute this. While faggots are pumping the stack full of garbage with non-tail recursed fibs calls, continuations can cleanly jump in right to where the action is and start closing worlds and opening the next.

Name: Anonymous 2016-03-03 13:03

>>21
Check 'em

Name: Anonymous 2016-03-03 13:17

>>22
My recursive dubs checker crashed with stack overflow, but after visual inspection of this case, I can confirm that you indeed got dubs. Nice job!

Name: Anonymous 2016-03-03 14:50

>>23
Don't encourage the retard.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List