10 PRINT CHR$ (205.5 + RND (1)); : GOTO 10
I found this specific one via slashdot[1], but something similar, which I've never managed to find/replicate, was used to generate mazes on the Atari 800 XL at my school when I was a kid.[1] https://developers.slashdot.org/story/12/12/01/1847244/how-d...
quicksort :: Ord a => [a] -> [a]
quicksort [] = []
quicksort (p:xs) = (quicksort lesser) ++ [p] ++ (quicksort greater)
where
lesser = filter (< p) xs
greater = filter (>= p) xs
Now surely someone may come along and point out how this isn't a true quicksort[0] because it doesn't partition the elements in place, but it's more of the simplicity of the logic and its readability that showed me how beautiful functional code can be.[0] https://stackoverflow.com/questions/7717691/why-is-the-minim...
FD 100
That's the "hello, world" of turtle graphics in Logo. While probably not as beautiful as the several splendid examples posted in this thread, that simple line of code changed my world. I could make stuff happen in an otherwise mostly blank monochrome CRT display. Until then I had seen CRTs in televisions where I had very little control on what I see on the screen. But now, I had control. The turtle became my toy and I could make it draw anything on a 320 x 250 canvas.The next beautiful piece of code I came across in the same language was:
REPEAT 360 [FD 1 RT 1]
The code above draws an approximation of a circle by combining 360 short line segments. It showed me how control flow can be used elegantly to express complex ideas in a simple expression. And then I came across this: REPEAT 20 [REPEAT 180 [FD 1 RT 2] RT 18]
The above code draws 20 overlapping circles. The output looks like this: https://susam.in/files/blog/dosbox-logo-1.png .At an impressionable age of 9, reading and writing code like this, and using simple arithmetic, geometry, logic, and code to manipulate a two-dimensional world had a lasting effect on me. I like to believe that my passion for software engineering as well as my love for writing code, sharing code, and open source development are a result of coming across these beautiful code examples early in my life.
perl -e 'while(<>){$x=$_ if rand()<=(1/$.)}print $x'
For each line, pick that line as your random line if a random number (0<=n<1) is less than the reciprocal of the number of lines read so far ($.).It hits my elegant bone. Only one line... rand < 1/1, pick it. Two lines, same as one, but the second line has a 1/2 change of replacing line one. Third line same as before but gets a 1/3 chance of taking the place of whichever line has survived the first two picks. At the end... you have your random line.
(loop(print(eval(read)))
to have a REPL. (Just reverse the letters, easy enough to remember).That to me is elegance. It's simple yet powerful, and just 4 words really.
(define eval-expr
(lambda (expr env)
(pmatch expr
[`,x (guard (symbol? x))
(env x)]
[`(lambda (,x) ,body)
(lambda (arg)
(eval-expr body (lambda (y)
(if (eq? x y)
arg
(env y)))))]
[`(,rator ,rand)
((eval-expr rator env)
(eval-expr rand env))])))
There's an amazing talk about it: https://www.youtube.com/watch?v=OyfBQmvr2Hc
void strcpy(char *s, char *t) {
while (*s++ = *t++);
}
It's short, elegant, and quite readable to the trained eye–a bit sharp too, but if you use it right it's quite functional.
https://gist.github.com/zabirauf/29c89a084901cab8bc6b
Parsing binary data can be...nontrivial. The beauty is in the code that doesn't exist.
I can remember the first code that showed how to exploit IFS, race conditions via symlink, the classic "smashing the stack", RTM's worm.
Beauty of a code to me has nothing to do with the formatting, comments, documentations, but everything to do with the mind that bent it into place. Most of the beautiful code I have ever seen would be classified as ugly, spaghetti, not production worthy.
It really inspired me to get better at seeking out the fundamental operations of whatever I was implementing.
https://github.com/chrislgarry/Apollo-11/blob/master/Luminar...
$ makewords sentences | lowercase | sort | unique | mismatch -
It reads a file called sentences then prints the words that are not spelled correctly.To me it's; concise, expressive, flexible, modular... Which makes it beautiful...
Not to sound cheeky but eliminating code, is a beautiful thing. Less code is easier to maintain, understand, and faster to run. So the less code you can achieve, the better overall the software will be.
Very elegant use of the fall-through behavior of the swtich statement.
universal_server() ->
receive
{become, F} ->
F()
end.
[0] https://joearms.github.io/published/2013-11-21-My-favorite-e...
:(){ :|:& };:
Changed the way I think about code
module Primes where
primes = 2 : filter isPrime [3..]
isPrime x = all (\y -> mod x y /= 0) $ takeWhile (\y -> y * y < x) primes
The beauty of this is that it's self-referential. The list `primes` is built by filtering all the natural numbers for prime numbers, using the predicate `isPrime` which itself uses the list `primes`. The only caveat is that we need to encode that 0 and 1 are not prime numbers, but 2 is a prime number, to provide the base cases for the recursion. Furthermore, `isPrime` uses that each non-prime number has at least one prime factor less than or equal to its square root, to ensure that it only needs to look at a finite number of possible prime factors.If you have GHC in your repo, you can test this by putting it in a file and running `ghci` with the file as the only argument. It will give you a REPL where `primes` and `isPrime` are in scope:
*Primes> isPrime 200
False
*Primes> take 10 primes
[2,3,5,7,11,13,17,19,23,29]
class Derived : public Base
[0] https://en.wikipedia.org/wiki/Curiously_recurring_template_p...
#!/bin/rm
10 PAUSE 4E4
"PAUSE nstops computing & displays the picture for n frames of the television (at 50 frames per second, or 60 in America). n can be up to 32767, which gives you just under 11 minutes; if n is any bigger then it means 'PAUSE for ever'.
A pause can always be cut short by pressing a key"[0]
(4E4 = 4*10^4 = 40000)
[0] http://www.worldofspectrum.org/ZX81BasicProgramming/chap19.h...
There are beautiful code bases like DOOM source or SAT solvers that are like super models beautiful. Complete and hard to improve. Marvel at from a distance.
There is beautiful code in the libraries everybody uses all the time. All the lib* code. Somebody to marry. Discover the good beauty over time.
And then there is the beautiful snippet of clever code at the bar, quick to love, but one you get to know him it's much more trouble than he's worth.
_ = (
255,
lambda
V ,B,c
:c and Y(V*V+B,B, c
-1)if(abs(V)<6)else
( 2+c-4*abs(V)**-0.4)/i
) ;v, x=1500,1000;C=range(v*x
);import struct;P=struct.pack;M,\
j ='
https://codegolf.stackexchange.com/questions/23423/mandelbro...
# python
names = []
names[0] # <- raises IndexError
In Elm you are forced to always consider this possibility. # Elm
names = []
case List.head names of
Just name ->
name
Nothing ->
"empty"
I felt it was sort of like poetry. I unfortunately no longer have a link to it, and once looked very hard but couldn't find it.
I would be extremely appreciative of someone else saw it and had a link. If I recall correctly it was a type of interpreter, I remember it having code for parsing.
public static int bitCount(int i) {
i = i - ((i >>> 1) & 0x55555555);
i = (i & 0x33333333) + ((i >>> 2) & 0x33333333);
i = (i + (i >>> 4)) & 0x0f0f0f0f;
i = i + (i >>> 8);
i = i + (i >>> 16);
return i & 0x3f;
}
It was like magic for me when I encountered it first time.
- haskell:
perms [] = [[]]
perms xs = [ x:ps | x <- xs , ps <- perms ( xs\\[x] ) ]
- js: (using https://github.com/tc39/proposal-slice-notation for conciseness) const perms = xs => xs.length === 0
? [[]]
: xs.flatMap((xi, i) => perms([...xs[0:i], ...xs[i+1:]).map(xsi => [xi, ...xsi])
# Cartesian product of 2 or n lists- haskell:
cart2 xs ys = [(x,y) | x <- xs, y <- ys]
cartn :: [[a]] -> [[a]];
cartn [] = [[]]
cartn(xs:xss) = [x:ys | x <- xs, ys <- yss]
where yss = cartn xss
- js: const cart2 = (xs, ys) => xs.flatMap(x => ys.map(y => [x,y]));
const cartn = (...args) => args.reduce((yss, xs) => yss.flatMap(ys => xs.map(x => [...ys, x])), [[]]);
// or recursive
const cartn = (xs, ...xss) => xss.length === 0
? xs
: xs.flatMap(x => cartn(...xss).map(y => [x,y]))
10 PRINT "HELLO"
20 GOTO 10
30 END
RUN
I remember typing this on an ASR-33 and being amazed. I made a computer do that. Then I hit Ctrl-C and learned how to make a paper tape with a "here is" leader, turning the paper punch off, then typing "LIST" and turning it back on before hitting RETURN.
A PDP-11/10 with 16K and 3 20mA TTYs connected, no disks, no storage except paper tape.
I've still got that paper tape somewhere, it's 42 years old now.
REBOL [title: "Calculator"] view layout [ origin 0 space 0x0 across style btn btn 50x50 [append f/text face/text show f] f: field 200x40 font-size 20 return btn "1" btn "2" btn "3" btn " + " return btn "4" btn "5" btn "6" btn " - " return btn "7" btn "8" btn "9" btn " * " return btn "0" btn "." btn " / " btn "=" [ attempt [f/text: form do f/text show f] ] ]
https://easiestprogramminglanguage.com/easiest_programming_l...
>>>list(zip(*[(1, 2, 3), (4, 5, 6), (7, 8, 9)]))
[(1, 4, 7), (2, 5, 8), (3, 6, 9)]
I think a much better question would be most beautifully structured codebase.
Code, as a snippet, or line, is constantly struggling between poetic conciseness and verbose clarity... To which I will always pick clarity (for "the next guy"), hence not necessarily elegant.
CONS: EXCH A,[EXCH A,[...[PUSHJ P,GC]]]
EXCH A,CONS
This allocates a cons cell for Lisp on PDP-10, by using the first instruction in the routine as the head pointer of the free list. The first instruction puts the first word of the free list into A (and then clobbers that word with the original contents of A, initializing the cons cell). The second then swaps the first instruction with the first item in the free list.The free list is simply a linked list of first instructions, which could be done because the PDP-10 was a 36-bit machine with an 18-bit address space, and the address field of an instruction was the entire right half: the same part of a word that was used as a pointer. So, when interpreted as a pointer, each of these instructions was just the pointer to the next cell.
The beautiful part to me is that, once you ran out of free list, the last word was a call to the garbage collector, which would build a free list of unreferenced cells and return a pointer to the second cell (with the correct opcode field) in A; the second instruction would then finish the cons operation, leaving the address of newly allocated cons cell in A.
Option provides an elegant way to handle parameters or results that may or may not be defined.
Here's a simple Option implementation:
https://gist.github.com/mceachen/75598510275865b8cf88bb2ef80...
With this you can write something like
Opt(possiblyNullResult).flatMap(ea => functionThatRequiresANonNullResultAndReturnsUndefinedOrDefined(ea)).getOrElse(() => someDefaultValue)
And here's a (very) simple implementation of lazy:
https://github.com/photostructure/exiftool-vendored.js/blob/...
The idea of lazy is to allow deferment of expensive operations until they are actually needed.
The above implementation allows for something like:
const service = lazy(makeService)
Which will ensure makeService is only called once, and the first caller will have to wait for the result of makeService(). All subsequent callers re-use the first result.
It's a simple construct, but extremely handy.
[1] https://github.com/scala/scala/blob/v2.13.1/src/library/scal...
https://m.youtube.com/watch?v=HxaD_trXwRE
A good debuggable piece of code explains what it is trying to do by being clearly written and conforming to a consistent and logical model. I don’t think I would ever have invented this type of lexer pattern in Go by myself, but would be very grateful to come across it in a code base I had to fix. Like Duff’s Device mentioned in this thread, it has just the right amount of cleverness without becoming inscrutable.
Also, if you’ll excuse some avuncular pride, my niece and I wrote some code yesterday. She asked me how many times grandma’s clock chimes every day and we ended up with the following Ruby:
2 * (1..12).reduce(&:+)
fibs = 0 : 1 : zipWith (+) fibs (tail fibs)
,[.,]
When it comes to the weird and wonderful world of esoteric programming languages, the above Brainfuck program is pretty elegant. It's a basic implementation of the echo program: printing back what the user inputs.The complete language consists of eight single-character commands. The four used in the echo program is:
, – accept one byte of input and store it at the current memory cell
. – output the byte at the current memory cell
[ – if the value of the current memory cell is zero, jump forward to the command after the matching ]
] – if the value of the current memory is nonzero, jump back to the command after the matching [
:v/./,/./-j
in vim will go through the whole file, joining multiple consecutive empty lines into one. Not only it is fork-bomb-level cryptic, but also showcases how you can use addresses to do advanced stuff.Somewhat more readable version:
:vglobal /./ .,/./- join
which is: go to every line that doesn't match (vglobal) /./ (is empty) and join lines from that line (.) to the line before (-) the next line that is not empty (/./ again).
: \ IMMEDIATE
#IB @ >IN !
; \ We can now comment!
Implementing a forth system is unbelievably fun because of gems like this.
C (K&R) program that calculates PI number by measuring circle that is its code: https://en.wikipedia.org/wiki/International_Obfuscated_C_Cod...
Perl one-liner that checks if a number is prime: perl -lne '(1x$_) =~ /^1?$|^(11+?)\1+$/ || print "$_ is prime"'
4856507896573978293098418946942861377074420873513579240196520736 6869851340104723744696879743992611751097377770102744752804905883
1384037549709987909653955227011712157025974666993240226834596619 6060348517424977358468518855674570257125474999648219418465571008
4119086259716947970799152004866709975923596061320725973797993618 8606316914473588300245336972781813914797955513399949394882899846
9178361001825978901031601961835034344895687053845208538045842415 6548248893338047475871128339598968522325446084089711197712769412
0795862440547161321005006459820176961771809478113622002723448272 2493232595472346880029277764979061481298404283457201463489685471
6908235473783566197218622496943162271666393905543024156473292485 5248991225739466548627140482117138124388217717602984125524464744
5055834628144883356319027253195904392838737640739168912579240550 1562088978716337599910788708490815909754801928576845198859630532
3823490558092032999603234471140776019847163531161713078576084862 2363702835701049612595681846785965333100770179916146744725492728
3348691600064758591746278121269007351830924153010630289329566584 3662000800476778967984382090797619859493646309380586336721469695
9750279687712057249966669805614533820741203159337703099491527469 1835659376210222006812679827344576093802030447912277498091795593
8387121000588766689258448700470772552497060444652127130404321182 610103591186476662963858495087448497373476861420880529443
This is a 1811-digit illegal prime number, which when unpacked into binary, becomes a compressed ELF executable which will decrypt DVDs. This was one of many ways used to enable people who had legally purchased a DVD with copy protection to play it on Linux. Here's the story behind finding the prime: https://web.archive.org/web/20070223075434/http://asdf.org/~...Aside from that, the qrpff perl scripts that became t-shirts (https://web.archive.org/web/20011221024307/http://www.copyle...) were another fun and illegal way to point out the stupidity of the DMCA. But they aren't so pretty ;)
s --> a,b.
s --> a,s,b.
a --> [a].
b --> [b].
s is a non-terminal, a and b are preterminals, [a] and [b] are terminals and
"-->" can be read as "expands to". The syntax is the same as BNF and the
grammar is a Prolog program that is directly executable as both a recogniser
or a generator, depending on instantiation pattern at call time.How does the grammar work? It must accept, or generate, a string of equal numbers of a's and b's, but the grammar is not keeping track of the length. There is nothing to count how many a's have been consumed or produced so far. How does it know?
s is the start symbol of the grammar. The first production of s, which is also the terminating condition for the recursion, accepts or produces one a followed by one b. The second production of s accepts an a, followed by an s-string, followed by a b.
Suppose we executed the grammar as a generator. In the first step, the output would be the string S₁ = ab. In the second step, the output would be the string S₂ = aS₁b. In the n'th step the output would be aSₙb.
So the grammar would always add exactly one a at the start, and one be at the end of its output, recursively.
And it would always generate the same number of a's as b's.
Similar for when it runs as an acceptor.
You can visualise the first couple of steps as follows:
S
,-------|-------.
| S |
A / \ B
| A B |
a | | b
a b
https://en.wikipedia.org/wiki/The_Complexity_of_Songs
https://en.wikipedia.org/wiki/Generative_music
https://en.wikipedia.org/wiki/Repetitive_song
|>~~~<<<
https://en.wikipedia.org/wiki/E%3DMC2_(song)
About 10 years later you would find this stuff everywhere in boost but for the time this was spectacularly elegant for C++
- https://en.wikipedia.org/wiki/Tower_of_Hanoi#Recursive_solut...
Regex for that is just great
^((?!word).)*$
https://github.com/billzhong/inbox.py/blob/master/inbox.py
It's about 42 lines of actual code excluding newlines.
10 print "Hello World";
20 goto 10;
run
This python code was part of the imaging, analysis, and simulation software for radio interferometry that led to the historical first 'image' of a black hole.
array.filter((item, index, arr) => arr.indexOf(item) === index)
It works because indexOf returns the index of the first occurrence of the item, so you're asking whether this occurrence is the first occurrence.
Also:
subsets = filterM (pure [True, False])
int dsf_find(int *t, int a)
{
if (a != t[a])
t[a] = dsf_find(t, t[a]);
return t[a];
}
(defun unify (x y e)
(let ((x (look-up x e))
(y (look-up y e)))
(cond ((eq x y) e)
((variable-p x) (cons (list x y) e))
((variable-p y) (cons (list y x) e))
((or (atom x) (atom y)) nil)
(#t (let ((ne (unify (car x) (car y) e)))
(and ne (unify (cdr x) (cdr y) ne)))))))
LOOK-UP looks up X or Y in E, VARIABLE-P returns truth, if X or Y is a
variable.
fibs = 0:1:zipWith (+) fibs (tail fibs)
Recursive definitions and lazy programming blew my mind.
// Dijkstra, Edgar. "Go To Statement Considered Harmful".
// Communications of the ACM. Vol. 11. No. 3 March 1968. pp. 147-148
if (neighboridx == target) {
goto OUTSIDE;
}
const flatten = arr => ((flat = [].concat(...arr)) => flat.some(Array.isArray) ? flatten(flat) : flat)()
Its simple, but i was - and still am - way to proud of it ;p
int henny() {
return((*opp_history?opp_history[random()%*opp_history+1]+1:random())%3);
}
[1] https://webdocs.cs.ualberta.ca/~darse/rsbpc.html
When I discovered the Magazine (back un the 90's) I wasn't ready to code for windows nor win32 because I was a broke student with a 1MB 80286; but I am pretty sure reading and rereading that code and articles made me learn more C/C++ than most books or courses I took later.
Mr. Petzold: If we meet someday, the beers are on me!
CNV10: MOV R0,-(SP) ;Converts binary value
CLR R0 ;in R0 to ASCII in buffer
1$: INC R0 ;pointed to R1
SUB #10.,@SP
BGE 1$
ADD #72,@SP
DEC R0
BEQ 2$
CALL CNV10
2$: MOVB (SP)+,(R1)+
RETURN
https://www.cs.princeton.edu/courses/archive/spr09/cos333/be...
This returns the greatest value (passed ? or max_value column):
?^((?^max_value)&-(?
And for minimum: min_value^((?^min_value)&-(?
Something completely different: the Factor language, in the beginning.
Array(nil).map ...
Array(“string”).each ...
Array([“a”, “b”]].select ...
Array([]).reject ...
...
Sounds trivial compared to the rest listed here, but for me it was just the first time I got a for loop to work in java.
Like, conceptually I knew programming was about getting machines to doStuff, but this was probably the first time I actually had a machine do something I asked of it directly. Well, that and Logo writer.
fn factorial(i: u64) -> u64 {
(1..=i).product()
}
In almost every other language this code would look messy or use some terrible recursion.For example in C it would look something like this:
long factorial(int n)
{
int c;
long result = 1;
for (c = 1; c <= n; c++)
result = result * c;
return result;
}
Or with recursion: long factorial(int n)
{
if (n == 0)
return 1;
else
return(n * factorial(n-1));
}
In any case, I thin Rust looks better in every way with its cleaner syntax.
fibonacci = 1 : 1 : [x + y | (x, y) <- zip fibonacci (tail fibonacci)]
For me, lazy as I am, most recursive algorithms operating on binary trees are a thing of beauty. Post-order ones even more so.
#ifdef __GNUC__
#define TDB_LIKELY(val) (__builtin_expect((val), 1))
#define TDB_UNLIKELY(val) (__builtin_expect((val), 0))
#else
#define TDB_LIKELY(val) (val)
#define TDB_UNLIKELY(val) (val)
#endif
This code is beautiful when it deal with CPU cache-line effects to speed up your program.
[1] https://github.com/apache/thrift/blob/647501693bd14256df8839...
powerSet = filterM (const [True, False])
repeat 360 [fd 1 rt 1]
used to draw a circle in Logo on the BBC micro. So obvious to an adult but blew my mind.
main(){char*s="main(){char*s=%c%s%c;printf(s,34,s,34);}";printf(s,34,s,34);}
It is beautiful because it was my introduction to C that led to the world that I am in now.
class Universe(void):
def __init__():
eval("Fiat Lux")
This was the first artistic use of code I had ever stumbled upon (not including LOGO programs).
it was a stored procedure to populate a dropdown list of languages each translated into their own language on an old asp.net app. i always liked it
This Python snippet is the most beautiful code I’ve read. It only went downhill from there.
mv ax, 0013h
int 10h
Intro to pretty much any language. It opens up so many possibilities ..
cat animals.txt | awk '{ cnts[$0] += 1 } END { for (v in cnts) print cnts[v], v }'
awk 'NR==FNR{A[$0]; next} $0 in A' file1.txt file2.txt
LEFT = «X=⌜»;
RIGHT = «⌝; While(True) {Print(X); X=⌜Print(`⌝+X+⌜')⌝}»;
X = «Exit()»;
While(True) {
X = LEFT + X + RIGHT;
Print(X);
}