Podcast #128: We chat with Kent C Dodds about why he loves React and discuss what life was like in the dark days before Git. Listen now.
4 replaced http://codegolf.stackexchange.com/ with https://codegolf.stackexchange.com/
source | link

Bash + Xdotool, 36 bytes

for((;;)){ xdotool key 66;sleep .5;}

Just execute it in a bash shell. It needs to be in a graphical environment. Infinite loop from herehere. Changed Num_Lock to 66 to save 6 bytes, and thanks to @Michael Kjörling for 2 bytes.

Bash + Xdotool, 36 bytes

for((;;)){ xdotool key 66;sleep .5;}

Just execute it in a bash shell. It needs to be in a graphical environment. Infinite loop from here. Changed Num_Lock to 66 to save 6 bytes, and thanks to @Michael Kjörling for 2 bytes.

Bash + Xdotool, 36 bytes

for((;;)){ xdotool key 66;sleep .5;}

Just execute it in a bash shell. It needs to be in a graphical environment. Infinite loop from here. Changed Num_Lock to 66 to save 6 bytes, and thanks to @Michael Kjörling for 2 bytes.

3 added 8 characters in body
source | link

Bash + Xdotool, 4536 bytes

for((;;)){ xdotool key Num_Lock; sleep66;sleep .5; }

Just execute it in a bash shell. It needs to be in a graphical environment. It uses Num Lock because it is shorter(Thanks to @Engineer Toast), and infinite Infinite loop from here. Changed Num_Lock to 66 to save 6 bytes, and thanks to @Michael Kjörling for 2 bytes.

Bash + Xdotool, 45 bytes

for((;;)){ xdotool key Num_Lock; sleep .5; }

Just execute it in a bash shell. It needs to be in a graphical environment. It uses Num Lock because it is shorter(Thanks to @Engineer Toast), and infinite loop from here

Bash + Xdotool, 36 bytes

for((;;)){ xdotool key 66;sleep .5;}

Just execute it in a bash shell. It needs to be in a graphical environment. Infinite loop from here. Changed Num_Lock to 66 to save 6 bytes, and thanks to @Michael Kjörling for 2 bytes.

2 added 100 characters in body
source | link

Bash + Xdotool, 5145 bytes

while true; dofor((;;)){ xdotool key Num_Lock; sleep .5; done}

Just execute it in a bash shell. It needs to be in a graphical environment. It uses Num Lock because it is shorter(Thanks to @Engineer Toast), and infinite loop from here

Bash + Xdotool, 51 bytes

while true; do xdotool key Num_Lock; sleep .5; done

Just execute it in a bash shell. It needs to be in a graphical environment. It uses Num Lock because it is shorter(Thanks to @Engineer Toast)

Bash + Xdotool, 45 bytes

for((;;)){ xdotool key Num_Lock; sleep .5; }

Just execute it in a bash shell. It needs to be in a graphical environment. It uses Num Lock because it is shorter(Thanks to @Engineer Toast), and infinite loop from here

1
source | link