Client : Can you make some adblock?
Me : Why? There is a lot of good things already...
C : I mean... Listen carefully.
M : ok
C: i have some google ads and user blocks with adblock
M : yeah, that is normal
C : so i implemented adblock blocker which blocks adblock so that i can show the webpage plus ads when the user disables adblock.
M : i bet users hate that.
C : yeah, so users found out a way to disable adblock blocker which disables adblock blocker which i implemented to show the ads! So i cant earn revenue..
M : so what?
C : Can you make ad block block block block?
M : Sure. How much will you give me ?
C : 20 to 30 dollars
M : great ( the most generous client ever seen)

*couple of years later*

Client : can you make ad block block block block block block block block block block?
Me : i cant understand
C : count the number of block
If there is odd number of block i means to block ads.
If there is even number of block ads, it means to show ads making user to disable ads.
M : so just tldr your request this time
C : even number
M : ok how much will you pay
C : 20 to 30 dollars

*next day*
C : can you..
M : offline

Who in the fucking world made ads, made adblock and made adblock block?

Just noticed on "winehq" that the acronym for "Wine" is "Wine Is Not an Emulator". This is great and all, but all my mind can think about is the infinite recursion problem they've got there.

Was joking with my sister about who has more steps. She had done more steps so far, so I said that I would walk 20 times around the McDonald's, where we were going to eat. She replied that she would walk 50 times around it, so I said that I would walk 2 times more around it than she would. She then said, that she would go once more around it. In the end, I explained recursion and infinite loops to her. Her comment was "großer Blödsinn" (German) -> "big bullshit".

Infinite recursion

I just came across this piece of recursive code, as much as I can guess this should be an infinite recursion but somehow it executes and does terminate. Can anybody tell me how this happens and what will be it's time complexity ?

Just some Linux file system fun...

Despite common sense, I think technology is not making our lives easier. It's just build chaos on top of chaos.

Take server-side programming for instance.

First you have to find someone to host your thing, or a PaaS provider. Then you have to figure out how much RAM and storage you need, which OS you're going to use. And then there's Docker (which will run on top of a VM on AWS or GCP anyway, making even less sense). And then there's the server technology: nginx, Apache (and many many more; if, that is, you're using a server at all). And then there are firewalls, proxies, SSL. And then you go back to the start, because you have to check if your hosting provider will support the OS or Docker or your server. (I smell infinite recursion here.)

Each of these moving parts come with their own can of worms in terms of configuration and security. A whole bible to read if you want to have the slightest clue about what you're doing.

And then there's the programming language to use and its accompanying frameworks. Can they replace the server technology? Should you? Will they conflict with each other and open yet another backdoor into your system? Is it supported by your hosting provider? (Did I mention an infinite recursion somewhere?)

And then there's the database. Does it have a port to the language/framework of your choosing? Why does it expose an web interface? Is it supposed to replace your server? And why are its security features optional again? (Just so I have to test both the insecure and the secure environments?)

And you haven't written a single line of code yet, mind you.

Devs don't understand "vicious circle". Please use "infinite recursion".

Someone made an infinite recursion loop through the aws cloud and racked up 86,000$ of bills in a few hours

IF I see something infinite and more than three.

and never more than three in real world.

I use recursion.

because who knows, people are crazy.
myself included.

I wouldn't be surprised if JavaScript reached the maximum allowed stack size without needing infinte recursion