Daily reminder that if you're still using loops in 2017, you're doing it wrong

Daily reminder that if you're still using loops in 2017, you're doing it wrong.

Those programming in dinosaur-era procedural languages like C or Fortran are the exception to the rule.

What is the most futuristic language?
SML ML 1ML ...?
I'm bored

¯\_(ツ)_/¯

>i dont understand abstraction
ok

Are you stupid?

>[overflows stack]

> increments your stack pointer

(define nigger (nigger))

Daily reminder if you still use indentation instead if {} your opinion is invalid

Daily reminder that pufunctional programming doesn't work in the real world.

What should we use instead of loops?

This is exactly why.

You should code every possibility by hand obviously.

...

Daily reminder if you can't fit all the code you need in one line and use only letters for variables then you are doing it wrong.

Map, Reduce, Filter, etc.

goto

And comprehensions

Should I learn a functional language? I read Norvig's post on writing a Lisp interpreter and now Im curious.
Any big benefit or is it just preference/mindset?

The change in mindset IS a big win.

Daily reminder that functional programming is bloated, inefficient, slow, more complicated and uglier than procedural programming.

These are encapsulated loops.

Even if they use iterators?

procedural & simplicity is the final redpill but its hard to convince the OOP maniacs to it. But functional seems to appeal to their mindsents and functional at least treats data as data and doesn't lead to disgusting do-ers objects or unmaintable shared state being inherited around.

Recursion

Implement stochastic gradient descent in Haskell. Don't cheat with loops or whatever is the equivalent in Haskell.
>protip: it will be a mess

It will be a simple recursion.

>simple
If you say so user

All of these are turning into loops after assembly, recursion is a social construct.

*moreover, recursion is bloating stack

>Don't cheat with loops or whatever is the equivalent in Haskell.
You don't need loops. Which is good because we don't have them.

>muh abstraction
T H I S
H
I
S

list comprehensions _are_ loops

>they don't know about tail recursion

>All of these are turning into loops after assembly
In some cases, it can compiled into the same assembly, but that doesn't make it a loop.

You are correct. I completely forgot about them because I don't use them, and they're backwards compared to imperative languages, and you use them more like creating a list and mapping over it in the same block, and there is no way to iterate until a predicate is true like a while loop. But yeah, basically a loop